This project is archived and is in readonly mode.
Psycopg2 Win Installer Not Working for 32-bit install on 64-bit machine
Reported by Niel | August 20th, 2013 @ 05:48 AM
Hello, good folks at psycopg.
Just tried installing psycopg2 for Windows with the installers located at:
Windows 7 (64-bit)
Python 3.3 64-bit
Python 3.3 32-bit (another install)
So the installer for psycopg2 for the Py 3.3 64-bit seems to have worked fine.
The psycopg2 installer used for the 32-bit version, however, fails. The installer finds the appropriate Py 3.3 32-bit version just fine. But then, after continuing to the actual install, it simply fails, and Windows tries to find a solution, without any luck. I can only assume that it's because it's trying to install to a 64-bit machine, but I pray that is NOT the problem. WHY:
I need 32-bit Python to use the OSGeo4W collection of GIS libraries. Using those GIS libs fails with 64-bit Python (at least 3.3). So if I can't link postgres/postgis to python, then i'm stuck.
Any help would be MOST APPRECIATED, as I have spent the last 30 hours or so trying to get geodjango operating under django and I've about lost my patience (and perhaps my mind). Have tried Spatialite and MySQL and have run into other issues. Oh, how I wish I were using Linux again. But i'm stuck on Windows for the time being, so I trudge on... Please, for the love of god, don't make me resort to the Oracle db. Help?!
Thanks much in advance... and more thanks to follow if any help is provided.
Comments and changes to this ticket
I've forwarded a message to Jason, who is the kind person providing the Windows builds. He may be able to point you in the right direction.
For what I recall anyway the windows installer is just a glorified .zip, so you can just unpack its content and copy it in the pythonpath.
The 32bit install does work on a 64bit OS, so the (good?) news is that is not the issue.
Since the installer initially finds the Python 3.3 directory, I am assuming you are using the Python 3.3 distribution from python.org, correct?
From your description, it sounds like the installer is crashing before completing. Can you inspect the windows event log (Applications) to see if there is any useful information there? Many times there isn't, but sometimes we get lucky :).
With the Windows 7 OS, do you have any other language packs installed and 'running'?
What other python packages have you installed? I am interested in binary distribution packages that have an installer that uses the default python installation manager like psycopg2.
Can you give me a brief description of additional programs that are installed on this computer that are not common?
As an option, you can extract the package from the exe using an unzip utility (ie. 7zip), as Daniele mentioned. Inside the exe, there is a directory called PLATLIB that has the psycopg2 directory and .egg-info file. Extract the contents of the PLATLIB directory to your python site-packages directory (ie, C:\Python33\Lib\site-packages)
I posted the following reply yesterday as an attachment, and I thought it was sent, but I guess it didn't. So here it is in its entirety:
Gentlemen (Daniele and Jason, and any others -- including ladies -- involved)
Thanks very much for your timely replies and effort. I'll answer your (Jason's) questions as best i can.
Windows 7 64-bit
Python 3.3 64-bit (your installer WORKS)
Python 3.3 32-bit (your installer does NOT work)
Python 2.7 32-bit (your installer does NOT work)
All these Python installs are from Python.org
As a possible avenue, i tried another python version (2.7) just to see if it was only that Py3.3 32-bit installer that was failing. The installer for Py2.7 32-bit also failed. During the "pre-install" they both (all) find the appropriate installation of Python, showing the appropriate path. But, after clicking NEXT to begin the actual installation, almost immediately, the 32-bit versions fail. I do get an Error in the windows event log (applications section), which i've (tried) to include below, but the data given seems rather general. Don't know if it will help.
I haven't tried any of the other 32-bit Pythons and installers, but my guess is that they will have problems too.
Other Python packages: Only Django. It was installed via Pip, not the "windowy" python installer.
Other language packs: NO (not that i am aware of)
"Strange" Apps: I did recently install the ENTIRE OSGeo4W package. That's about the only thing that might be "abnormal." MySQL? Adobe apps? Those all seem fairly standard. I have several other items but i doubt they have any sort of interference with this.
Manually Extracting The Package from the EXE: That is good to know that i can actually do that. I'll keep that in mind for the future, but as for now i don't need to, because:
I FOUND AN INSTALLER THAT WORKED:
The installer found here for the Py3.3 32-bit version worked on my computer. I did not try any of the others.
That's a rather impressive repository of installers. I found a link to it buried in a single response in a StackOverflow thread. Maybe you should link to that page for the few individuals who have problems via the installers you provide? I'd like to see your efforts become fool-proof (for fools such as myself), to minimize or to at least lessen the awful amount of time these endeavors can take.
So i currently have PostgreSQL up and running! Very cool! It only took me about 30+ hours of work over 2+ days to get django and geodjango fully working. Maybe i should not have decided to return to independent web-work?
THANKS much for your efforts. If there's anything i can do to further help (any tests, etc.) let me know. I was so happy to actually find a sort of "help-desk" for one of these aspects of installation. I wish that existed for all parts of the process.
WINDOWS EVENT LOG: (for the attempt at the Py2.7 version)
Event General Data:
Faulting application name: psycopg2-2.5.1.win32-py2.7-pg9.2.4-release.exe, version: 0.0.0.0, time stamp: 0x49819995
Faulting module name: psycopg2-2.5.1.win32-py2.7-pg9.2.4-release.exe, version: 0.0.0.0, time stamp: 0x49819995
Exception code: 0xc0000417
Fault offset: 0x000086dc
Faulting process id: 0x1a5c
Faulting application start time: 0x01ce9de84ba45971
Faulting application path: C:\Users\TJB\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5\8M77H6JH\psycopg2-2.5.1.win32-py2.7-pg9.2.4-release.exe
Faulting module path: C:\Users\TJB\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5\8M77H6JH\psycopg2-2.5.1.win32-py2.7-pg9.2.4-release.exe
Report Id: 8c3eb5c7-09db-11e3-b868-e8393549264e
- Provider [ Name] Application Error - EventID 1000 [ Qualifiers] 0 Level 2 Task 100 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2013-08-20T21:00:31.000000000Z EventRecordID 44815 Channel Application Computer TJB-HP Security
psycopg2-2.5.1.win32-py2.7-pg9.2.4-release.exe 0.0.0.0 49819995 psycopg2-2.5.1.win32-py2.7-pg9.2.4-release.exe 0.0.0.0 49819995 c0000417 000086dc 1a5c 01ce9de84ba45971 C:\Users\TJB\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5\8M77H6JH\psycopg2-2.5.1.win32-py2.7-pg9.2.4-release.exe C:\Users\TJB\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5\8M77H6JH\psycopg2-2.5.1.win32-py2.7-pg9.2.4-release.exe 8c3eb5c7-09db-11e3-b868-e8393549264e
On Wed, Aug 21, 2013 at 11:48 PM, Lighthouse <firstname.lastname@example.org> wrote:
> So i currently have PostgreSQL up and running! Very cool! It only took me about 30+ hours of work over 2+ days to get django and geodjango fully working. Maybe i should not have decided to return to independent web-work?
Maybe you should have avoided to try to do web work on windows.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
WARNING: the informations in this tracker are archived. Please submit new tickets or comments to the new tracker.
Psycopg is the most used PostgreSQL adapter for the Python programming language. At the core it fully implements the Python DB API 2.0 specifications. Several extensions allow access to many of the features offered by PostgreSQL.