7 Commits

Author	SHA1	Message	Date
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
Daniele Varrazzo	32fae728b3	Dropped quirks in connection arguments handling ... Now connect() raises an exception instead of swallowing keyword arguments when a connection string is specified as well Closes ticket #131.	2012-09-25 23:46:46 +01:00
Daniele Varrazzo	98d6d96ee3	Fixed exception testing on Python 3 ... ...and so caught exceptions are local to the except suite in Py3. (Lo sapevate? Sapevatelo!)	2012-02-23 23:15:42 +00:00
Daniele Varrazzo	43daba38e7	Make Error and subclasses picklable ... Useful for multiprocessing interaction. Closes ticket #90.	2012-01-14 17:34:09 +00:00
Daniele Varrazzo	417203f68e	Added test to check connect() with no parameters	2011-11-17 21:51:24 +00:00
Daniele Varrazzo	625cc1b402	Escape parameters to the connection strings as required by PQconnectdb	2011-11-17 21:51:24 +00:00
Daniele Varrazzo	99ac79511c	Added test module to verify the dsn manipulation	2011-11-17 21:51:24 +00:00