I just did a fresh build of Python 3.3.3 on OSX, upgrading from 3.3.2, didn’t
re-install psycopg2, and I’m able to connect via SQLAlchemy. So the issue
might be local to windows.
On Nov 24, 2013, at 5:39 PM, Michael Bayer wrote:
>
> On Nov 24, 2013, at 7:33 AM, Sibylle Koczian wrote:
>
>
On Nov 24, 2013, at 7:33 AM, Sibylle Koczian wrote:
> Hello,
>
> I'm using SQLAlchemy 0.8.3, psycopg2 2.5.1, Python 3.3.3 on Windows 7,
> PostgreSQL 9.3.1. No change to SQLAlchemy and psycopg2, update from Python
> 3.3.2 to 3.3.3 some days ago.
the error is emitted by psycopg2 so I’d try a f
Hello,
I'm using SQLAlchemy 0.8.3, psycopg2 2.5.1, Python 3.3.3 on Windows 7,
PostgreSQL 9.3.1. No change to SQLAlchemy and psycopg2, update from
Python 3.3.2 to 3.3.3 some days ago.
Today I get this when trying to use this combination:
Python 3.3.3 (v3.3.3:c3896275c0f6, Nov 18 2013, 21:19:
Hello,
I'm using SQLAlchemy 0.8.3, psycopg2 2.5.1, Python 3.3.3 on Windows 7,
PostgreSQL 9.3.1. No change to SQLAlchemy and psycopg2, update from
Python 3.3.2 to 3.3.3 some days ago.
Today I get this when trying to use this combination:
Python 3.3.3 (v3.3.3:c3896275c0f6, Nov 18 2013, 21:19:
