Re: [HACKERS] PATCH: Compiling PostgreSQL using ActiveState Python 3.2

2011-08-18 Thread Ashesh Vashi
On Thu, Aug 18, 2011 at 5:25 PM, Peter Eisentraut wrote: > On tor, 2011-08-18 at 14:51 +0530, Ashesh Vashi wrote: > > Please ignore the previous patch. > > Please find the updated patch. > > Committed more or less like that. > Thanks > > In passing I also fixed the build with Python 3 on Windows

Re: [HACKERS] PATCH: Compiling PostgreSQL using ActiveState Python 3.2

2011-08-18 Thread Peter Eisentraut
On tor, 2011-08-18 at 14:51 +0530, Ashesh Vashi wrote: > Please ignore the previous patch. > Please find the updated patch. Committed more or less like that. In passing I also fixed the build with Python 3 on Windows, which apparently never worked before. But I suppose you have been referring to

Re: [HACKERS] PATCH: Compiling PostgreSQL using ActiveState Python 3.2

2011-08-18 Thread Ashesh Vashi
Please ignore the previous patch. Please find the updated patch. -- Thanks & Regards, Ashesh Vashi EnterpriseDB INDIA: Enterprise PostgreSQL Company *http://www.linkedin.com/in/asheshvashi* On Thu, Aug 18, 2011 at 12:57 P

Re: [HACKERS] PATCH: Compiling PostgreSQL using ActiveState Python 3.2

2011-08-18 Thread Ashesh Vashi
On Thu, Aug 18, 2011 at 1:25 AM, Tom Lane wrote: > Peter Eisentraut writes: > > On ons, 2011-08-17 at 13:20 -0400, Tom Lane wrote: > >> It's not immediately apparent to me why we should think that > >> get_python_lib is less trustworthy than LIBPL; but if someone > >> can make that case, I don't

Re: [HACKERS] PATCH: Compiling PostgreSQL using ActiveState Python 3.2

2011-08-17 Thread Tom Lane
Peter Eisentraut writes: > On ons, 2011-08-17 at 13:20 -0400, Tom Lane wrote: >> It's not immediately apparent to me why we should think that >> get_python_lib is less trustworthy than LIBPL; but if someone >> can make that case, I don't have any objection to this part of >> the patch. > The issu

Re: [HACKERS] PATCH: Compiling PostgreSQL using ActiveState Python 3.2

2011-08-17 Thread Peter Eisentraut
On ons, 2011-08-17 at 13:20 -0400, Tom Lane wrote: > FWIW, all three python installations I have handy (2.7 on Fedora 14, 2.7 > on OS X Lion, 2.5 on HPUX) produce the same result from either of > > python -c "from distutils.sysconfig import get_python_lib as f; import os; > print(os.path.join(f(p

Re: [HACKERS] PATCH: Compiling PostgreSQL using ActiveState Python 3.2

2011-08-17 Thread Tom Lane
Peter Eisentraut writes: > On ons, 2011-08-17 at 18:28 +0530, Ashesh Vashi wrote: >> When I tried to figure out the exact reason for the failure, I found that: >> 1. 'python_configdir' variable is hardcoded, instead it should use the >> configuration 'LIBPL'. > That looks reasonable. My Debian i

Re: [HACKERS] PATCH: Compiling PostgreSQL using ActiveState Python 3.2

2011-08-17 Thread Peter Eisentraut
On ons, 2011-08-17 at 18:28 +0530, Ashesh Vashi wrote: > I am trying to build PostgreSQL 9.1beta3 using the ActiveState Python 3.2. > It did not compile successfully. Note that building against Python 3.2 works at least on Debian, so this is not a universal problem. It appears to have to do with