psycopg2/lib
Daniele Varrazzo 74e6efd717 Raise TypeError instead of InterfaceError on bad params on connect()
TypeError is the standard Python error raised in this case:

    $ python -c "(lambda a: None)(b=10)"
    TypeError: <lambda>() got an unexpected keyword argument 'b'

We only used to raise InterfaceError when connect was used without
any parameter at all, so it's hard to think a program depending on
that design. Furthermore the function has always raised (and still
does) OperationalError too, if the bad argument is detected by the
libpq, and that cannot be changed because we can't tell the
difference from a normal connection error.
2012-09-26 11:55:21 +01:00
..
__init__.py Raise TypeError instead of InterfaceError on bad params on connect() 2012-09-26 11:55:21 +01:00
errorcodes.py Update all links to PostgreSQL docs to the current version. 2012-02-28 18:28:07 +02:00
extensions.py Fixed SQL_IN when getquoted() is called without prepare() 2012-09-24 16:55:01 +01:00
extras.py Info about hstore versions history moved from code to docs 2012-09-22 02:10:58 +01:00
pool.py Check the connection status before putting back into the pool 2011-08-09 11:44:30 +01:00
psycopg1.py A couple of fixes to psycopg1 2011-12-15 13:06:32 +00:00
tz.py Cache FixedOffsetTimezone instances 2012-01-30 13:27:40 +00:00