sys.exec_prefix doesn't seem to reflect --exec-prefix path

[Ralph Heinkel]

Hi,

on my linux box there is a python version 2.7.5 installed in /usr/local.

Now I want to install the newer version 2.7.9, but in a different directory to 
avoid clashes with the current installation.

What I did was:

./configure --prefix /usr/local/Python-2.7.9 --exec-prefix 
/usr/local/Python-2.7.9
make
make install

Everything looks fine, Python is installed in the proper directory.

BUT: When I run /usr/local/Python-2.7.9/bin/python and do 'print 
sys.exec_prefix' it prints '/usr/local' instead of '/usr/local/Python-2.7.9'.

This has the effect that the old libraries of version 2.7.5 are used instead of 
the 2.7.9 ones.

The docs in https://docs.python.org/2/library/sys.html state that 
sys.exec_prefix will reflect the value given to option --exec-prefix at 
configuration time. Any idea what I did wrong? 

Thanks for your help,

Ralph
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: Compiling Python (modules) on 64bit Windows - which compiler suite?

[Ralph Heinkel]

> 
> See "Compiling 64-bit extension modules on Windows" at 
> . It applies to 
> non-Cython extensions as well.
> 
> MinGW-w64 also works, but you'll have to generate and use libpythonXX.a and 
> libmsvcr90.a link libraries.
> 
> Christoph

Thanks to everyone who has replied to my question.
Especially for the link/hint to use the .NET SDK which indeed seems to provide 
the right tools for 64bit compilation.
I'm going to try this and report back here.

Cheers,

Ralph
-- 
http://mail.python.org/mailman/listinfo/python-list

Compiling Python (modules) on 64bit Windows - which compiler suite?

[Ralph Heinkel]

Hi,

when processing our mass spectrometry data we are running against the
2GB memory limit on our 32 bit machines. So we are planning to move to
64bit. Downloading and installing the 64bit version of Python for
Windows is trivial, but how do we compile our own C extension? Visual C
++ 2008 express comes for free, but only compiles for 32 bit.

What has been used to compile the downloadable Python Win64 bit
version? Visual Studio professional?
The problem with the professional edition is that it is hard to obtain
and it is sort of out-of-date - nowadays everyone uses Visual Studio
2010 (or even 2011 coming soon). So if Visual Studio 2008 professional
is required for compiling 64bit modules, we would have to spend $1200
for a license which is actually rather out of date.

Any hints or suggestions are very welcome.

Thanks,

Ralph
-- 
http://mail.python.org/mailman/listinfo/python-list