➜

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 pitrou
Recipients barry, eric.smith, koobs, martin.panter, mdk, nascheme, pitrou, twouters, vstinner, xdegaye, yan12125
Date 2018-09-26.17:21:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1537982514.41.0.545547206417.issue34814@psf.upfronthosting.co.za>
In-reply-to
Content 
Why do you call this a bug?
For me it's the reverse: it's linking to libpython.so which is a bug.  It means a C extension compiled with a shared-library Python cannot be imported on a monolithic Python (which doesn't have libpython.so).  It's a real problem when you want to redistribute compiled C extensions: if you compile it on RedHat/CentOS, it won't work on Ubuntu/Debian (the reverse works).

I even opened an issue about that: issue21536
("extension built with a shared python cannot be loaded with a static python")
History
Date User Action Args
2018-09-26 17:21:54pitrousetrecipients: + pitrou, twouters, barry, nascheme, vstinner, eric.smith, xdegaye, martin.panter, koobs, yan12125, mdk
2018-09-26 17:21:54pitrousetmessageid: <1537982514.41.0.545547206417.issue34814@psf.upfronthosting.co.za>
2018-09-26 17:21:54pitroulinkissue34814 messages
2018-09-26 17:21:54pitroucreate