Psycopg2

Latest version: v2.9.9

Safety actively analyzes 630169 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 9 of 14

2.2.2

^^^^^^^^^^^^^^^^^^^^^^^^^^^

Bux fixes:

- the call to logging.basicConfig() in pool.py has been dropped: it was
messing with some projects using logging (and a library should not
initialize the logging system anyway.)
- psycopg now correctly handles time zones with seconds in the UTC offset.
The old register_tstz_w_secs() function is deprecated and will raise a
warning if called.
- Exceptions raised by the column iterator are propagated.
- Exceptions raised by executemany() iterators are propagated.

2.2.1

^^^^^^^^^^^^^^^^^^^^^^^^^^^

Bux fixes:

- psycopg now builds again on MS Windows.

2.2

-------------------------

This is the first release of the new 2.2 series, supporting not just one but
two different ways of executing asynchronous queries, thanks to Jan and Daniele
(with a little help from me and others, but they did 99% of the work so they
deserve their names here in the news.)

psycopg now supports both classic select() loops and "green" coroutine
libraries. It is all in the documentation, so just point your browser to
doc/html/advanced.html.

Other new features:

- truncate() method for lobjects.
- COPY functions are now a little bit faster.
- All builtin PostgreSQL to Python typecasters are now available from the
psycopg2.extensions module.
- Notifications from the backend are now available right after the execute()
call (before client code needed to call isbusy() to ensure NOTIFY
reception.)
- Better timezone support.
- Lots of documentation updates.

Bug fixes:

- Fixed some gc/refcounting problems.
- Fixed reference leak in NOTIFY reception.
- Fixed problem with PostgreSQL not casting string literals to the correct
types in some situations: psycopg now add an explicit cast to dates, times
and bytea representations.
- Fixed TimestampFromTicks() and TimeFromTicks() for seconds >= 59.5.
- Fixed spurious exception raised when calling C typecasters from Python
ones.

2.0.14

^^^^^^^^^^^^^^^^^^^^^^^^^^^^

New features:

- Support for adapting tuples to PostgreSQL arrays is now enabled by
default and does not require importing psycopg2.extensions anymore.
- "can't adapt" error message now includes full type information.
- Thank to Daniele Varrazzo (piro) psycopg2's source package now includes
full documentation in HTML and plain text format.

Bug fixes:

- No loss of precision when using floats anymore.
- decimal.Decimal "nan" and "infinity" correctly converted to PostgreSQL
numeric NaN values (note that PostgreSQL numeric type does not support
infinity but just NaNs.)
- psycopg2.extensions now includes Binary.

It seems we're good citizens of the free software ecosystem and that big
big big companies and people ranting on the pgsql-hackers mailing list
we'll now not dislike us. *g* (See LICENSE file for the details.)

2.0.13

^^^^^^^^^^^^^^^^^^^^^^^^^^^^

New features:

- Support for UUID arrays.
- It is now possible to build psycopg linking to a static libpq
library.

Bug fixes:

- Fixed a deadlock related to using the same connection with
multiple cursors from different threads.
- Builds again with MSVC.

2.0.12

^^^^^^^^^^^^^^^^^^^^^^^^^^^^

New features:

- The connection object now has a reset() method that can be used to
reset the connection to its default state.

Bug fixes:

- copy_to() and copy_from() now accept a much larger number of columns.
- Fixed PostgreSQL version detection.
- Fixed ZPsycopgDA version check.
- Fixed regression in ZPsycopgDA that made it behave wrongly when
receiving serialization errors: now the query is re-issued as it
should be by propagating the correct exception to Zope.
- Writing "large" large objects should now work.

Page 9 of 14

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.