On 4/08/2011 7:24 AM, Will Sadkin wrote:
So... Can someone tell me how to build our .pyd in VS2010 such that it doesn't have a manifest, and thus can be loaded by the Python2.7 interpreter?
You should be able to use the cmdline option MANIFEST:NO to the linker - that is what pywin32 does.
PS: Is there any growing pressure to make Python compatible with the latest compiler from Microsoft, now almost 2 years old?!?
Not really - there is a bit of a history of skipping every second release. The main problem is friction for extension authors targetting multiple Python versions and thereby forcing them to update their tool chain. This is slightly less of a problem if the free tools are used but still a PITA for people who need to use features not available in the free version.
As I understand it though, some of the manifest pain should go away with VS2010, so this could be a compelling reason for Python 3.3 - it's almost certainly not an option for anything already released using VC2008 (ie, I expect we will never see a VS2010 version of 2.7)
Cheers, Mark _______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
