Thread: Psycopg 2.7.4 released
Good afternoon, we have released Psycopg version 2.7.4. You will find a few bug fixes in the release, and an important change in the Wheels packages. In short, installing the 'psycopg2' package from binary will now raise a warning on import: if you still want to install from binary you should now install the 'psycopg2-binary' package (this is only the package name to ask pip, no change is required to the Python import statements). All the details of the story are available at: <http://initd.org/psycopg/articles/2018/02/08/psycopg-274-released/>. This is the summary of the bugs fixed in this release: - Moving away from installing the wheel package by default. Packages installed from wheel raise a warning on import. Added package 'psycopg2-binary' to install from wheel instead (ticket #543). - Convert fields names into valid Python identifiers in 'NamedTupleCursor' (ticket #211). - Fixed Solaris 10 support (ticket #532). - 'cursor.mogrify()' can be called on closed cursors (ticket #579). - Fixed setting session characteristics in corner cases on autocommit connections (ticket #580). - Fixed 'MinTimeLoggingCursor' on Python 3 (ticket #609). - Fixed parsing of array of points as floats (ticket #613). - Fixed '__libpq_version__' building with libpq >= 10.1 (ticket 632). - Fixed 'rowcount' after 'executemany()' with 'RETURNING' statements (ticket 633). - Fixed compatibility problem with pypy3 (ticket #649). - Wheel packages compiled against PostgreSQL 10.1 libpq and OpenSSL 1.0.2n. - Wheel packages for Python 2.6 no more available (support dropped from wheel building infrastructure). Happy hacking! ---- Psycopg is the most popular PostgreSQL adapter for the Python programming language. At its core it fully implements the Python DB API 2.0 specifications. Several extensions allow access to many of the features offered by PostgreSQL.
On Thu, Feb 08, 2018 at 03:29:26PM +0000, Daniele Varrazzo wrote: > Good afternoon, > > we have released Psycopg version 2.7.4. Kudos! :) Best, David. -- David Fetter <david(at)fetter(dot)org> http://fetter.org/ Phone: +1 415 235 3778 Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
Hi Daniele, thanks for the new release.
Fantastic work as usual :)
Currently I list psycopg2>=2.7.3.
![](https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif)
On 8 February 2018 at 15:29, Daniele Varrazzo <daniele.varrazzo@gmail.com> wrote:
Good afternoon,
we have released Psycopg version 2.7.4.
You will find a few bug fixes in the release, and an important change
in the Wheels packages. In short, installing the 'psycopg2' package
from binary will now raise a warning on import: if you still want to
install from binary you should now install the 'psycopg2-binary'
package (this is only the package name to ask pip, no change is
required to the Python import statements). All the details of the
story are available at:
<http://initd.org/psycopg/articles/2018/02/08/psycopg- 274-released/>.
This is the summary of the bugs fixed in this release:
- Moving away from installing the wheel package by default.
Packages installed from wheel raise a warning on import. Added package
'psycopg2-binary' to install from wheel instead (ticket #543).
- Convert fields names into valid Python identifiers in
'NamedTupleCursor' (ticket #211).
- Fixed Solaris 10 support (ticket #532).
- 'cursor.mogrify()' can be called on closed cursors (ticket #579).
- Fixed setting session characteristics in corner cases on autocommit
connections (ticket #580).
- Fixed 'MinTimeLoggingCursor' on Python 3 (ticket #609).
- Fixed parsing of array of points as floats (ticket #613).
- Fixed '__libpq_version__' building with libpq >= 10.1 (ticket 632).
- Fixed 'rowcount' after 'executemany()' with 'RETURNING' statements
(ticket 633).
- Fixed compatibility problem with pypy3 (ticket #649).
- Wheel packages compiled against PostgreSQL 10.1 libpq and OpenSSL 1.0.2n.
- Wheel packages for Python 2.6 no more available (support dropped
from wheel building infrastructure).
Happy hacking!
----
Psycopg is the most popular PostgreSQL adapter for the Python
programming language. At its core it fully implements the Python DB
API 2.0 specifications. Several extensions allow access to many of the
features offered by PostgreSQL.
--
--
Federico Campoli
Hove, East Sussex, UK, Planet Earth, The Milky Way Galaxy
/*******************************
There's no point being grown-up if you can't be childish sometimes.
(The fourth Doctor)
http://www.pgdba.co.uk
*******************************/
Federico Campoli
Hove, East Sussex, UK, Planet Earth, The Milky Way Galaxy
/*******************************
There's no point being grown-up if you can't be childish sometimes.
(The fourth Doctor)
http://www.pgdba.co.uk
*******************************/
On 8 Feb 2018 7:04 p.m., "Federico" <rotellaro@gmail.com> wrote:
ThanksHi Daniele, thanks for the new release.Fantastic work as usual :)I was just wondering how can I manage this separation in the setup.py (install_requires argument).Currently I list psycopg2>=2.7.3.Shall I follow the pattern and create two different source packages or do you recommend a different approach?FedericoOn 8 February 2018 at 15:29, Daniele Varrazzo <daniele.varrazzo@gmail.com> wrote:Good afternoon,
we have released Psycopg version 2.7.4.
You will find a few bug fixes in the release, and an important change
in the Wheels packages. In short, installing the 'psycopg2' package
from binary will now raise a warning on import: if you still want to
install from binary you should now install the 'psycopg2-binary'
package (this is only the package name to ask pip, no change is
required to the Python import statements). All the details of the
story are available at:
<http://initd.org/psycopg/articles/2018/02/08/psycopg-274- released/>.
This is the summary of the bugs fixed in this release:
- Moving away from installing the wheel package by default.
Packages installed from wheel raise a warning on import. Added package
'psycopg2-binary' to install from wheel instead (ticket #543).
- Convert fields names into valid Python identifiers in
'NamedTupleCursor' (ticket #211).
- Fixed Solaris 10 support (ticket #532).
- 'cursor.mogrify()' can be called on closed cursors (ticket #579).
- Fixed setting session characteristics in corner cases on autocommit
connections (ticket #580).
- Fixed 'MinTimeLoggingCursor' on Python 3 (ticket #609).
- Fixed parsing of array of points as floats (ticket #613).
- Fixed '__libpq_version__' building with libpq >= 10.1 (ticket 632).
- Fixed 'rowcount' after 'executemany()' with 'RETURNING' statements
(ticket 633).
- Fixed compatibility problem with pypy3 (ticket #649).
- Wheel packages compiled against PostgreSQL 10.1 libpq and OpenSSL 1.0.2n.
- Wheel packages for Python 2.6 no more available (support dropped
from wheel building infrastructure).
Happy hacking!
----
Psycopg is the most popular PostgreSQL adapter for the Python
programming language. At its core it fully implements the Python DB
API 2.0 specifications. Several extensions allow access to many of the
features offered by PostgreSQL.
----
Federico Campoli
Hove, East Sussex, UK, Planet Earth, The Milky Way Galaxy
/*******************************
There's no point being grown-up if you can't be childish sometimes.
(The fourth Doctor)
http://www.pgdba.co.uk
*******************************/
Sorry, wrong send earlier...
On 8 Feb 2018 7:04 p.m., "Federico" <rotellaro@gmail.com> wrote:
I was just wondering how can I manage this separation in the setup.py (install_requires argument).Currently I list psycopg2>=2.7.3.Shall I follow the pattern and create two different source packages or do you recommend a different approach?
If binary packages work as expected you may just use that as a dependency, so "psycopg2-binary>=2.7.3" should do.
But now it occurs to me that the choice of not releasing a source package under psycopg2-binary was probably wrong: if you update your requirements as above, installation would fail if the user has an old pip version, or a non glibc architecture (e.g. Linux Alpine).
I'll create the missing package tomorrow morning. Once done, if your app is not a multithread program also using the system ssh, depending on binary is enough, I don't see reason for two packages.
Cheers
-- Daniele
Tested on my pc and on Travis CI.
So far so good :)On 8 February 2018 at 19:16, Daniele Varrazzo <daniele.varrazzo@gmail.com> wrote:
Sorry, wrong send earlier...On 8 Feb 2018 7:04 p.m., "Federico" <rotellaro@gmail.com> wrote:I was just wondering how can I manage this separation in the setup.py (install_requires argument).Currently I list psycopg2>=2.7.3.Shall I follow the pattern and create two different source packages or do you recommend a different approach?If binary packages work as expected you may just use that as a dependency, so "psycopg2-binary>=2.7.3" should do.But now it occurs to me that the choice of not releasing a source package under psycopg2-binary was probably wrong: if you update your requirements as above, installation would fail if the user has an old pip version, or a non glibc architecture (e.g. Linux Alpine).I'll create the missing package tomorrow morning. Once done, if your app is not a multithread program also using the system ssh, depending on binary is enough, I don't see reason for two packages.Cheers-- Daniele
--
--
Federico Campoli
Hove, East Sussex, UK, Planet Earth, The Milky Way Galaxy
/*******************************
There's no point being grown-up if you can't be childish sometimes.
(The fourth Doctor)
http://www.pgdba.co.uk
*******************************/
Federico Campoli
Hove, East Sussex, UK, Planet Earth, The Milky Way Galaxy
/*******************************
There's no point being grown-up if you can't be childish sometimes.
(The fourth Doctor)
http://www.pgdba.co.uk
*******************************/
On Thu, Feb 08, 2018 at 03:29:26PM +0000, Daniele Varrazzo wrote: > we have released Psycopg version 2.7.4. > - Fixed setting session characteristics in corner cases on autocommit connections (ticket #580). Many thanks, Daniele, I will report as soon as 2.7.4 becomes available on Debian. Best, Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
On Thu, Feb 08, 2018 at 03:29:26PM +0000, Daniele Varrazzo wrote: > - Fixed setting session characteristics in corner cases on autocommit connections (ticket #580). It seems to work for me. Thanks, Karsten -- GPG key ID E4071346 @ eu.pool.sks-keyservers.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346