2010/1/20 James William Pye li...@jwp.name:
On Jan 20, 2010, at 12:27 PM, Magnus Hagander wrote:
Well, it needs the version to match it to the DLL name. For python
2.6, it needs python26.dll. But yes, there should probably be some way
to ask python itself about that - that would be the
Matt bsg...@gmail.com writes:
Attempting to build 8.5 alpha on Windows XP (MSVC 2005) with Python support.
Path to local interpreter added to config.pl (C:\Python), but message is
presented:
Could not determine python version from path at build.pl line 38
Do the build scripts attempt to
On Wed, Jan 20, 2010 at 18:59, Tom Lane t...@sss.pgh.pa.us wrote:
Matt bsg...@gmail.com writes:
Attempting to build 8.5 alpha on Windows XP (MSVC 2005) with Python support.
Path to local interpreter added to config.pl (C:\Python), but message is
presented:
Could not determine python
Magnus Hagander mag...@hagander.net writes:
Or we'd welcome a patch for a smarter way to detect the version ;)
This particular code doesn't look like it really needs to know the
*version*. What it wants is the full pathname of the python.lib file
that goes with the python executable. Isn't
On Wed, Jan 20, 2010 at 20:24, Tom Lane t...@sss.pgh.pa.us wrote:
Magnus Hagander mag...@hagander.net writes:
Or we'd welcome a patch for a smarter way to detect the version ;)
This particular code doesn't look like it really needs to know the
*version*. What it wants is the full pathname of
On Jan 20, 2010, at 12:27 PM, Magnus Hagander wrote:
Well, it needs the version to match it to the DLL name. For python
2.6, it needs python26.dll. But yes, there should probably be some way
to ask python itself about that - that would be the non-naive method.
But as long as python is
