Re: [sqlalchemy] Re: Python 3.1 + SQLAlchemy 0.6 or 0.7

2011-03-30 Thread Michael Bayer
On Mar 30, 2011, at 1:39 PM, Hans-Martin wrote: > On Mar 30, 7:13 pm, Michael Bayer wrote: >> well its not going to work there either most likely since we don't support >> connecting without a hostname, probably. You can't put "localhost" in there >> ? > > Doesn't work either, same error. Ad

[sqlalchemy] Re: Python 3.1 + SQLAlchemy 0.6 or 0.7

2011-03-30 Thread Hans-Martin
On Mar 30, 7:13 pm, Michael Bayer wrote: > well its not going to work there either most likely since we don't support > connecting without a hostname, probably.  You can't put "localhost" in there ? Doesn't work either, same error. Adding my system username (and password) then throws errors from

Re: [sqlalchemy] Re: Python 3.1 + SQLAlchemy 0.6 or 0.7

2011-03-30 Thread Michael Bayer
well its not going to work there either most likely since we don't support connecting without a hostname, probably. You can't put "localhost" in there ? On Mar 30, 2011, at 1:07 PM, Hans-Martin wrote: >> you'd need an @ sign in there perhaps: >> >> db://@/test > > Same error. But no big deal

[sqlalchemy] Re: Python 3.1 + SQLAlchemy 0.6 or 0.7

2011-03-30 Thread Hans-Martin
> you'd need an @ sign in there perhaps: > > db://@/test Same error. But no big deal, I can wait for psycopg2 support in Python 3.2. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com.

Re: [sqlalchemy] Re: Python 3.1 + SQLAlchemy 0.6 or 0.7

2011-03-30 Thread Michael Bayer
On Mar 30, 2011, at 12:42 PM, Hans-Martin wrote: > On Mar 30, 5:43 pm, Michael Bayer wrote: >> That's not an error I'm familiar with how to reproduce; it suggests an >> incorrect string passed to create_engine(). Working code with Python 3.2 >> plus pg8000 looks like: >> >> from sqlalchemy

[sqlalchemy] Re: Python 3.1 + SQLAlchemy 0.6 or 0.7

2011-03-30 Thread Hans-Martin
On Mar 30, 5:43 pm, Michael Bayer wrote: > That's not an error I'm familiar with how to reproduce; it suggests an > incorrect string passed to create_engine().   Working code with Python 3.2 > plus pg8000 looks like: > > from sqlalchemy import create_engine > > e = create_engine("postgresql+pg80

Re: [sqlalchemy] Re: Python 3.1 + SQLAlchemy 0.6 or 0.7

2011-03-30 Thread Michael Bayer
That's not an error I'm familiar with how to reproduce; it suggests an incorrect string passed to create_engine(). Working code with Python 3.2 plus pg8000 looks like: from sqlalchemy import create_engine e = create_engine("postgresql+pg8000://scott:tiger@localhost/test") print(e.execute("sel

[sqlalchemy] Re: Python 3.1 + SQLAlchemy 0.6 or 0.7

2011-03-30 Thread Hans-Martin
Sorry, I was not expecting it to work, just trying to follow your suggestion. SQLAlchemy Dev snapshot + pg8000 from http://pybrary.net/pg8000/dist/pg8000-py3-1.08.tar.gz throws this error: Traceback (most recent call last): File "set_meta_info_levels_0_1.py", line 60, in set_up_schemata()

Re: [sqlalchemy] Re: Python 3.1 + SQLAlchemy 0.6 or 0.7

2011-03-30 Thread Michael Bayer
On Mar 30, 2011, at 8:31 AM, Hans-Martin wrote: >> On Mar 21, 3:31 pm, Michael Bayer wrote: >> >>> Yeah psycopg2 with python 3 / sqlalchemy is not supported yet. The python >>> 3 supported version of psycopg2 came out like, in the past two weeks.It >>> will be 0.7 where its supported at

[sqlalchemy] Re: Python 3.1 + SQLAlchemy 0.6 or 0.7

2011-03-30 Thread Hans-Martin
> On Mar 21, 3:31 pm, Michael Bayer wrote: > > > Yeah psycopg2 with python 3 / sqlalchemy is not supported yet.  The python > > 3 supported version of psycopg2 came out like, in the past two weeks.    It > > will be 0.7 where its supported at all, hopefully soon as its a matter of > > setting u

[sqlalchemy] Re: Python 3.1 + SQLAlchemy 0.6 or 0.7

2011-03-21 Thread ddarko
Everything is clear - so wait for 0.7 finall. Meanwhile, would use pg8000. Pity that does not support pgarray :/ thx On Mar 21, 3:31 pm, Michael Bayer wrote: > Yeah psycopg2 with python 3 / sqlalchemy is not supported yet.  The python 3 > supported version of psycopg2 came out like, in the past