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 loewis
Recipients Banger, loewis, pitrou
Date 2014-04-19.09:13:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1397898813.41.0.649598673101.issue21292@psf.upfronthosting.co.za>
In-reply-to
Content
I think the issue is actually slightly different. You can certainly build your Python "in debug", and still link with the release mode Python. The question is what "in debug" means, and the normal definition would be "with the generation of debug symbols by the compiler".

What you cannot do is
1. to build with _DEBUG defined (or whatever the exact spelling of the macro is, or
2. to link with the debug version of msvcrt.

We could fix 1, i.e. allowing you to define _DEBUG, and still bind the release version. I think we cannot reasonably fix 2; this is a Microsoft issue.

You can work around by simply not defining _DEBUG, and still build "in debug"
History
Date User Action Args
2014-04-19 09:13:33loewissetrecipients: + loewis, pitrou, Banger
2014-04-19 09:13:33loewissetmessageid: <1397898813.41.0.649598673101.issue21292@psf.upfronthosting.co.za>
2014-04-19 09:13:33loewislinkissue21292 messages
2014-04-19 09:13:32loewiscreate