[pywin32-bugs] [ pywin32-Bugs-3301132 ] Need VC 10 version of Python for Windows extensions

[SourceForge.net <no...@so...>]

Bugs item #3301132, was opened at 2011-05-13 03:40
Message generated for change (Comment added) made by mhammond
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3301132&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Martin Glynn (martymike)
Assigned to: Nobody/Anonymous (nobody)
Summary: Need VC 10 version of Python for Windows extensions

Initial Comment:
Background: have app that has Python embedded and we using the extensions in many scripts that we supply. Needed features in new MFC with VC10. Want to use Python 2.7. Python won't initialize unless same C run-time, so rebuilt python27.dll (and some others, but that seems all that is critical). We've done this before (at Python 2.8 with VC 9) but this time cannot import win32api. So thought we needed to rebuild that, too.
Using Python 2.7. Downloaded source for v 216.2. Try to build it using setup.py that came with it with installed Py 2.7. Fails trying to build perfmondata; appears to be looking for *.man files that do not exist. Decided to try again using rebuilt Python (VC10). Setup correctly identifies compiler and linker (cool!) but now failure occurs trying to load winapi. Tried rebuilding that using VS project file. Seems to build. Tried to run product on bare hope that that was all that was needed - failure importing _win32sysloader. Don't see how that gets rebuilt. Still can't get past perfmondata in setup.
Are we going about this the right way?

----------------------------------------------------------------------

>Comment By: Mark Hammond (mhammond)
Date: 2011-05-13 08:55

Message:
Things should be build with just "setup.py build" - the VS project files
are out of date and just act as a "container" for the list of source files
for each project.

Try doing "setup.py build --force" and paste the full error log.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3301132&group_id=78018