Has Python 2.4.1 changed implementation for __init__.py???

[Fredrik Lundh]

Werner Merkl wrote:

> I just downloaded http://www.python.org/pypi/xexpr/0.02, installed
> if (python setup.py install) and tried the example in the README file.
>
> Than I got following error: AttributeError: 'module' object has no attribute 'Read'
>
> This is same behavior for all module using empty __init__.pr files,
> like venster, Pyrex or libxmlmods...

if "xexpr" is a package with an empty __init__.py file, the behaviour you're
seeing is the expected behaviour.  importing a toplevel module doesn't auto-
matically import any submodules.

> Is there a change in the implementation, so that every module needs an
> explicit list for exchanged modules?

what's an "exchanged module"?

> EXAMPLE
> ------------------------------------------------------------------------
>
> Python 2.4.1 (#65, Mar 30 2005, 09:13:57) [MSC v.1310 32 bit (Intel)] on win32
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import xexpr
> >>> example = '<foo a="b" c="d"><bar><baz a="d" />Blah</bar></foo>'
> >>> xexpr.Read.to_xexpr(example)
> Traceback (most recent call last):
>   File "<stdin>", line 1, in ?
> AttributeError: 'module' object has no attribute 'Read'
> >>>

does it work better if you type

    import xexpr.Read

before you call the to_xexpr function?

</F>