for what it's worth...

usually I see errors in psycopg and other c-extended python libraries when 
the python and/or postgres versions got upgraded.  it can get tricky when 
you're using a virtualenv, because you need to rebuild the entire 
virtualenv - and sometimes people forget that.  ( i know i have )

one of the best tricks I've found is this:

on Python upgrades, even from x.x.y to x.x.y+1 , rebuild a new virtualenv 
for all your projects and reinstall every module.

also, go into the system's site-packages library and do a hard "delete" of 
psycopg/other modules with c-extensions.  don't "upgrade", but instead 
install fresh.

-- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to