Thread: install on windows
I'm having hard time installing psycopg on windows. I have installed python 3.5, and yet psycopg2 can't find the installation. It has something to do with windows registry. I've tried some script, but it failed to register my python installation. Could you please help me? Thanks, Levente
Python 3.5 is not officially supported yet. It will be with the psycopg 2.6.2 release, which I hope to pack in a few days. Python 3.5 support is already in the maint_2_6 branch, if you can compile it from source, but I assume it will be easier for you to install Python 3.4 than compile psycopg. -- Daniele On Wed, Mar 23, 2016 at 10:22 AM, Levente <leventelist@gmail.com> wrote: > I'm having hard time installing psycopg on windows. I have installed > python 3.5, and yet psycopg2 can't find the installation. It has > something to do with windows registry. > > I've tried some script, but it failed to register my python installation. > > Could you please help me? > > Thanks, > Levente > > > -- > Sent via psycopg mailing list (psycopg@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/psycopg
Ummm... This is on the website: http://www.stickpeople.com/projects/python/win-psycopg/2.6.1/psycopg2-2.6.1.win32-py3.5.exe Lev On Wed, Mar 23, 2016 at 11:48 AM, Daniele Varrazzo <daniele.varrazzo@gmail.com> wrote: > Python 3.5 is not officially supported yet. It will be with the > psycopg 2.6.2 release, which I hope to pack in a few days. > > Python 3.5 support is already in the maint_2_6 branch, if you can > compile it from source, but I assume it will be easier for you to > install Python 3.4 than compile psycopg. > > -- Daniele > > On Wed, Mar 23, 2016 at 10:22 AM, Levente <leventelist@gmail.com> wrote: >> I'm having hard time installing psycopg on windows. I have installed >> python 3.5, and yet psycopg2 can't find the installation. It has >> something to do with windows registry. >> >> I've tried some script, but it failed to register my python installation. >> >> Could you please help me? >> >> Thanks, >> Levente >> >> >> -- >> Sent via psycopg mailing list (psycopg@postgresql.org) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/psycopg
On Wed, Mar 23, 2016 at 12:06 PM, Levente <leventelist@gmail.com> wrote: > Ummm... > > > This is on the website: > > http://www.stickpeople.com/projects/python/win-psycopg/2.6.1/psycopg2-2.6.1.win32-py3.5.exe > > Lev Ok right: I thought you were trying to use 'pip install'. In this case I don't know what's going on with your registry; someone else may. -- Daniele
Hmm, I can duplicate this issue. But investigating it more, it is not strictly a psycopg2 issue, either.
This change causes a problem for ALL 32bit extension installers on Python 3.5 that use the standard Python stub installer.
Briefly looking at the stub code, I believe the standard Python stub installer only recognizes registry keys in the format <major>.<minor>. The extra '-32' at the end of the registry key makes the installer ignore the key, never finding the Python installation.
Another package that uses the Python stub installer, pycurl, exhibits the same issues:
I'm not suggesting this, but a workaround is to rename the following registry key from:
SOFTWARE\WOW6432Node\Python\PythonCore\3.5-32
to:
SOFTWARE\WOW6432Node\Python\PythonCore\3.5
(ie, remove the '-32')
Install the extension, and then rename the registry back. Don't forget to rename it back!
Another workaround is to use the 64bit version of Python and Extensions.
-jason
On Wed, Mar 23, 2016 at 7:11 AM, Daniele Varrazzo <daniele.varrazzo@gmail.com> wrote:
On Wed, Mar 23, 2016 at 12:06 PM, Levente <leventelist@gmail.com> wrote:
> Ummm...
>
>
> This is on the website:
>
> http://www.stickpeople.com/projects/python/win-psycopg/2.6.1/psycopg2-2.6.1.win32-py3.5.exe
>
> Lev
Ok right: I thought you were trying to use 'pip install'. In this case
I don't know what's going on with your registry; someone else may.
-- Daniele
--
Sent via psycopg mailing list (psycopg@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/psycopg
On Wed, 23 Mar 2016 12:55:43 -0600 Jason Erickson <jerickso@stickpeople.com> wrote: > Hmm, I can duplicate this issue. But investigating it more, it is not > strictly a psycopg2 issue, either. > > As Levente noted, the installers use Windows registry keys to > determine the location of the Python installation. Between python > 3.4.x and 3.5.x, it looks like the registry key for 32bit Python was > changed from a format of 3.5 to 3.5-32. > > This change causes a problem for ALL 32bit extension installers on > Python 3.5 that use the standard Python stub installer. > > Briefly looking at the stub code, I believe the standard Python stub > installer only recognizes registry keys in the format > <major>.<minor>. The extra '-32' at the end of the registry key > makes the installer ignore the key, never finding the Python > installation. > > Another package that uses the Python stub installer, pycurl, exhibits > the same issues: > > https://bintray.com/artifact/download/pycurl/pycurl/pycurl-7.43.0.win32-py3.5.exe > > > > I'm not suggesting this, but a workaround is to rename the following > registry key from: > > SOFTWARE\WOW6432Node\Python\PythonCore\3.5-32 > > to: > > SOFTWARE\WOW6432Node\Python\PythonCore\3.5 > > > (ie, remove the '-32') > > Install the extension, and then rename the registry back. Don't > forget to rename it back! > > > Another workaround is to use the 64bit version of Python and > Extensions. Ok. Thanks. I have the same issue with python2.7. The problem might be that the default python download is for 32bit systems. Thanks again! Lev