Hello,

I try to compile Python and several packages (like Numarray) with Visual
Studio 2005. I downloaded the last version of Python from Subversion,
and project files are provided for Visual Studio 2005. With some few
simple corrections, everything compile and Python run correctly.

Unfortunately, distutils does not support VisualStudio2005. I tried to
modify the file msvccompiler.py without success (this case requires to
support some changes of the Visual Studio 8 register for both Win32 and
Win64). So, I wonder if the integration of VisualStudio2005 in distutils
is scheduled in the Python developments or better, if someone has
experiences or patch to support VisualStudio2005 in distutils.

Thanks,
Mathieu.

mg schrieb:

Unfortunately, distutils does not support VisualStudio2005. I tried to
modify the file msvccompiler.py without success (this case requires to
support some changes of the Visual Studio 8 register for both Win32 and
Win64). So, I wonder if the integration of VisualStudio2005 in distutils
is scheduled in the Python developments or better, if someone has
experiences or patch to support VisualStudio2005 in distutils.

You shouldn't attempt to do that. Even if you manage to convince
distutils to use VS 2005 to compile your extension, the resulting
code may crash Python because of obscure incompatibilities between
the compiler that was used to compile Python (VS 2003) and the compiler
that was used to compile the extension (VS 2005).

Whether or not it will actually crash depends on obscure details
of the API that the extension uses.

Regards,
Martin

mg schrieb:

Unfortunately, distutils does not support VisualStudio2005. I tried to
modify the file msvccompiler.py without success (this case requires to
support some changes of the Visual Studio 8 register for both Win32 and
Win64). So, I wonder if the integration of VisualStudio2005 in distutils
is scheduled in the Python developments or better, if someone has
experiences or patch to support VisualStudio2005 in distutils.

You shouldn't attempt to do that. Even if you manage to convince
distutils to use VS 2005 to compile your extension, the resulting
code may crash Python because of obscure incompatibilities between
the compiler that was used to compile Python (VS 2003) and the compiler
that was used to compile the extension (VS 2005).

Whether or not it will actually crash depends on obscure details
of the API that the extension uses.

Regards,
Martin

Martin v. Löwis napisa³(a):

>
You shouldn't attempt to do that. Even if you manage to convince
distutils to use VS 2005 to compile your extension, the resulting
code may crash Python because of obscure incompatibilities between
the compiler that was used to compile Python (VS 2003) and the compiler
that was used to compile the extension (VS 2005).
>
Whether or not it will actually crash depends on obscure details
of the API that the extension uses.

Sure, but what if I succesfully compile Python with VS 2005? Hier ist
der Hund begraben, distutils cann't handle this compiler so I'll be
unable to compile any extension for my home-baken Python.

--
Jarek Zgoda
http://jpa.berlios.de/

I know the incompatibility problem to have Python compiled with one
compiler and packages with another one. Nevertheless, in my case, Python
is well compiled with VisualStudio2005 thank to project files provided
by Mr Python himself. So, Python is not yet ready to support completely
VisualStudio2005: Python can be compiled with VisualStudio2005 but a
VisualStudio2005-compiled-Python can not install additional packages.

So, if someone can help me or provides me a solution, I am very
interested ;-)

Martin v. Löwis wrote:

mg schrieb:
>

>
You shouldn't attempt to do that. Even if you manage to convince
distutils to use VS 2005 to compile your extension, the resulting
code may crash Python because of obscure incompatibilities between
the compiler that was used to compile Python (VS 2003) and the compiler
that was used to compile the extension (VS 2005).
>
Whether or not it will actually crash depends on obscure details
of the API that the extension uses.
>
Regards,
Martin
>

Jarek Zgoda schrieb:

Sure, but what if I succesfully compile Python with VS 2005? Hier ist
der Hund begraben, distutils cann't handle this compiler so I'll be
unable to compile any extension for my home-baken Python.

It sure can. Just open a "Visual Studio Command Prompt" (or whatever
its name), and make sure MSSdk and DISTUTILS_USE_SDK are both set.
Then distutils will use the compiler from PATH, rather than the
pre-configured one.

Regards,
Martin

mg schrieb:

I know the incompatibility problem to have Python compiled with one
compiler and packages with another one. Nevertheless, in my case, Python
is well compiled with VisualStudio2005 thank to project files provided
by Mr Python himself. So, Python is not yet ready to support completely
VisualStudio2005: Python can be compiled with VisualStudio2005 but a
VisualStudio2005-compiled-Python can not install additional packages.

As I just wrote in a different message: Make sure DISTUTILS_USE_SDK
and MSSdk are both set, and arrange PATH to point to the compiler to
want to use; then distutils will obey you.

Regards,
Martin

mg schrieb:

I know the incompatibility problem to have Python compiled with one
compiler and packages with another one. Nevertheless, in my case, Python
is well compiled with VisualStudio2005 thank to project files provided
by Mr Python himself. So, Python is not yet ready to support completely
VisualStudio2005: Python can be compiled with VisualStudio2005 but a
VisualStudio2005-compiled-Python can not install additional packages.

As I just wrote in a different message: Make sure DISTUTILS_USE_SDK
and MSSdk are both set, and arrange PATH to point to the compiler to
want to use; then distutils will obey you.

Regards,
Martin

Martin v. Löwis napisa³(a):

>
It sure can. Just open a "Visual Studio Command Prompt" (or whatever
its name), and make sure MSSdk and DISTUTILS_USE_SDK are both set.
Then distutils will use the compiler from PATH, rather than the
pre-configured one.

Thanks, didn't know that.

--
Jarek Zgoda
http://jpa.berlios.de/