Re: [Twisted-Python] Re: Twisted - Python 2.3 - Windows
At 07:05 PM 7/31/03 +0200, Thomas Heller wrote:
Cory Dodt <corydodt@yahoo.com> writes:
Subject: [Twisted-Python] Twisted - Python 2.3 - Windows
Hi,
anyone who knows when the first Python 2.3 build of twisted for windows will be available? Which version will it be?
I tried to build it myself but got into trouble. I first installed Cygwin and then tried 'setup.py build --compiler=mingw32' as per documentation, but I got an error message that Python itself is build with Visual Studio 6. I don't feel building python myself and I don't have VS6.
I'm with you man, I don't feel like building Python myself either. I have asked the appropriate list (http://mail.python.org/pipermail/distutils-sig/2003-July/003333.html ) about this problem. I also tried using distutils from CVS instead of the bundled copy with Python 2.3, and no luck.
It looks like the error occurs when an MSVCCompiler instance is created; I haven't yet figured out *why* such an instance is being created. I don't have 2.3 installed on Win32, so as an experiment, I added a 'raise' statement to 2.2's MSVCCompiler. If I specified compilation with msvc, I get the error I raised. If I specify mingw32, I don't. So, evidently 2.2's distutils don't create an MSVCCompiler instance when specifying mingw32. I can't fathom why 2.3 would do so.
On Thu, Jul 31, 2003 at 01:41:53PM -0400, Phillip J. Eby wrote:
It looks like the error occurs when an MSVCCompiler instance is created; I haven't yet figured out *why* such an instance is being created. I don't
Surely the resulting traceback tells you the line of code where it's being instantiated? --amk
Phillip J. Eby wrote:
It looks like the error occurs when an MSVCCompiler instance is created; I haven't yet figured out *why* such an instance is being created. I don't have 2.3 installed on Win32, so as an experiment, I added a 'raise' statement to 2.2's MSVCCompiler. If I specified compilation with msvc, I get the error I raised. If I specify mingw32, I don't. So, evidently 2.2's distutils don't create an MSVCCompiler instance when specifying mingw32. I can't fathom why 2.3 would do so.
Well, I figured out why. This was a bug in Twisted's setup.py, which has a function _check_header that is supposed to invoke the compiler on a tiny test module to make sure the module being built will build successfully. The new compiler is constructed with new_compiler(), but no arguments were passed to it; it was this invocation that fails with the error message I was getting. This bug was introduced some time ago; I'm not sure why I didn't see it before now. Using self.compiler instead worked (there's no need to call new_compiler() when it's already been done for you). C
participants (3)
-
A.M. Kuchling -
Cory Dodt -
Phillip J. Eby