• psycopg3 packaging: need new version of cython3 (and psycopg2)

    From Tomasz Rybak@21:1/5 to All on Fri Oct 1 21:10:02 2021
    Hello everyone.
    I'm working on packaging of psycopg3 (ITP #994860, home page https://www.psycopg.org/psycopg3/), which is successor of psycopg2
    (maintained by team), supporting Python3 features like asycio
    and with new architecture.

    Current upstream version is 3.0.beta1, beta2 in preparation.
    When preparing package, I made sure it's lintian-clean; it's also
    running tests (some are failing - not sure if this is problem
    with package or recently-uploaded PostgreSQL 14).
    There are still some issues I'd like to fix before uploading though.

    Psycopg3 differs from psycopg2: it consists of 3 modules.
    Two of them (psycopg and psycopg_pool) are pure Python
    so I intend to make them arch: all. They might also support
    PyPy, but I haven't yet succeeded in doing so.
    They use ctypes to talk to libpq for PostgreSQL communication,
    which makes it slower than psycopg2.

    Third module, psycopg_c, uses Cython to build code communicating
    with libpq, which makes it faster than ctypes. But it requires
    cython 3.0.alpha5. Currently Debian has cython3 0.29.21 (and
    cython 0.29.14); latest stable upstream version is 0.29.24
    (psycopg3 does not work with it - I checked) and development version
    is 3.0.alpha9. So my question is - which route to take now?

    Cython is team's package and it could use some attention. It was
    not updated in 11 months, uses really old debhelper (7),
    lintian complains heavily about it, there are 7 issues in BTS...
    Should I upload 3.0.alpha9 to unstable (maybe blocking transition
    to testing), and later try to fix most of its problems, uploading
    psycopg3 to unstable shortly after?
    Or should I first upload 3.0.alpha9 to experimetnal, trying to fix
    most of issues there, and upload to sid only when it reaches 3.0.final?
    This is important package, so I'd like to get some opinions before
    proceeding. And also - what should we do with cython (not cython3),
    in our quest to migrate from Python2?

    On similar topic - should I upload newest version of psycopg2
    (removing *dbg package at the same time)? Debian has 2.8.6 while
    latest upstream is 2.9.1. It's less invasive change than in case
    of cython, but I'd still like to get some opinions, or at least acknowledgement.

    Best regards.

    --
    Tomasz Rybak, Debian Developer <serpent@debian.org>
    GPG: A565 CE64 F866 A258 4DDC F9C7 ECB7 3E37 E887 AA8C

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEE1bhtbqZEgXjcK9cyggqgxGY3jWkFAmFXW8oACgkQggqgxGY3 jWnlEw/+IrUX3GhZEJY6chNAdxWGda08Iip238sVLNiv+ceetrTQTxKl4T7U1Boi NDarHjrCSCPUuKMXjfwaT7vj9L4PTII3ClnNj8bI+ZH/M/HkWlZsDOkjtc7BS1OX wyf7ZGmgBoAnAsq+vus9UjysQzr+Tm2U0m4YJ3cLY8WvBCJMylWA+3XU76tLvkmU /rMXAZfeV7H0VW2DFG8lkuZPn9NwnuBRPOkWiXOjypNu6TFT3QPk+pNWF+DCuryd oAaj41VSzmO1b7EPvv8IByg++vcNIi95NQhYlybMsfLr1TTDtT1eWxfDibDi1bVf IlWD6nvXJzeZqE8DA+vo04H2Bafgbe66ISB3iPhK80i3k2kfPXYGtcJT8nm2tVzC GWs8Dq/T+yKNwbMiM+HQkQcxT4BKJhcjuyV35rkQ1UAne1TOrRxAZwEst2zzV6TS cGwrEaqKXqsM3tfxPdvOxUm7rko4hR+Gd9QOmIA/MRNX3TBTDctIUVCwPMRZIDYB vNdxDmQHoXHNbtf9nnVzXJKl9LCZFwMhJHc/R3hqqBUX5iQmuXKjjE15Niyr1x/4 nREfWqsk0iKOPdByugAcXCw0R/OVn0LrHGClwAPCPPBGKatLWFjQn4vj1Wa+55co 0s8buEVw5sGbueZnAKVDxYSLTJys8ztF4GtRyr63z4xymfLdqjM=
    =Fs7l
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gatew
  • From Paul Wise@21:1/5 to All on Sat Oct 2 04:50:01 2021
    On Fri, Oct 1, 2021 at 7:05 PM Tomasz Rybak wrote:

    Should I upload 3.0.alpha9 to unstable (maybe blocking transition
    to testing), and later try to fix most of its problems, uploading
    psycopg3 to unstable shortly after?
    Or should I first upload 3.0.alpha9 to experimetnal, trying to fix
    most of issues there, and upload to sid only when it reaches 3.0.final?
    This is important package, so I'd like to get some opinions before proceeding. And also - what should we do with cython (not cython3),
    in our quest to migrate from Python2?

    Since Cython has many reverse dependencies and this sounds like a
    major upgrade of Cython, this sounds like a transition I would
    definitely stage the transition in experimental and do a test rebuild
    of all reverse dependencies using the ratt too. Doing this in
    experimental also allows you to see autopkgtest results for packages
    in testing but using the Cython from experimental.

    https://wiki.debian.org/Teams/ReleaseTeam/Transitions https://release.debian.org/transitions/ https://release.debian.org/britney/pseudo-excuses-experimental.html

    On similar topic - should I upload newest version of psycopg2
    (removing *dbg package at the same time)? Debian has 2.8.6 while
    latest upstream is 2.9.1. It's less invasive change than in case
    of cython, but I'd still like to get some opinions, or at least acknowledgement.

    The same as above probably applies for psycopg2.

    --
    bye,
    pabs

    https://wiki.debian.org/PaulWise

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)