Hi there, I'm getting tracebacks like this from a package (pymbolic in this case--available from PyPI) installed using setuptools.
8< -----------------------------------------------------------------------------
File "build/bdist.linux-x86_64/egg/pymbolic/primitives.py", line 150, in
__str__
File "/usr/lib/python2.5/site-packages/PIL/__init__.py", line 17, in
__call__
File "build/bdist.linux-x86_64/egg/pymbolic/mapper/stringifier.py", line 75,
in map_product
File "build/bdist.linux-x86_64/egg/pymbolic/mapper/stringifier.py", line 75,
in <genexpr>
File "/usr/lib/python2.5/site-packages/PIL/__init__.py", line 58, in rec
File "build/bdist.linux-x86_64/egg/pymbolic/mapper/stringifier.py", line 23,
in handle_unsupported_expression
8< -----------------------------------------------------------------------------
At least two things are bad here:
- Some source files refer to their relative location in the build directory of
their *own* package. Unsurprisingly, this is not found when an exception
occurs in user code that does not live in the package's base directory.
- Whenever a file name is __init__.py, the PIL __init__.py gets picked up
instead of the corect file name. (nothing uses PIL in what generated the
above)
What can I do to fix this? (setuptools 0.6c8 on 2.5)
Thanks
Andreas
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
