This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author movement
Recipients movement, rb, schmir
Date 2008-11-28.15:17:39
SpamBayes Score 0.00024158716
Marked as misclassified No
Message-id <1227885460.72.0.255331988585.issue4434@psf.upfronthosting.co.za>
In-reply-to
Content
If Ubuntu wants to deliver a static libpython, it also needs to deliver
static versions of the Python modules, or accept that they're not usable
from a static libpython.

It makes no sense at all to mix libpython.a with these .so files. Many of
them declare dynamic dependencies on stuff like libkrb5.so or
libsqlite3.so. I can't conceive of a scenario where you need a static
libpython AND you're OK with both dlopen() of the Python modules and any
of its dynamic dependencies. What is this case?
History
Date User Action Args
2008-11-28 15:17:41movementsetrecipients: + movement, schmir, rb
2008-11-28 15:17:40movementsetmessageid: <1227885460.72.0.255331988585.issue4434@psf.upfronthosting.co.za>
2008-11-28 15:17:39movementlinkissue4434 messages
2008-11-28 15:17:39movementcreate