[Django] #26065: psycopg2 __init__ reports an error: DLL load failed: The specified module could not be found

14 views
Skip to first unread message

Django

unread,
Jan 9, 2016, 9:24:34 PM1/9/16
to django-...@googlegroups.com
#26065: psycopg2 __init__ reports an error: DLL load failed: The specified module
could not be found
-------------------------+-------------------------------------------------
Reporter: | Owner:
alvigilegner |
Type: | Status: new
Uncategorized |
Component: | Version: 1.9
contrib.postgres | Keywords: psycopg2, Windows 10, __init___,
Severity: Normal | postgres
Triage Stage: | Has patch: 0
Unreviewed |
Easy pickings: 0 | UI/UX: 0
-------------------------+-------------------------------------------------
I am unable to use PostGresql with Django on my Windows 10 installation.
The error is traced back to __init__.py of psycopg2, line 50:
psycopg2._psycopg import BINARY, NUMBER, STRING, DATETIME, ROWID.

I suspect this is some kind of DLL incompatibility. I am using PostGres
9.2, Python 3.5.1, and Django 1.9 on a Windows 10 PC. Have tried to
install psycgp2 from pip and the exe file with the same result.

Does any one out there know of a combination of these three programs that
works? This issue has been reported on and off for years, but none of the
solutions that I have run across do not work for me.

--
Ticket URL: <https://code.djangoproject.com/ticket/26065>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Jan 10, 2016, 8:12:43 AM1/10/16
to django-...@googlegroups.com
#26065: psycopg2 __init__ reports an error: DLL load failed: The specified module
could not be found
-------------------------------------+-------------------------------------
Reporter: alvigilegner | Owner:
Type: Uncategorized | Status: closed
Component: contrib.postgres | Version: 1.9
Severity: Normal | Resolution: invalid
Keywords: psycopg2, Windows | Triage Stage:
10, __init___, postgres | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by shaib):

* status: new => closed
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
* resolution: => invalid


Old description:

> I am unable to use PostGresql with Django on my Windows 10 installation.
> The error is traced back to __init__.py of psycopg2, line 50:
> psycopg2._psycopg import BINARY, NUMBER, STRING, DATETIME, ROWID.
>
> I suspect this is some kind of DLL incompatibility. I am using PostGres
> 9.2, Python 3.5.1, and Django 1.9 on a Windows 10 PC. Have tried to
> install psycgp2 from pip and the exe file with the same result.
>
> Does any one out there know of a combination of these three programs that
> works? This issue has been reported on and off for years, but none of
> the solutions that I have run across do not work for me.

New description:

I am unable to use PostGresql with Django on my Windows 10 installation.
The error is traced back to `__init__.py` of psycopg2, `line 50:

psycopg2._psycopg import BINARY, NUMBER, STRING, DATETIME, ROWID`.

I suspect this is some kind of DLL incompatibility. I am using PostGres
9.2, Python 3.5.1, and Django 1.9 on a Windows 10 PC. Have tried to
install psycgp2 from pip and the exe file with the same result.

Does any one out there know of a combination of these three programs that
works? This issue has been reported on and off for years, but none of the
solutions that I have run across do not work for me.

--

Comment:

I sympathize with your hardships, and yet I see no problem with Django
reported here. There might be one if you were able to use psycopg2 from
Python outside Django, and only had a problem with Django, but I see
nothing like that in the report.

If you can show there actually is some problem with Django, feel free to
reopen. Otherwise, the Django issue tracker is not the place to ask for
help.

You can try the django-users mailing list, or some psycopg2 forums.

--
Ticket URL: <https://code.djangoproject.com/ticket/26065#comment:1>

Reply all
Reply to author
Forward
0 new messages