Re: psycopg3 packaging: need new version of cython3 (and psycopg2)
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
psycopg3 packaging: need new version of cython3 (and psycopg2)
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 GPG: A565 CE64 F866 A258 4DDC F9C7 ECB7 3E37 E887 AA8C signature.asc Description: This is a digitally signed message part
Re: mypy and typeshed
On Fri, Oct 01, 2021 at 08:14:20AM -0300, Antonio Terceiro wrote: > On Thu, Sep 30, 2021 at 04:29:20PM -0300, Antonio Terceiro wrote: > > Maybe I didn't dedicate enough time for this, but I couldn't figure out > > how the pypi packages are produced from the git repository. Knowing this > > would help creating such typeshed package by means of some scripting > > (not necessarily volunteering, will be happy if someone beats me to it). > > It turns out that this is done by this repository: > > https://github.com/typeshed-internal/stub_uploader I gave this a try, and came up with https://salsa.debian.org/terceiro/typeshed This seems to work, but there are still issues to solve, e.g. the licensing status of the stub_uploader repository¹, and generating a meaningful Provides: field. ¹ https://github.com/typeshed-internal/stub_uploader/issues/31 signature.asc Description: PGP signature
Re: mypy and typeshed
On Thu, Sep 30, 2021 at 04:29:20PM -0300, Antonio Terceiro wrote: > Maybe I didn't dedicate enough time for this, but I couldn't figure out > how the pypi packages are produced from the git repository. Knowing this > would help creating such typeshed package by means of some scripting > (not necessarily volunteering, will be happy if someone beats me to it). It turns out that this is done by this repository: https://github.com/typeshed-internal/stub_uploader signature.asc Description: PGP signature
Wiki: Debian Python Policy docu not on team site
Hello, this is about the wiki page of that team. https://wiki.debian.org/Teams/PythonTeam I accidentally found the "Debian Python Policy documentation". https://www.debian.org/doc/packaging-manuals/python-policy/ Looks nice and very important for new team members. Maybe it would help if it is linked on the team wiki page. Kind Christian Buhtz
Re: Difference between "python-debian team" and "Debian Python Team"
On Fri, Oct 01, 2021 at 10:38:34AM +, c.bu...@posteo.jp wrote: > what are the differences between this two salsa groups? > > https://salsa.debian.org/python-team > > https://salsa.debian.org/python-debian-team This second one is specific for this one package and only that: https://tracker.debian.org/pkg/python-debian The first one (python-team) is probably the one you are looking for. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Difference between "python-debian team" and "Debian Python Team"
Hello together, what are the differences between this two salsa groups? https://salsa.debian.org/python-team https://salsa.debian.org/python-debian-team As a novice in debian python packaging it extremely confuses me. And I have impression that "team sites" in salsa (e.g. the two links above) do not contain detailed descriptions about the teams. Kind Christian
