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 steve.dower
Recipients Joakim.Karlsson, loewis, r-englund, steve.dower, tim.golden, zach.ware
Date 2015-01-09.17:46:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1420825619.14.0.938861308691.issue22411@psf.upfronthosting.co.za>
In-reply-to
Content
Right, so when using python34_d.dll you need the _d.pyd versions (and if you're building your own .pyd you need to add the _d suffix too). There's nothing wrong with this difference, since the debug and release builds are subtly incompatible with each other, so the alternative is that you'd get random crashes when mixing them. Better off getting blatant errors that files can't be found.

Any option to install a debug build in 3.5 would obviously install a complete debug build - not just the one DLL.
History
Date User Action Args
2015-01-09 17:46:59steve.dowersetrecipients: + steve.dower, loewis, tim.golden, zach.ware, Joakim.Karlsson, r-englund
2015-01-09 17:46:59steve.dowersetmessageid: <1420825619.14.0.938861308691.issue22411@psf.upfronthosting.co.za>
2015-01-09 17:46:59steve.dowerlinkissue22411 messages
2015-01-09 17:46:58steve.dowercreate