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 Banger
Recipients Banger, loewis, pitrou
Date 2014-04-25.03:26:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1398396418.9.0.778825554215.issue21292@psf.upfronthosting.co.za>
In-reply-to
Content
Indeed, but not defining _DEBUG for debug compiling is not realistic.  Too many dependencies.  I am not even sure it would work, because if we bind with the debug libraries, but build with the "release" headers, it might break.  In any case it is not an option we have on the table at this moment.

As for the linking part, I am not sure I am following you.  Your runtime libraries and DLLs should not need to be linked to anything.  They may be dependent on the release msvcrt, and that is fine (like I said, we can live with the Python parts in release).  We have many other such libraries that are only in release mode (even when we build in debug).
History
Date User Action Args
2014-04-25 03:26:58Bangersetrecipients: + Banger, loewis, pitrou
2014-04-25 03:26:58Bangersetmessageid: <1398396418.9.0.778825554215.issue21292@psf.upfronthosting.co.za>
2014-04-25 03:26:58Bangerlinkissue21292 messages
2014-04-25 03:26:58Bangercreate