Changes between Initial Version and Version 1 of Ticket #26065


Ignore:
Timestamp:
Jan 10, 2016, 7:10:46 AM (8 years ago)
Author:
Shai Berger
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.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #26065

    • Property Resolution → invalid
    • Property Status new → closed

  • Ticket #26065 – Description

    initial v1  
    1 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.
     1I 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`.
    22
    33I 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. 
Back to Top