➜

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 reimar
Recipients barry, cstratak, doko, eric.smith, koobs, martin.panter, mdk, nascheme, ned.deily, petr.viktorin, pitrou, reimar, serge-sans-paille, twouters, vstinner, yan12125
Date 2019-04-29.14:37:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1556548675.57.0.349986067346.issue34814@roundup.psfhosted.org>
In-reply-to
Content 
> In short, RTLD_LOCAL is not supported.

I am sorry, this is not a workable stance.
This does not just affect loading libpython directly.
It also affects dlopen of a library that links to a library ... that links to libpython.
For a developer is impossible to know if some library via dozens of dependencies might ever bring in libpython.
Thus your stance is essentially equivalent to "nobody must ever use RTLD_LOCAL". I find it hard to consider that an acceptable "solution".
History
Date User Action Args
2019-04-29 14:37:55reimarsetrecipients: + reimar, twouters, barry, nascheme, doko, pitrou, vstinner, eric.smith, ned.deily, petr.viktorin, martin.panter, koobs, yan12125, serge-sans-paille, mdk, cstratak
2019-04-29 14:37:55reimarsetmessageid: <1556548675.57.0.349986067346.issue34814@roundup.psfhosted.org>
2019-04-29 14:37:55reimarlinkissue34814 messages
2019-04-29 14:37:55reimarcreate