[Python-Dev] Use C extensions compiled in release mode on a Python compiled in debug mode

Victor Stinner vstinner at redhat.com
Sun Apr 28 04:53:25 EDT 2019

FYI I pushed my 3 changes to implement my idea. It is now possible to
install some extensions in release mode and some others in debug mode.
Python in debug mode prefers debug extensions. I documented changes here:

The library filename has to be different in debug mode, so it can be
co-installable with release build of a C extension.


Le samedi 27 avril 2019, Stefan Behnel <stefan_ml at behnel.de> a écrit :
> Matthias Klose schrieb am 25.04.19 um 13:48:
>> Are there use cases where you only want to load *some*
>> debug extensions, even if more are installed?
> Not sure if there are _important_ use cases (that could justify certain
> design decisions), but I can certainly imagine using a non-debug (and
> therefore faster) Pandas or NumPy for preparing some data that I need to
> debug my own code. More generally, whenever I can avoid using a debug
> version of a *dependency* that I don't need to include in my debug
> analysis, it's probably a good idea to not use the debug version.
> Even given venvs and virtualisation techniques, it would probably be nice
> if users could install debug+nondebug versions of libraries once and then
> import the right one at need, rather than having to set up a new
> environment (while they're on a train in the middle of nowhere without
> access to PyPI).
> Stefan
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:

Night gathers, and now my watch begins. It shall not end until my death.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20190428/2cf78802/attachment.html>

More information about the Python-Dev mailing list