[issue34461] Availability of parsers in etree initializer

Ned Deily added the comment: Thanks for the suggestion but, since there has been no agreement that this change is desirable, I am going to close the issue along with the submitted PRs. -- nosy: +ned.deily resolution: -> not a bug stage: patch review -> resolved status: open ->

[issue34461] Availability of parsers in etree initializer

nilanjan roy added the comment: @serhiy.storchaka: If I concur with your comment then probably declaration of *__all__** over xml initializer(__init__) is little contradictory - because whenever we declare __all__ to enable global-scope means API provides the flexibility to use * during

[issue34461] Availability of parsers in etree initializer

Serhiy Storchaka added the comment: I concur with Stefan. Not all users of ElementTree need to import ElementInclude, ElementPath and deprecated cElementTree. If you need ElementInclude or ElementPath, it is better to specify this explicitly. The star import is not recommended in general

[issue34461] Availability of parsers in etree initializer

nilanjan roy added the comment: @scoder: *xml* package organization have little confusion 1. Current xml have exposed all the sub-packages from *__all__* scope from the initializer - so there are possibilities to write code from script a. *import xml as x* or *import xml.somepackage as x*

[issue34461] Availability of parsers in etree initializer

Change by Roundup Robot : -- pull_requests: +8482 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34461] Availability of parsers in etree initializer

Stefan Behnel added the comment: The normal way to use ElementTree is to import the ElementTree module from the xml.etree package. Why do you think that needs to change? And why do you want to enforce an import of all modules before you even know which of them the users actually wants?

[issue34461] Availability of parsers in etree initializer

Change by Ronald Oussoren : -- nosy: +eli.bendersky, scoder ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34461] Availability of parsers in etree initializer

Change by Roundup Robot : -- keywords: +patch pull_requests: +8330 stage: -> patch review ___ Python tracker ___ ___

[issue34461] Availability of parsers in etree initializer

New submission from nilanjan roy : As xml package make the availability of separate global name-space by *__all__* so considerably *etree* should have included of all the parser files in its initialize(i.e. in *__init__.py*). So if any script consider as "from xml import *" then *etree*