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 Inverness
Recipients Inverness
Date 2011-11-02.01:17:13
SpamBayes Score 3.73308e-06
Marked as misclassified No
Message-id <1320196634.59.0.302796026714.issue13320@psf.upfronthosting.co.za>
In-reply-to
Content
I am using a custom Python executable for an application I'm developing. I also build PYDs to extend this Python environment. I decided to upgrade them and my executable to use Visual C++ 10 while the Python DLL and other third party PYDs, specifically wxPython, continued to use Visual C++ 9. Doing this did not cause an issue in and of itself, however, my wxPython release, but not debug, PYDs were failing to load the VC9 CRT.

I discovered this is a result of MSVCCompiler._remove_visual_c_ref() being called in the module disutils.msvc9compiler. I had to comment out this line in order to rebuild wxPython and get my program running correctly.

I'm requesting this feature of the compiler be made optional.
History
Date User Action Args
2011-11-02 01:17:14Invernesssetrecipients: + Inverness
2011-11-02 01:17:14Invernesssetmessageid: <1320196634.59.0.302796026714.issue13320@psf.upfronthosting.co.za>
2011-11-02 01:17:13Invernesslinkissue13320 messages
2011-11-02 01:17:13Invernesscreate