On Fri, Jul 17, 2009 at 11:55:30AM -0400, Tim Abbott wrote: > package: python-support > version: 1.0.3 > > Consider a package foo that provides both a python module (say, foo.bar) > and a python program baz that imports foo.bar. With the current > python-support implementation, it is not possible to run baz in the > package's postinst script. What will happen is that the "import foo.bar" > line of baz will fail in the postinst script with > > ImportError: No module named foo > > because /usr/lib/pymodules/python2.5/foo/__init__.py doesn't exist yet. > (It is created by the python-support trigger that runs after installation > completes.) > > It seems like one could fix this by having python-support create its empty > __init__.py file when update-python-modules is run, rather than delaying > until the trigger is processed. > > It is quite possible that this problem will also affect situations where > the package running bar in its postinst script depends on the package > containing foo.bar and the packages are installed at the same time, but > I've not tested it.
More than missing __init__.py files, the lack of the symbolic links to /usr/share/pyshared hurts. #582071 and #576108 are an emanation of this, where pre-depend only worked around part of the issue. The problem in my case is that installing python-xpcom triggers the xulrunner script, which doesn't work properly if the python-support trigger hasn't run first (because of the lack of symlinks) Mike -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
