distutils fix for building Zope against Python 2.4.1c1
http://mail.python.org/pipermail/python-checkins/2005-March/045185.html Note that I also could not build PyWin32 against 2.4.1c1 and I suspect this was the same problem. (Still checking to see if this change fixes the PyWin32 build for me.) In any case, this change should also make it to the trunk, right? Trent -- Trent Mick TrentM@ActiveState.com
[Trent Mick wrote]
http://mail.python.org/pipermail/python-checkins/2005-March/045185.html
Note that I also could not build PyWin32 against 2.4.1c1 and I suspect this was the same problem. (Still checking to see if this change fixes the PyWin32 build for me. ...
It doesn't. Investigating... Trent -- Trent Mick TrentM@ActiveState.com
[Trent Mick wrote]
[Trent Mick wrote]
http://mail.python.org/pipermail/python-checkins/2005-March/045185.html
Note that I also could not build PyWin32 against 2.4.1c1 and I suspect this was the same problem. (Still checking to see if this change fixes the PyWin32 build for me. ...
It doesn't. Investigating...
Investigation has turned up that I cannot keep my Python trees straight. That patch *does* fix building PyWin32 against 2.4.1c1. Cheers, Trent -- Trent Mick TrentM@ActiveState.com
[Trent Mick]
http://mail.python.org/pipermail/python-checkins/2005-March/045185.html
Note that I also could not build PyWin32 against 2.4.1c1 and I suspect this was the same problem. (Still checking to see if this change fixes the PyWin32 build for me.)
Be sure to speak up if it doesn't! Any build that invokes the C compiler often on Windows would have the same problem.
In any case, this change should also make it to the trunk, right?
Don't think it's needed on HEAD. As the checkin comment said: This doesn't appear to be an issue on the HEAD (MSVCCompiler initializes itself via __init__() on the HEAD). I verified by building Zope with unaltered HEAD too, and had no problem with that.
Tim Peters wrote:
Don't think it's needed on HEAD. As the checkin comment said:
This doesn't appear to be an issue on the HEAD (MSVCCompiler initializes itself via __init__() on the HEAD).
I verified by building Zope with unaltered HEAD too, and had no problem with that.
Are you sure your HEAD is current? My copy of msvccompiler.py 1.67 reads def __init__ (self, verbose=0, dry_run=0, force=0): CCompiler.__init__ (self, verbose, dry_run, force) self.__version = get_build_version() if self.__version >= 7: self.__root = r"Software\Microsoft\VisualStudio" self.__macros = MacroExpander(self.__version) else: self.__root = r"Software\Microsoft\Devstudio" self.initialized = False def initialize(self): self.__paths = self.get_msvc_paths("path") ... Regards, Martin
[Tim]
Don't think it's needed on HEAD. As the checkin comment said:
This doesn't appear to be an issue on the HEAD (MSVCCompiler initializes itself via __init__() on the HEAD).
I verified by building Zope with unaltered HEAD too, and had no problem with that.
[Martin]
Are you sure your HEAD is current?
Of course I was sure. I was also wrong about that, but I resent the implication that I wasn't sure <wink>. I'll port the fix sometime this weekend. Thanks!
participants (3)
-
"Martin v. Löwis" -
Tim Peters -
Trent Mick