[issue21292] C API in debug fails

Change by STINNER Victor : -- components: +C API ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue21292] C API in debug fails

Steve added the comment: 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

[issue21292] C API in debug fails

Martin v. Löwis added the comment: 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 t

[issue21292] C API in debug fails

Steve added the comment: A bit more info: - When building in debug you need the Pythonxx_d.lib. - This lib does not come with the normal install (or any other install). That part is fine and normal (you don't include debug libs with install). - To get that lib you have to build Python in debug

[issue21292] C API in debug fails

Changes by Antoine Pitrou : -- nosy: +loewis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue21292] C API in debug fails

Steve added the comment: It is under windows -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue21292] C API in debug fails

New submission from Steve: Although not a bug, it annoys me enough that it is a bug in my head! The problem is that trying to compile an application in debug that embeds Python fails. Case in point; we canned the idea of embedding Python (went with Lua) for that reason only. We did not have

[issue21292] C API in debug fails

Antoine Pitrou added the comment: Is that under Windows? -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Uns