Re: problems compiling pyscopg2 on Windows with Python 2.6

On Wed, 30 Sep 2009, Chris Withers wrote:

> Jason Erickson wrote:
>> And if you are looking for pre-built binaries for windows, you can check 
>> here :)
>>     http://www.stickpeople.com/projects/python/psycopg/
>
> Do these require PostGreSQL DLLs to be on my machine? That's the experience I 
> had... I got DLL errors using the stickpeople binaries until I installed 
> PostGreSQL locally...

The build is statically linked against the libpq libraries, so no 
libpq.dll is required.  Interesting that it started working for you after 
installing PostgreSQL locally.  Did you try installing the VC2005 ATL 
Security Update, too?  I wonder if the PostgreSQL install installs what is 
missing...  What install package did you use to install Postgres?


> What would be ideal for me would be a statically linked .egg on PyPI. Any 
> chance of that happening? Would this need to be built for specific postgres 
> versions?

There's a chance of it happing, just need to understand .egg & PyPI :). 
The big thing I see there is does one tag along with the official package 
listed there, or create a package listing specific to win32.  Being 
combined with the official package would be ideal.  Also, someone 
recommended to me to format the web page so that easysetup could point to 
the page and download the package from that page.  This might be a good 
initial first step.

At one time, I was thinking about building different version for different 
Postgres versions, but it dawned on me that it doesn't make any sense to 
do that.  I my opinion, as long as you are using the latest libpq 
interface, you are good to go, as it is backwards compatible to versions 
quite a ways back (I believe the current stuff works at least as far back 
as the 7.4 line).  Unless others can come up with a good reason to build 
against an older libpq, I think using the latest libpq interface is best.


> cheers,
>
> Chris


-jason