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 jbit
Recipients cgrebeld, jbit, lemburg, loewis, lylefile, stutzbach
Date 2010-08-01.22:09:44
SpamBayes Score 0.0062569696
Marked as misclassified No
Message-id <1280700592.37.0.143813951317.issue1303434@psf.upfronthosting.co.za>
In-reply-to
Content
Right now if you have any moderately complex Python based application (or extension set) the only way to easily debug it on windows is by building Python yourself, which is a horrible solution since it means you may end up with a subtly different version to what your crash dump is against.
While including the PDB in the MSI distribution would require a patch (and might not be the best solution since 99% of people won't need it), copying the PDB to some place does not, so I'm not sure why this hasn't been done years ago.
Even if it's not in a super easy-to-find place (ie: not on the download page), placing the PDB somewhere will greatly help developers who need to debug Python internals in visual studio.
History
Date User Action Args
2010-08-01 22:09:52jbitsetrecipients: + jbit, lemburg, loewis, lylefile, stutzbach, cgrebeld
2010-08-01 22:09:52jbitsetmessageid: <1280700592.37.0.143813951317.issue1303434@psf.upfronthosting.co.za>
2010-08-01 22:09:45jbitlinkissue1303434 messages
2010-08-01 22:09:45jbitcreate