Message241155
| Author | steve.dower |
|---|---|
| Recipients | Joakim.Karlsson, loewis, r-englund, steve.dower, tim.golden, zach.ware |
| Date | 2015-04-15.20:24:21 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1429129461.62.0.241254687226.issue22411@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
The 3.5 installer contains the option to install the debug binaries, so that side is solved and I'm closing this as fixed. In the video at https://www.youtube.com/watch?v=D9RlT06a1EI I demonstrate how you can build a debug EXE against a release python34.dll without issues (though you lose a bit of debugging support) - in short, use the compiler option to link against the release runtime. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-04-15 20:24:21 | steve.dower | set | recipients: + steve.dower, loewis, tim.golden, zach.ware, Joakim.Karlsson, r-englund |
| 2015-04-15 20:24:21 | steve.dower | set | messageid: <1429129461.62.0.241254687226.issue22411@psf.upfronthosting.co.za> |
| 2015-04-15 20:24:21 | steve.dower | link | issue22411 messages |
| 2015-04-15 20:24:21 | steve.dower | create | |