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
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
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 *" t
