Re: Bug#1022526: python-ssdeep: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command

2022-11-13 Thread Stefano Rivera
Hi Helmut (2022.11.04_11:36:41_+0200)
> And no, updating it to 3.4 does not fix the ftbfs.

Updating it to 3.4.1 might. It includes this commit:
https://github.com/DinoTools/python-ssdeep/commit/fce02106c07ff56a84097dec0df02fb00ef69dc7
which moves the setuptools import above the first distutils import,
which should resolve this issue.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Python 3.11 is now a supported release in unstable

2022-11-11 Thread Stefano Rivera
We've started the Python 3.11 addition transition.
https://release.debian.org/transitions/html/python3.11-add.html

The release team will do binNMUs to rebuild C extensions to add 3.11
support.

To help the transition, please:
1. Avoid starting any Python-related transitions until we get this
   migrated into testing.
2. Fix arch-any python packages that FTBFS
3. Fix any python3.11 compatibility bugs that come up.

I'm aware of a number of FTBFS caused by setuptools >= 60, at the moment.
If there is a distutils-related exception, they're usually fixed by
importing distutils after setuptools. I've been looking for them and
NMUing. Feel free to help :)

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: zope.testrunner: FTBFS: AttributeError: 're.Pattern' object has no attribute 'replace'

2022-10-01 Thread Stefano Rivera
Hi Nilesh (2022.10.01_09:48:50_+)
> > >   File "/usr/share/dh-python/dhpython/depends.py", line 228, in parse
> > > args += " -X '%s'" % pattern.replace("'", r"'\''")
> > > AttributeError: 're.Pattern' object has no attribute 'replace'
> > > make[1]: *** [debian/rules:20: override_dh_python3] Error 1
> 
> This looks like a bug with dh-python itself. Maybe this needs to be "sub" 
> instead of "replace", similar
> string regex replaces at a couple more places.

That looks like fallout from my migration of dh_python* to argparse. I
changed the objects used to represent regexes, but clearly didn't test
-X.

I'll upload a fix, now.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Enabling salsa-ci on all Debian Python Team repos

2022-09-23 Thread Stefano Rivera
Hi Carsten (2022.09.23_05:01:05_+)
> sure, that's a killer argument that I can't really argue against. But that
> is not the point for me.
> 
> For all these checks we already have existing infrastructure, running the
> same also by a pipeline job isn't helping at all if it's not clear how to
> handle the fallout (we already mostly have seen in other places too!).

Yeah, it's similar for me. I test build locally, my sbuild setup does
most (but not all) of the same checks as gitlab CI. Then when I'm happy
I push and upload. If there is any gitlab CI, it runs too late. And if
it fails, I usually don't even bother to investigate, because I trust my
local setup implicitly. Anything that's failing in gitlab CI is almost
certain to be a failure specific to gitlab CI.

I do see a value in having it enabled globally, for the team, though.

1. It can make the team packages friendlier to new contributor team
   members who don't have a setup like that.
   I would like to see our team act more like a team and have people
   contribute to packages that they don't regularly maintain.
2. Getting a test failure on a merge-request catches contributor
   mistakes early. I love having CI on incoming patches like that.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join the team

2022-09-12 Thread Stefano Rivera
Hi Chiara (2022.09.06_07:33:59_+)
> I would like to join the Debian Python team.
> I am currently maintaining the python package sphinxext-opengraph [1] and I
> am contributing to the updates of numpydoc [2].

Added, welcome!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join the team

2022-09-12 Thread Stefano Rivera
Hi Blair (2022.09.01_13:18:50_+)
> I would like to join the Python team, to help update and maintain
> the Python packages in Debian as a daily Debian and Python user,
> to learn how Debian works, and to contribute to the community.
> 
> I have read and accept the team's policy.

Added, welcome to the team.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: PYTHONPATH with cmake build

2022-08-30 Thread Stefano Rivera
Hi PICCA (2022.08.30_16:02:01_+)
> cd build
> cmake ../modules/dxtbx
> cmake --build . --target install
> pip install ../modules/dxtbx

This package essentially has 2 build systems, camke for the C++ stuff
and setuptools for the pure-python. I don't see any integration between
the two (which is quite annoying, the upstream really should fix that).

pybuild knows how to drive distutils, and knows how to drive cmake, but
not both together. Ideally, you do want to use pybuild when building
Python extensions, so you can do them for all supported Python versions.

So, can I suggest something like this?

#! /usr/bin/make -f

export PYBUILD_NAME=dxtbx
export PYBUILD_SYSTEM=distutils
export PYBUILD_AFTER_CONFIGURE=cmake -DPython_EXECUTABLE=/usr/bin/{interpreter} 
-S . -B {build_dir}/lib
export PYBUILD_AFTER_BUILD=make -C {build_dir}/lib
export PYBUILD_BEFORE_TEST=cp {build_dir}/lib/lib/*.so {build_dir}

%:
dh $@ --with python3 --buildsystem=pybuild

You'll need something for the install too, but I didn't get that far, as
the tests fail (due to missing dependencies in Debian).

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Join the team

2022-08-30 Thread Stefano Rivera
Hi Claudius (2022.08.30_09:56:12_+)
> I would like to join the python team to help maintain packages, currently
> related to tpm2-pytss but will potentially extend to other python packages
> like python-cryptography and others.

Added, welcome!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Joining the team

2022-08-30 Thread Stefano Rivera
Hi Emanuele (2022.08.29_19:39:17_+)
> I'd like to join the debian-python team to help with general QA work on
> all packages.
> 
> My salsa login is ema.

Added, welcome!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: is sysconfig.get_path('purelib') local ?

2022-08-28 Thread Stefano Rivera
Hi Jerome (2022.08.28_12:41:18_+)
> > > You want to propagate the change to /usr/share/aclocal/ax_python_devel.m4
> > > distributed in autoconf-archive .
> > > (I localized the error there.)
> > Can you point at a package that FTBFS because of this? Or something
> > easily reproducible. It's really useful to have test cases, when
> > changing code you've never seen before.
> My brand new package graph-tool [1] that experienced a FTBFS during
> what should be a quiet 'Upload to unstable'.

Thanks, that's a beast of a package that wanted *all* my memory when
building with parallel=16 :)

But it gave me a good starting point to drive the autoconf macro.

Filed: https://bugs.debian.org/1018298 (and forwarded it upstream)

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: is sysconfig.get_path('purelib') local ?

2022-08-28 Thread Stefano Rivera
Hi Jerome (2022.08.27_21:24:48_+)
> You want to propagate the change to /usr/share/aclocal/ax_python_devel.m4
> distributed in autoconf-archive .
> (I localized the error there.)

Can you point at a package that FTBFS because of this? Or something
easily reproducible. It's really useful to have test cases, when
changing code you've never seen before.

> Otherwise, is there any keyword to get /usr/lib/python/dist-packages
> via sysconfig.get_path ? May we pass 'distlib' ?
> I guess it would be useful.

I quote from that email:

> The solution in build tools is to explicitly select the posix_prefix
> scheme, and specify the appropriate prefix (/usr or /usr/local). For
> build tools that default to /usr/local, this should be all you need to
> do.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: is sysconfig.get_path('purelib') local ?

2022-08-27 Thread Stefano Rivera
Hi Jerome (2022.08.27_18:01:45_+)
> in the current Sid (Python 3.10.6),
> 
> $ python3 -c "import sysconfig; print (sysconfig.get_path('purelib'));"
> 
> gives
> 
> /usr/local/lib/python3.10/dist-packages
> 
> I suspect that it formaly gave (< Python 3.10.6)
> 
> /usr/lib/python3.10/dist-packages

Correct, see:
https://lists.debian.org/debian-python/2022/03/msg00039.html

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Python distributions with multiple packages

2022-08-26 Thread Stefano Rivera
Hi c.buhtz (2022.08.26_11:10:03_+)
> today I found out that it is possible to create a Python "Distribution
> Package" [1] (e.g. a whl-file) that contain more then one "Importable
> Packages" [2].
> 
> Are you aware of any packages in Debian that are related to upstream
> projects using that "technic"?

This has always been somewhat frowned upon, but it's not that uncommon.
Offhand, I can think of python3-configobj, which upstream is in the
process of tidying up.

> And if so how do you (as debian distro maintainers) handle that? Do you
> create one deb-file for "mydistropackage" (e.g.
> "python3-mydistropackage.deb") or do you separate into "python3-mya.deb" and
> "python3-myb.deb"?

Sometimes we do the one, sometimes the other. It depends.

A famous example is pkg_resources, which is shipped in setuptools,
upstream. We packaged it as a separate module, because it's a runtime
dependency of many packages, but they don't need the whole of setuptools
at runtime.

When we split packages like this, it breaks our automatic dependency
generation tools.  They understand upstream's dependency declarations,
so we have to manually add dependencies to packages that depend on split
libraries.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: joining the Python team

2022-08-24 Thread Stefano Rivera
Hi Chin (2022.08.23_14:58:31_+)
> > > I just packaged docarray for Debian and plan to package jina, a
> > > reverse dependency of docarray soon. As these are python packages I
> > > would like to join the python team and maintain these packages under
> > > the team. I initially tried going through Debian mentors and submitted
> > > an RFS for docarray but they suggested I join the python team and do
> > > it through the team.

Added, welcome!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Requesting to join the team

2022-08-24 Thread Stefano Rivera
Hi Michel (2022.08.19_20:09:12_+)
> Per pollo's suggestion, I am requesting to join the Python Team.

Added, welcome!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Proposed MBF: packages still using nose

2022-08-21 Thread Stefano Rivera
Hi Dmitry (2022.08.21_13:04:36_+)
> Stefano Rivera 
>dh-python (U)

Fixed in git.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: joining the Python team

2022-08-19 Thread Stefano Rivera
Hi Chin (2022.08.17_14:22:19_+)
> I just packaged docarray for Debian and plan to package jina, a
> reverse dependency of docarray soon. As these are python packages I
> would like to join the python team and maintain these packages under
> the team. I initially tried going through Debian mentors and submitted
> an RFS for docarray but they suggested I join the python team and do
> it through the team.

Welcome, please read the team policy:

https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join python team

2022-08-19 Thread Stefano Rivera
Hi Ileana (2022.08.17_14:42:26_+)
> I am requesting to join the debian python team.

Added, welcome!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



[MBF] pybuild: Stop calling setup.py test?

2022-08-15 Thread Stefano Rivera
Calling "setup.py test" has been deprecated since setuptools 28.5.
That's 6 years ago.

pybuild calls currently setup.py test, when it can see that the package
supports it, and another test runner hasn't been selected. I looked at
dropping support for this (https://bugs.debian.org/982298) last year.
I did some test builds and decided that breaking 50 odd packages to stop
calling setup.py test wasn't worth it.

I just ran the tests again, and the numbers are 41 new FTBFS, and 54
packages start emitting "Ran 0 tests", so they lost test coverage.
dd-lists attached.

That's an improvement over last year, but still enough to give me pause
on just changing pybuild and breaking packages.

We also now know that calling setup.py at all is deprecated. "setup.py
test" support hasn't been removed yet, and I don't know if it will be,
at this point...

Options:
1. Change pybuild, cause 41 new FTBFS, and 54 packages to lose testing.
   File FTBFS bugs.
2. File "Severity: important" bugs on the packages that would FTBFS or lose
   testing.
   Change pybuild when most of these are closed.
3. File "Severity: minor" bugs on the packages that would FTBFS or lose
   testing.
   Leave pybuild as is, for now.
   Change pybuild when upstream setuptools drops support for "setup.py
   test".

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272
Adam Cecile 
   python-libais (U)

Aggelos Avgerinos 
   elasticsearch-curator (U)

Andrius Merkys 
   pdb-tools (U)

Antoine Beaupré 
   magic-wormhole

Apollon Oikonomopoulos 
   elasticsearch-curator (U)

Arnaud Fontaine 
   python-libusb1

Brian May 
   django-guardian (U)
   factory-boy (U)

Debian Accessibility Team 
   pocketsphinx-python

Debian Math Team 
   python-pulp

Debian OpenStack 
   python-funcsigs

Debian Python Team 
   autopep8 (U)
   django-classy-tags
   django-guardian
   elasticsearch-curator
   factory-boy
   flask-autoindex
   flask-testing
   lazr.uri (U)
   lesana
   manuel
   mmllib
   multiprocess (U)
   ponyorm
   powerline
   python-applicationinsights
   python-argcomplete
   python-ciso8601
   python-django-ical
   python-django-swapper
   python-libais
   python-libusb1 (U)
   python-pkginfo
   python-wadllib (U)
   pyzbar
   quark-sphinx-theme
   zodbpickle

Debian QA Group 
   python-chameleon
   python-ofxhome
   xmldiff
   zope.i18nmessageid

Debian Tryton Maintainers 
   tryton-server

Debichem Team 
   pdb-tools

Dominik George 
   mmllib (U)

Elena Grandi 
   lesana (U)

Evangelos Ribeiro Tzaras 
   pyzbar (U)

Federico Ceratto 
   python-django-bootstrap-form (U)

Felix Krull 
   quark-sphinx-theme (U)

FreedomBox Packaging Team 
   python-django-bootstrap-form

Héctor Orón Martínez 
   python-phabricator

James Valleroy 
   manuel (U)
   python-django-bootstrap-form (U)

Jameson Graef Rollins 
   magic-wormhole (U)

Jan Dittberner 
   python-pkginfo (U)

Jelmer Vernooij 
   ponyorm (U)
   upstream-ontologist

Jerome Charaoui 
   powerline (U)

Jon Bernard 
   lttnganalyses (U)

Jonathan Carter 
   flask-autoindex (U)

Julien Muchembled 
   zodbpickle (U)

Julien Puydt 
   python-django-ical (U)

Luca Boccassi 
   python-applicationinsights (U)

Malihe Asemani 
   python-ciso8601 (U)

Marc Dequènes (Duck) 
   python-argcomplete (U)

Mathias Behrle 
   tryton-server (U)

Michael Fladischer 
   django-classy-tags (U)
   python-django-swapper (U)

Michael Jeanson 
   lttnganalyses

Nicolas Dandrimont 
   flask-testing (U)

Nilesh Patra 
   python-pulp (U)

Ondřej Surý 
   django-classy-tags (U)

Pirate Praveen 
   pyramid-jinja2

Samuel Henrique 
   powerline (U)

Samuel Thibault 
   pocketsphinx-python (U)

Sandro Tosi 
   multiprocess

Stefano Rivera 
   lazr.uri
   python-wadllib

Stefano Zacchiroli 
   flask-testing (U)

Steffen Moeller 
   python-pulp (U)

Sunil Mohan Adapa 
   python-django-bootstrap-form (U)

Sylvestre Ledru 
   autopep8

Thomas Goirand 
   django-classy-tags (U)
   python-funcsigs (U)

Adam Cecile 
   python-libais (U)

Adrian Alves 
   python-stopit (U)

Ana Rodríguez López 
   siphashc

Andrea Colangelo 
   python-roman (U)

Andreas Tille 
   sphinxcontrib-autoprogram (U)

Andrej Shadura 
   python-phonenumbers (U)

Andrius Merkys 
   pycifrw (U)
   python-freesasa (U)
   python-peakutils (U)

Arto Jantunen 
   pytrainer (U)

Carl Chenet 
   retweet

Chris MacNaughton 
   python3-onelogin-saml2 (U)

Christopher Baines 
   pygtail (U)

Colin Watson 
   httmock (U)

Daniele Tricoli 
   simplegeneric (U)

David Watson 
   pep8 (U)

Debian Fonts Task Force 
   mutatormath

Debian Python Modules Team 
   python-decorator

Debian Python Team 
   blist
   cccolutils
   chargebee-python
   flask-basicauth (U)
   flask-bcrypt
   gitless
   httmock
   objgraph
   pep8
   pycifrw
   pygtail
   pyjks
   pyparsing2
   python-beniget
   python-cpuinfo
   python-decorator
   python-dictobj
   python-django-ical
   python-freesasa
   python-geoip2
   python

Re: Cython 3.0.0

2022-08-14 Thread Stefano Rivera
Hi Julian (2022.08.14_07:41:26_+)
> I don't know how many packages in Debian would be broken by the move
> to 3.0.0; that may be something worth exploring.  It may well be that
> approach (2) makes most sense for the short term.

I think that's the first question to answer. Once we know how bad
the incompatibilities are, we can decide on the best approach.

So, first step is probably to package the new cython version (locally),
and try to rebuild everything against it.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Auto-handling of closed bugs - how does it work?

2022-08-14 Thread Stefano Rivera
Hi Julian (2022.08.14_07:18:49_+)
> A question of curiosity: when I push a commit to salsa with a "Closes:
> #n" in the changelog, the BTS gets a "tag: pending" notification.
> I looked and looked, and could not find out how salsa does this?
> Could anyone enlighten me?  (The standard debian-ci scripts, which the
> repositories use for their CI, appear to only do something with RC
> bugs.)

It's a salsa webhook:
https://wiki.debian.org/Salsa/Doc#Dealing_with_Debian_BTS_from_commit_messages

We don't have tooling that automatically configures all the repos, but
when we migrated to salsa, we set them all up for tagpending, and
posting to #debian-python-changes on IRC

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: pybuild pyproject.toml problem

2022-08-12 Thread Stefano Rivera
Hi Scott (2022.08.11_21:57:04_+)
> I *think* the issue might be that our setuptools is too old to understand
> how to get project metadata from pyproject.toml (PEP 621).  This seems to
> indicate that it was added in setuptools 61.0.0:
> 
> https://setuptools.pypa.io/en/latest/userguide/pyproject_config.html

Yep, I just saw this in another package, too.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join debian-python team on salsa

2022-08-11 Thread Stefano Rivera
Hi Jérémy (2022.08.11_17:58:33_+)
> Yes, of course, I agree with the python policy.
> Also mind that I don't plan to upload anything new without requesting
> review.

Added, welcome to the team.

And sorry that took a while.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join the Debian Python team

2022-08-11 Thread Stefano Rivera
Hi Lena (2022.07.18_14:58:11_+)
> I would like to join the Python team to help maintain various packages
> mostly related to Django.

Added. Welcome to the team. And sorry about the delay.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Desire to join

2022-08-11 Thread Stefano Rivera
Hi Felix (2022.08.03_19:57:26_+)
> With this email, I am expressing my wish to join the team.

Added. Welcome to the team!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Joining the team

2022-08-11 Thread Stefano Rivera
Hi Matt (2022.07.17_23:21:03_+)
> I am interested in joining the Python team, or at least helping out a
> bit if I can.  I work a lot with Python, and I'm currently maintaining
> a tiny module (python-decouple) and working on a second (python-
> public).. my non-Python experience in Debian includes a bunch of perl
> in the latest adduser. :)

Added, sorry about the delay. Welcome!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join the Debian Python Team

2022-08-11 Thread Stefano Rivera
Hi Julien (2022.07.06_16:38:35_+)
> I would like to join the Debian Python Team to package some of my
> projects, mainly sphinx-lint [1], but maybe also pospell [2], pogrep
> [3], and friends created while translating the Python documentation in
> french.

Sorry about the delay. Welcome to the team!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: joining the python team

2022-08-11 Thread Stefano Rivera
Hi Étienne (2022.06.25_18:08:27_+)
> I would be happy to join the team to help adding these packages and
> maintain them on the long run.

Sorry about the long delay, added.

Welcome to the team.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join debian-python team on salsa

2022-08-11 Thread Stefano Rivera
Hi Jérémy (2022.07.07_13:19:01_+)
> I'd like to continue to maintain "gyp",
> and possibly some other python packages in a near future.
> 
> I am aware of python policy and documentation.

Please state that you *agree* with the policy :)

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Fwd: Request to join the Python team

2022-08-11 Thread Stefano Rivera
Hi Guilherme (2022.07.07_09:07:19_+)
> I sent my request to join the team following the Wiki recommendations
> ten days ago and so far I have not received a response.
> I would like to know if there are any more steps to be taken?

I'm afraid the admins were just busy.

I've added you to the team, welcome!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: pdm-pep517: Shall we package it now?

2022-06-28 Thread Stefano Rivera
Hi Boyuan (2022.06.28_13:24:49_+)
> I am wondering if it's time to package pdm-pep517 itself [2], or is there
> any blocking for it. I am aware that some sort of bootstrapping might be
> needed since pdm-pep517 seems to build-depends on itself.

Yes, probably time to package it.

Bootstrapping shouldn't be problematic, PEP517 includes support for
bootstrapping (backend-path = ["."]), so backends can build themselves
from their own source trees.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Joining the team

2022-06-02 Thread Stefano Rivera
Hi Ben (2022.06.01_20:42:21_+)
> I sent this message to the mailing list over a month ago and also asked
> about it on IRC, getting no response from either platform. The Wiki says
> this is how I join the team, so I'm just sending it again.

Sorry about the delay. Welcome to the team!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join the team

2022-05-29 Thread Stefano Rivera
Hi Moessbauer, (2022.05.29_09:17:18_+)
> I have Debian packagings for multiple python packages, found a sponsor 
> (Stephan Lachnit) and would like to join the team.

Please the team policy and reply, indicating your agreement to follow
it:
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

And, nice to meet you in-person, in Hamburg!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to Join the Team

2022-05-23 Thread Stefano Rivera
Hi Lev (2022.05.23_09:01:52_+)
> I’m apologize. But any update for this?
> I want to add new package to python repo. This package already in sid.
> https://salsa.debian.org/faunris/importlab 
> <https://salsa.debian.org/faunris/importlab>

Apologies, it fell through the cracks. Thanks for reminding us!

Welcome to the team, please add your package :)

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: python-argcomplete salvaging and possible team (re)join

2022-04-27 Thread Stefano Rivera
Hi Marc (2022.04.27_05:16:02_+)
> I have read and agree to the policy on:
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

Welcome back to the team :)

Quack!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Bug#1009397: dh-python: Flit plugin suddenly installs to usr/local/ causing FTBFS

2022-04-15 Thread Stefano Rivera
Hi Philip (2022.04.15_14:06:28_+)
> I think I found a way to fix it, just like you did it here 
> https://salsa.debian.org/python-team/tools/dh-python/-/commit/6137db4dc870672615c31c9d1c9535dafe5b0d2a
> I'll create a MR later.

Aha, of course. You can try to use the pyproject plugin, directly (we
should retire the flit plugin in favour of it, at some point). But yes,
fixing the flit plugin should be simple enough...

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: dh-python: Flit plugin suddenly installs to usr/local/ causing FTBFS

2022-04-15 Thread Stefano Rivera
Hi Philip (2022.04.15_08:44:42_+)
> I'm writing to the list as I'm not sure what the source of the problem is.

It'll be something related to
https://lists.debian.org/debian-python/2022/03/msg00039.html

I'll have a more detailed look, later today.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: python3-pysnmp4 forked upstream

2022-04-07 Thread Stefano Rivera
Hi Luiz (2022.04.07_11:22:49_+)
> It looks like the current upstream[1] of pysnmp has been unmaintained
> for a while and got forked [2].
> 
> FreeBSD has done some adjustments to pysnmp and the related packages
> because of that [3][4], as the current version seems broken in Python 3.9.
> 
> What is your opinion on updating these packages to use the forked upstream?

Sounds like switching to the fork is a good idea.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: PDM - Python package manager for Debian

2022-04-03 Thread Stefano Rivera
Hi Dominik (2022.04.03_09:16:14_+)
> > I've compared the tarball from GH with the file from PyPi, the sdist on 
> > PyPi contains even less files than the GH tarball, but also no setup.* 
> > files.
> 
> Uh, PEP-517 actually allows that... I have never seen that in the wild.

It's becoming quite common now. Anything that doesn't use setuptools
won't have setup.* files. And now that there are options besides
setuptools, people are switching to them.

> Cool, so this really means we will ultimately have to package
> everybody's homegrown build system now .

Sensible build systems divide the frontend (CLI and developer tools)
from the backend (PEP-517 API), so that only the latter is needed at
build time (and in Debian).  But yes, I expect a bit of an explosion in
PEP-517 backends in the archive.  And none of them are particularly
stable, yet. Lots of churn.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: sysconfig default scheme change in Python 3.10

2022-03-28 Thread Stefano Rivera
Hi Simon (2022.03.28_21:44:38_+)

> On Mon, 28 Mar 2022 at 21:17:40 +0000, Stefano Rivera wrote:
> > We've fixed this issue in pybind11 and automake-1.16, so far.
> 
> Does this mean that packages that build using Automake, but use the
> pregenerated configure/Makefile.in provided by the upstream maintainer
> (often on an older or non-Debian distro) instead of regenerating the
> build system with dh_autoreconf or equivalent, are going to be broken now?

The change is to python.m4, so it gets included in aclocal.m4 and
configure. If you rebuild those, you'll get the correct behaviour.

I don't think the generated makefiles are affected, just the configured
paths.

We have upstreamed the patch, https://debbugs.gnu.org/54412 so
eventually upstreams will ship something that works correctly, again.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



sysconfig default scheme change in Python 3.10

2022-03-28 Thread Stefano Rivera
I realise we made a consequential changes in Python 3.10, that was never
announced to the team. At the time, I didn't realise how consequential
it would be, but it has forced a few packages to change in response.

The change was in python3.10 3.10.2-3 (25 Feb 2022).

The default sysconfig change has changed from posix_prefix to
posix_local. This matches the long-existing behaviour in Debian's
distutils.sysconfig. distutils is being removed from Python's stdlib in
3.12 [PEP-632], so setuptools etc. are being migrated to be configured
by sysconfig instead.

The practical reason for this is to make "python3 setup.py install"
install to /usr/local/lib/... rather than into the generally
package-managed /usr/lib/python3/.

$ python3.10 -m sysconfig
...
Current installation scheme: "posix_local"

Paths:
data = "/usr/local"
include = "/usr/include/python3.10"
platinclude = "/usr/include/python3.10"
platlib = "/usr/local/lib/python3.10/dist-packages"
platstdlib = "/usr/lib/python3.10"
purelib = "/usr/local/lib/python3.10/dist-packages"
scripts = "/usr/local/bin"
stdlib = "/usr/lib/python3.10"
...

This has caused some changes for some Debian packages. Generally it can
be fixed at a build-tool level, and shouldn't break other Python
packages, but for non-standard tools that haven't been fixed yet, you
may notice that modules install into /usr/local instead of /usr.
dh_python3 will move modules from /usr/local back to /usr, but it's
called after dh_install, so dh_install configuration can get broken by
this change.

The solution in build tools is to explicitly select the posix_prefix
scheme, and specify the appropriate prefix (/usr or /usr/local). For
build tools that default to /usr/local, this should be all you need to
do.

We've fixed this issue in pybind11 and automake-1.16, so far.
If you find any more tools that need work, feel free to ask me to help.

There have been some tweaks to this, since 3.10.2-3, to reduce breakage.
One of the significant wants was to not prefix the include paths with
/local/, as they are defined as referencing the location of cPython's
headers, not the install location for headers [bpo-5]. But some
build tools may have their own interpretations of this...

Related to this change is something else worth noting:

Because distutils is being removed, modern setuptools now carries its
own distutils fork, internally. This doesn't have Debian's patches
implementing these scheme differences. Instead, it's configured by the
presence of a _distutils_system_mod module, which monkey-patches
distutils.

[PEP-632]: https://peps.python.org/pep-0632/
[bpo-5]: https://bugs.python.org/issue5

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join the Debian Python Team

2022-03-26 Thread Stefano Rivera
Hi Martin (2022.03.11_15:32:10_+)
> I would like to join the Debian Python Team. My salsa handle is "mguenther"

Added, welcome!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join the python team

2022-03-26 Thread Stefano Rivera
Hi Timon (2022.03.12_21:06:00_+)
> I have now also read the Debian Python Team Policy and accept it.

Added, welcome.

> (I also suggest to update https://wiki.debian.org/Teams/PythonTeam/HowToJoin 
> with the
> current text from policy.rst as it is much more clearly structured.)

It probably doesn't makes sense to duplicate the same thing in both
places. If there is duplication, I'd suggest trimming the duplication
from the wiki.

If you have suggestions for improving the policy structure, please file
an MR against it and post on the team list, here.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: I want to join the DPT

2022-03-26 Thread Stefano Rivera
Hi vimer (2022.03.17_14:34:11_+)
> I have read the policy [1] and accept it.
> In fact, in my native language, the follow is the same as accept.
> Whataway, I accept the policy now.

Added, welcome.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: DebConf22 -- Python Team BoF + Sprint?

2022-03-26 Thread Stefano Rivera
Hi Louis-Philippe (2022.03.20_21:51:45_+)
> The DebConf22 content team has issued a call for papers [1]. As I'm
> planning to be there this year, I'd be happy to send a proposal for our
> annual BoF :)

Yes, please (and I can see that you've submitted it, thanks!)

> I think it would also be neat to have a team sprint during DebCamp. Here
> are a few ideas of things we could work on:
> 
> * pybuild improvements (getting the autopkgtest MR in would be great)
> * general team QA (maybe based on [2]?)
> * lintian tags used for the team

+1 to a sprint, as usual.

I think upstream cpython would also appreciate it if we did a pass
through all of our cpython patches and ensured they were forwarded. Ping
bugs, etc. Same goes for any core libraries / big packages.
I've attempted to document them all, this year, which is a start. But
only a start. In many cases forwarding the patch would require clearly
defining the bug, writing reproducer scripts, etc.

I'd happily mentor people in working on this.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: pygame: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" --system=custom --test-args "/usr/bin/xvfb-run {interpreter} -m pygame.tests.__main__ --exclude opengl" returned

2022-02-22 Thread Stefano Rivera
Hi Andreas (2022.02.22_07:57:25_+)
> I've put all developers mentioned as Uploader in CC.  Given that the
> last non-team upload was two years ago which might have lead to the
> situation that following upstream changes is stalled it would be great
> if you confirm that you intend to continue working on this package.

I think it's high time to get pygame 2 into Debian. There's probably
some transition required, and maybe some rev-deps will need to be
removed, but pygame 1.9 isn't supportable forever.

I've done some of the recent uploads, kicking the can down the road, but
they're getting harder and harder.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join the DPT

2022-02-18 Thread Stefano Rivera
Hi Georges (2022.02.17_18:05:01_+)
> I'd like to join the Debian Python Team. My salsa handle: gracinet

Added you to the team, welcome!

> I have been on the verge of doing Debian packaging for a very long time,
> but never had the opportunity to go all the way before now.

Glad you made the leap :)

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: [Help] Re: python-envisage: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13

2022-02-14 Thread Stefano Rivera
Hi Andreas (2022.02.14_13:00:13_+)
> I switched to Github downloads and followed the Fedora approach.
> I'd be happy if you could review my changes[1].

That looks like it's all doing the right thing, I only have minor
nit-picks from review:

I'd suggest starting the multi-line shell thing with a "set -e;" for
sanity.

You could use a subshell in the inner-loop, to avoid having to change
directory back to CURDIR again, but

You could generate all the eggs and then run pybuild --test once,
letting it loop over python versions, itself.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Python Team membership request for Nicotine package

2022-02-13 Thread Stefano Rivera
Hi François (2022.02.12_10:15:46_+)

I think your request just got missed or forgotten about.

I've added you to the team, welcome!

SR

> Hello Python Team,
> 
> unless I'm mistaken, I haven't received any answer to my requests. Is
> the team interested by co-maintaining the nicotine package?
> 
> 
> Best,
> François
> 
> 
> 
> Le dimanche 30 janvier 2022 à 17:38 +0100, François Mazen a écrit :
> > Dear Python team,
> > 
> > I'm working on reintroduction of the nicotine package [1] [2]. This
> > software is written in python and Bastian Germann advises me to move
> > the package to the Python Team's umbrella [3].
> > 
> > I really like this idea so I'm requesting to be part of the Debian
> > Python team. My salsa login is mzf. I've read the team policy and I
> > accept it.
> > 
> > The package is currently at [4] in good shape. I guess it should move
> > to the salsa python team group and comply to the policy (use gbp pq
> > for
> > instance). So feel free to guide me with the migration.
> > 
> > Thanks!
> > François
> > 
> > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966000
> > [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004401
> > [3] https://mentors.debian.net/package/nicotine/
> > [4] https://salsa.debian.org/mzf/nicotine
> 



-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Bug#1005043: lintian: check that Python version numbers are not 0.0.0

2022-02-07 Thread Stefano Rivera
Hi Julian (2022.02.07_06:26:38_+)
> I'm a little confused by this.  Have a look at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005039 against
> python3-iniconfig.  It has a very straightforward debian/rules, using
> pybuild, and its setup.py script has "use_scm_version=True", but it
> still produces a python package with version number 0.0.0.
> 
> I have tried this in an environment where I have
> python3-setuptools-scm installed, by the way (even though the package
> does not Build-Depends on it).  I'm using dh-python version 5.20220119

That's the issue, it *needs* to Build-Depend on that (pybuild only
exports the PRETEND environment variable when there is a
Build-Dependency).

Committed a fix to git.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Bug#1005043: lintian: check that Python version numbers are not 0.0.0

2022-02-06 Thread Stefano Rivera
Hi Julian (2022.02.06_12:19:54_+)
> In the couple of cases I've looked at so far, it is due to the
> upstream version using use_scm_version in setup.py.  This works fine
> for a version that is in a Git repository, but it doesn't work for
> Debian packages, as the Git version lookup fails.  So this needs to be
> patched.

Or export SETUPTOOLS_SCM_PRETEND_VERSION.
https://github.com/pypa/setuptools_scm#environment-variables

pybuild does this for you.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Please enable me transfering python-bioblend to Debian Med team

2022-01-15 Thread Stefano Rivera
Hi Nilesh (2022.01.15_14:57:40_+)
> > I think we sorted out that the request to move python-bioblend to Debian
> > Med is valid.  I'm CCing Debian Python team maintainers to get this
> > finally done.
> Could you process this transfer please? Moving python-bioblend from 
> python->med team.
> You have maintainer access in -med and owner in -python, hence please 
> consider transferring this.

Transferred: https://salsa.debian.org/med-team/python-bioblend

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Joining the DPT

2021-12-29 Thread Stefano Rivera
Hi Thomas (2021.12.25_19:07:11_+)
> I would like to join the Debian Python Team to maintain my python
> packages within the team. I'm currently maintaining paperwork [1] and
> its dependencies in an ad-hoc team [2] but I would like to move the
> python packages to the DPT for team maintaining.

Added to the team, welcome!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Ruffin's Request to join Debian Python Team

2021-12-29 Thread Stefano Rivera
Hi ruffsl (2021.12.23_01:07:35_+)
> I'd like to please join your team in order to help package a few new python
> modules.
> As expanded upon below, packaging these python modules will aid my end goal
> in packaging my own build tool extensions.
> 
> Salsa account: ruffsl
> (account is pending approval from your GitLab administrator)
> 
> I state I have read and accept the policy as published here:
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

Welcome to the team, you're member #400!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



New pybuild plugin for PEP-517 pyproject.toml projects

2021-12-17 Thread Stefano Rivera
The Python world has developed new standards for building and
distributing modules. The previous approach of running setup.py has been
replaced by a build API described in PEP517 (and some associated
documents).

An increasing number of projects now use this approach to building -
there is no setup.py in the source package but instead a pyproject.toml
file that lists the build tools and build dependencies that are to be
used. In some cases, a vestigial setup.py is kept for compatibility, but
the upstream expects the package to be built without it.

With the upload of dh-python 5.20211213, we now have an *experimental*
plugin that should be able to build all pyproject.toml packages. The
plugin has been designed to feel as similar to the previous distutils
(setup.py) plugin as possible. To select this plugin:

- Remove any patches creating a workaround setup.py for the project
- Build-depend on `dh-python-pep517` as well as any build tools
  specified by upstream in pyproject.toml (in build-system.requires)
  such as python3-setuptools, flit, or python3-poetry-core
- debdiff or diffoscope the resulting deb to check that it isn't
  missing anything / including things it shouldn't

You'll notice that the binary package contains a .dist-info directory,
rather than .egg-info. This is expected, and fulfils the same purpose
with a better-defined structure. Your package should include this
.dist-info directory if it provides a public Python module. As we expect
.dist-info to become more common, we have improved .dist-info parsing in
this dh-python upload. If you had to previously explicitly specify
binary package dependencies, you may find that you don't need to any
more. dh_python3 --depends-section=SECTION now supports dist-info extra
sections, too.

Since this is a new plugin and somewhat experimental, an explicit opt-in
is required. It is anticipated that this plugin will eventually replace
the distutils plugin in situations where both pyproject.toml and
setup.py exist as well as the specialized flit plugin that was included
in bullseye. This plugin has so far been tested against packages using
setuptools, scons, flit and poetry-core as build backends, and against
packages that are pure python and ones containing C extensions; however,
further testing and bug reports are most welcome ("reportbug dh-python";
discussion in #debian-python on irc.oftc.net).

For the curious, the plugin sequence is as follows
- build step: invokes the upstream build backend (using the
  python3-build module) and unpacks the wheel created by the build
  (using the python3-installer module) into the pybuild {build_dir}.
  Scripts and entry points should be available after this stage.
- test step: runs just like the distutils plugin
- install step: copies the files into debian/tmp or debian/package
  as requested by debhelper

Thanks to the many contributions that went into this work, in
particular Stuart Prescott, Stefano Rivera, and Scott Kitterman.

regards,

Debian Python People

Further reading:

PEP517 and related:
https://www.python.org/dev/peps/pep-0517/
https://www.python.org/dev/peps/pep-0518/
https://www.python.org/dev/peps/pep-0621/

pybuild documentation:
https://salsa.debian.org/python-team/tools/dh-python/-/blob/master/pybuild.rst

pybuild plugin:
https://salsa.debian.org/python-team/tools/dh-python/-/blob/master/dhpython/build/plugin_pep517.py



Re: Request to join the Debian Python Team

2021-12-11 Thread Stefano Rivera
Hi Mechtilde (2021.12.11_09:51:21_+)
> I want to join the Python-Team to package paperless-ng (#986227) and the
> needed dependencies under the umbrella of the python team.

Added, welcome!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: [RFH] Bug#1000812: pyrle: import fails on Python 3.10

2021-12-04 Thread Stefano Rivera
Hi Nilesh (2021.12.04_15:15:05_+)
> Would you have any hint on this?
> Is it a bug with the python3 package itself?

You're waiting for python3-tabulate to be patched for Python 3.10
support.

I added a bug blocking link.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Installing data files with pybuild

2021-12-01 Thread Stefano Rivera
Hi Julian (2021.12.01_21:47:38_+)
> I don't understand why the files are not correctly installed by
> setup.py; it has set include_package_data=True, which includes the
> files (and file patterns) listed in MANIFEST.in, but it seems that
> this is only used for the bdist and sdist targets of setup.py, but not
> for the install target.

Correct, the package_data key needs to be set in setup.py / cfg to
install data in bdist_wheels and install:
https://setuptools.pypa.io/en/latest/userguide/datafiles.html

I would suggest forwarding a patch upstream that does that.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: python-cryptography, Rust, and OpenSSL 3.0

2021-12-01 Thread Stefano Rivera
Hi Simon (2021.12.01_12:31:20_+)
> Now that the OpenSSL 3 transition has started in Ubuntu, I plan on
> uploading this package to our archive as I lack the time to do the
> necessary work for the Rust enablement, but I'm wondering if it makes
> sense to do the same in Debian?

I'd assume, yes.

We were waiting on PyO3, primarily, I think. I see it's in unstable, but
hasn't made it to testing, yet. I'll do a source-only upload.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Use of flit as a build-backend in pybuild

2021-11-29 Thread Stefano Rivera
Hi Scott (2021.11.29_19:38:52_+)
> The versions of pybuild in stable, testing, and unstable all support flit as 
> a 
> build-backend for packages built upstream using flit.

While we're talking about this. Until recently, the flit plugin in
pybuild didn't have the test-runner support that was available when
using setuptools. That is now fixed, so if you were using a workaround
to run the test manually, you can probably drop it now (for bookworm).

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: DPT repositories checks/"violations" report

2021-11-27 Thread Stefano Rivera
Hi Sandro (2021.11.27_06:01:08_+)

> Hello,
> while working on something else[1], i noticed how many of the
> repositories in the DPT salsa group are in poor shape:
> 
> * missing branches
> * changes not pushed to salsa
> * general misalignment in configuration/setup/organization
> * many other small nuances
> 
> [1] https://github.com/sandrotosi/debian-python-team-tracker

+1 this is great!

I've been doing some 3.10 NMUs recently, and found myself re-creating
several upstream and pristine-tar branches...

> please take the content with caution, as it's still an early, raw
> draft (i spot-checked some of the reported issues, but there could be
> bugs/issues) and it contains data that can be outdated (see below re
> caching); the fact that the report indicates only 43 repos are without
> violations is a bit disarming, but i think the tool tries to err on
> the side of verbosity and pedantry, with 2 level of violations (ERROR
> and WARNING) to mark which ones are the most important that require
> immediate attention vs the nice-to-have ones.

When we did the migration to git, there weren't good tools for managing
the setup of the salsa repos (hooks, etc.) yet.  I'd assume those exist
now, we should check in with what other teams are doing. That stuff can
all be fixed in one run of a tool, I'd assume.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Status of python-charset-normalizer in Debian

2021-11-14 Thread Stefano Rivera
Hi Sandro (2021.11.15_01:05:12_+)
> > I filed https://github.com/Ousret/charset_normalizer/issues/138
> > upstream.
> 
> In the interest of moving things along, and while we wait for upstream
> action on it, should we Files-Excluded: data/ , re-import the upstream
> tarball, and disable tests/test_cli.py and
> tests/test_full_detection.py (which appear to be the only 2 test files
> using the data directory)?

+1 to that.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join the team

2021-11-14 Thread Stefano Rivera
Hi Athos (2021.11.09_23:42:38_+)
> Salsa login: athos
> 
> I have read the Debian Python Team Policy [1] and I accept it.

Added, welcome!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Status of python-charset-normalizer in Debian

2021-11-14 Thread Stefano Rivera
Hi Sandro (2021.11.12_01:44:11_+)
> Hello Dominik,
> can you update the DPT on the status of python-charset-normalizer? it
> used to be in NEW, but now i cant find it there and it's not in the
> archive.

FWIW: $ grep charset-normalizer /srv/ftp-master.debian.org/log/2021-11
20211106022017|clean-queues|dak|move file to 
morgue|Incoming/REJECT|python-charset-normalizer_2.0.6-1_amd64.changes|/srv/ftp-master.debian.org/morgue/queues/2021/11/06

So, looks like it got a reject.
My guess would be due to data/sample*

I filed https://github.com/Ousret/charset_normalizer/issues/138
upstream.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: platform.machine() on salsa i386 build?

2021-10-30 Thread Stefano Rivera
Hi Ole (2021.10.30_12:20:40_+)
> How can one find out the correct machine here?

sys.implementation._multiarch will return the Debian multiarch tuple
that python was built for.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Bug#997662: lintian: Incorrect tag: package-contains-python-dot-directory for .egg-info directories

2021-10-23 Thread Stefano Rivera
Package: lintian
Version: 2.110.0
Severity: normal

Hi, I see lintian 2.110 is now emitting a
package-contains-python-dot-directory tag for .egg-info directories in
binary packages.

We do not want to encourage package maintainers to remove .egg-info
directories from their Python binary packages. Tools inspect these to
know which Python modules are available on the system, as well as many
other things.

I would consider all of these tags to be incorrect:
W: python3-bs4: package-contains-python-dot-directory 
usr/lib/python3/dist-packages/beautifulsoup4-4.10.0.egg-info/
W: python3-bs4: package-contains-python-dot-directory 
usr/lib/python3/dist-packages/beautifulsoup4-4.10.0.egg-info/PKG-INFO
W: python3-bs4: package-contains-python-dot-directory 
usr/lib/python3/dist-packages/beautifulsoup4-4.10.0.egg-info/dependency_links.txt
W: python3-bs4: package-contains-python-dot-directory 
usr/lib/python3/dist-packages/beautifulsoup4-4.10.0.egg-info/requires.txt
W: python3-bs4: package-contains-python-dot-directory 
usr/lib/python3/dist-packages/beautifulsoup4-4.10.0.egg-info/top_level.txt

Thanks,

SR



Re: .egg-info for entry points during dh_auto_test

2021-10-21 Thread Stefano Rivera
Hi Michael (2021.10.21_18:55:51_+)
> pytest-lazy-fixtures is a pytest plugin and registers itself through the
> Python entrypoints mechanism. In its unitests, it assumes that this
> registration has already happened but during dh_auto_test there is no
> .egg-info directory available. I could use "python3 setup.py develop -x" to
> generate it, but this registers the package in /usr inside the build chroot
> which I think is not the best solution.

I looked at this recently for pytest-doctestplus.

The lazy answer is to run the full test suite in an autopkgtest, not at
build time.

pytest also has a mechanism to register plugins through an environment
variable, but I couldn't figure out how to get the test suite to work
with that.

If you do find a nice mechanism, we should probably apply it to the
packaging of all pytest plugins.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Join the Python team

2021-10-18 Thread Stefano Rivera
Hi Jose (2021.10.12_19:54:59_+)
> My salsa login is jrivero-guest. I've read the policy at
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst,
> looks good to me.

Added, welcome.

> The only point is that I don't have experience using pq
> for the management of the patches (always used quilt) but does not sound
> difficult to learn.

pq is just a tool to turn a quilt series into a git branch and
vice-versa. It's great for rebasing patches on new upstream releases.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: request to join python-team/packages group on salsa

2021-10-18 Thread Stefano Rivera
Hi Afif (2021.10.04_02:18:30_+)
> On 10/3/21 6:50 PM, Sandro Tosi wrote:
> >> I sometimes need to add or make updates to python packages. Currently, I
> >> just uploaded a newer upstream version of httpbin and I'd like to push
> >> the changes to the git repository, which resides in python-team/packages.
> > 
> > httpbin has been orphaned, so it appears as if this repo should be
> > moved from the python-team to the debian namespace (only admins can do
> > that).
> > 
> > please let us know if you still want to join the team.
> > 
> 
> I'd still like to join.

Added, welcome.

And sorry about the delay.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join Debian Python Team

2021-10-18 Thread Stefano Rivera
Hi Vasudev (2021.09.29_08:51:47_+)
> I would like to reintroduce foolscap [1] which is part of DPT back to
> unstable as it is a dependency for reintroducing tahoe-lafs which I used
> to maintain earlier in Debian.

Added you on Salsa, welcome to the team!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join the team

2021-10-18 Thread Stefano Rivera
Hi Phil (2021.09.29_05:37:20_+)
> Hi all, I've been lurking on the list for a while as several important
> applications I use are written in python and I hope to package e.g.
> mautrix-signal. Right now if I am part of the team, I can help with
> lexicon and backports.

Added, welcome to the team!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join the team

2021-10-18 Thread Stefano Rivera
Hi Luiz (2021.09.19_11:02:13_+)
> My Salsa login is lamaral, but my account is not activated yet. Once I
> get salsa access, I will move the fbtftp repository there, as it
> currently resides in my GitHub[2].

I sponsored fbtftp to NEW, we should move its repo into the team.

Added you. Welcome to the team!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Joining Debian Python team

2021-10-18 Thread Stefano Rivera
Hi yokota (2021.09.20_03:04:31_+)
> I want to join Debian Python team to help packaging "python-zeroconf"
> to work "calibre" well.
> Because "python-zeroconf" is required package to "calibre".
> 
> Please add me (salsa: yokota) to Debian Python team.

Added, welcome to the team (and sorry about the delay).

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join the team

2021-09-17 Thread Stefano Rivera
Hi Joshua (2021.09.17_19:26:06_+)
> My official statement: I would like to join the Debian Python Team to
> maintain the pyupgrade, patch-ng, and the eventually the conan Python 
> packages.
> I have read and agree to the DPT policy, and I have subscribed to the
> mailing list (fyi). My salsa login is @ItzSwirlz-guest.

Added, welcome to the team.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Joining Python-team

2021-09-16 Thread Stefano Rivera
Hi Alastair (2021.09.16_12:23:15_+)
> My  salsa / DD login is "mckinstry"
> 
> I have read 
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
>  
> <https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst>
> and will adhere to it.

Added, welcome!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join the team by Christian Buhtz

2021-09-16 Thread Stefano Rivera
Hi c.buhtz (2021.09.12_11:45:28_+)
> I want to package feedparser [1][2]. The main reason is my own
> software (not yet released [3]) depends on it. I am in good contact
> with the upstream maintainer for years and he supports my goal. And some
> of your team members still offered to sponsor me.
> 
> In the faraway future I am willing to take care of the package
> "backintime", too; just because my life and my good sleep depends on
> it. ;)
>
> > Your Salsa login.
> 
> "buhtz" (still waiting for admins approval)
> 
> > A statement
> 
> I read and accept the Debian Python Team - Policy at [4].

Welcome!

I'm not going to add you to the team, immediately, without some visible
history of contribution.

However, I've granted you access to the feedparser repo for a year,
which should be all you need for now. After an upload or two, request
here again, and we can grant team membership.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: pyupgrade has been packaged + request to join the team

2021-09-16 Thread Stefano Rivera
Hi Joshua (2021.09.05_23:13:14_+)
> Now I'm trying to package things to rack up some contributions to
> Debian (and Ubuntu in that vein) by packaging more things.

Welcome. We're glad to have you rack up contributions in our
neighbourhood.

> My previous RFS's was a handful of Nemo extensions, which happened to
> be at the time Bullseye freeze depression struck, and they were all
> expired.

Sometimes the most effective way to get things sponsored in the python
team is via the IRC sponsorship request list. But sometimes they pile up
because nobody is sponsoring...

>   1.  Can I be the maintainer for pyupgrade and have the team as an
>   uploader? I'm asking this because the wiki mentions rule of thumb is
>   the team maintaining to find a 'knowledgeable person'.

Yes, you can. Or the other way around if you want people in the team to
feel free to work on your package (this tends to be rare, though).

>   2.  Can I join the team and later move pyupgrade to the python-team
>   repos? This way I can still upload my package(s, and more as I heard
>   some help is needed for pip at the BoF), and get contributions in
>   for my NM.

If the team is an uploader or maintainer of the package, it should live
in the team repos.

You can move existing package repos into the python-team/packages group.

>   3.  When I join, for the initial release: can the git repo still be
>   my personal salsa repo and use pypi? This way I can just get it
>   pushed, and then later it can be adjusted to pull from a GitHub tag
>   and moved to the team.

Yes, you can delay adding the team as a Maintainer, until the package is
moved into the team salsa group.

> So, with that being said, can I join the team

Please read the team policy:
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
And send an email saying that you agree to it.

> how should I carry the initial release out? Let me know when you are
> ready for me to open an RFS.

Once you've got membership, you can move your repo into the team and
request sponsorship.

> Update: I have also packaged a fork of python-patch that is better
> maintained to close #845482, which is visible at
> https://salsa.debian.org/ItzSwirlz-guest/python-patch-ng. I've decided
> to set the team as Maintainer and me as Uploader this time, as I
> figured I would still technically be a maintainer if I was part of the
> team. As soon as pyupgrade gets its initial release I will do the
> same.

In Debian we generally consider the Maintainer and Uploaders of a
package to all be the maintainers of the package. The Maintainer field
only permits a single entity while Uploaders permits more.

In the Debian Python Team, we have some extra nuance about whether the
team is in the Maintainer or Uploaders field. Team as maintainer means
anybody can work on the package, team as uploader means feel free to
commit changes to git but ask for permission before uploading. This is
unusual, I don't know of any other teams that do that.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join the team

2021-09-16 Thread Stefano Rivera
Hi Nobuhiro (2021.08.30_05:13:26_+)
> I would like to join the team,  I plan to ITP some python packages and
> would like to
> maintain them as team.
> 
> My salsa login is iwamatsu and I have read the Debian Python Team Policy
> and I accept them.

Added to the team, welcome!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join the team

2021-09-16 Thread Stefano Rivera
Hi Dylan (2021.08.19_12:27:42_+)
> I would like to join the team in order to update python-sparse [1] and
> more generally to do some QA work.
> 
> My salsa login is daissi and I have read the Debian Python Team Policy
> and accept it.

Added to the team, welcome!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Joining team

2021-09-16 Thread Stefano Rivera
Hi Valdo (2021.08.20_19:33:11_+)
> I would like to join the team and help the team in maintaining and creating
> packages. I love open source and freeware and I want to contribute to the
> betterment of the open source projects. I like to learn and experience the
> joy of being a contributor for one of the open source software that I liked
> so much.

Sorry for the delayed reply.  Thanks for the offer, we'd love to have
your help in the team.

However, I'm not going to add you to the team, immediately.
I'd recommend getting started by contributing Merge Requests in Salsa
and patches through the bug tracking system, or adopting some orphaned
packages, and getting some experience maintaining them.  Ideally finding
some mentors to help you out, along the way. You can get uploads
sponsored through the team or debian-mentors.

Once it's clear that you're familiar with Debian development processes
and package maintenance, then we'll happily grant you commit access to
the team repos.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: joining python team

2021-09-16 Thread Stefano Rivera
Hi Norbert (2021.07.09_20:43:38_+)
> I think I once was member of this team and had some packages, but
> seemingly in some reorganization this was lost.
> 
> Could you please add me (salsa: preining) to the Debian package team.

Sorry for the delayed reply, added you to the team.

Welcome.

> I am currently updating python-zeroconf which is needed for newer
> calibre.
> I have read the python policy.

I'll interpret that as you saying you agree to follow the Python policy.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Considering letting python-pip use vendored dependencies

2021-09-15 Thread Stefano Rivera
As mentioned in debian-devel recently [1], at the DebConf 21 Debian
Python BoF [2] we discussed the idea of reverting our unbundling patches
to python-pip. The group consensus was that it wasn't worth the effort
to maintain these patches.

Debian Security Team and my co-maintainers: Do you have an opinion on
doing this?

What does pip vendor, and why?
--
See: https://github.com/pypa/pip/tree/main/src/pip/_vendor which
includes a README explaining their rationale.

Why is unbundling pip messy in Debian?
--
pip (and setuptools) have a special position in Debian, as they are
bootstrapped into virtualenvs, used by Python developers and deployment
systems. Virtualenvs exist to provide isolated Python library stacks,
and they need to be able to install these libraries, usually via pip.
They are bootstrapped from wheels in /usr/share/python-wheels.

How do we unbundle pip?
---
Our unbundling approach was to build wheels for every one of the
vendored modules, in /usr/share/python-wheels with dirtbike [3].
Historically, every one of these modules built its own python-X-whl
binary package, that python-pip-whl depended on. But as the dependency
set grew we consolidated building the dirtbiked wheels into the
python-pip source package and generated an appropriate Built-Using
field.

This means we've avoided using pip's vendored copies of modules, but at
the cost of building our own vendored copies at build time. To update
the vendored copies (e.g. to apply security updates), we have to do a
sourceful upload of python-pip.

Over time, our unbundling has caused issues:
1. Version mismatches. We've had old/newer versions that upstream knew
   wouldn't work with pip, but we didn't pick up on until bug reports
   came in.
2. The unbundled libraries were visible in the virtualenv. If they were
   updated, the above mismatches could occur again.
   Their presence also confused users.
   This has now been resolved, but there's still the possibility for new
   versions of one of these libraries, in the virtualenv, breaking pip.
3. Historically, pip have occasionally patched their vendored libraries,
   causing our pip to behave differently / brokenly:
   https://github.com/pypa/pip/issues/7784
4. We've had bugs in our unbundling, e.g.
   https://bugs.debian.org/958396
   https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1935882
   https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1880749
   https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1869247
   https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1833229
   https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1822842
5. Upstream doesn't really support the unbundling mechanism (even though
   they provide it), and don't have any CI coverage of it at the moment.
   This means we've pushed them further away, over time (esp. given the
   bugs above).
   Related to that, but not solely because of it, upstream support has
   been likely to suggest to users that they avoid Debian python things.

We don't have great CI coverage of pip. We don't currently run their
test suite (but we probably should), and we have limited integration
testing to avoid executing untrusted code from the Internet in our
autopkgtests. This has improved over time, but it's still far from
perfect.

I spent a couple of weeks earlier this year getting virtualenv and pip
working correctly in Debian and all the Ubuntu stable releases. In many
cases they'd been somewhat broken for years. Most of the issues were
around the de-vendoring patch. Some of the bugs were quite subtle.

This is a good sign that the Debian maintenance of pip hasn't been
keeping up with the bugs, and suggests to me that the cost of
maintaining this patch isn't worth the benefit.

In the past, we've discussed whether we should continue to de-bundle,
and have done so because we could and it seemed important. I'm not so
sure about that, any more.

If we did start letting pip vendor its dependencies, we'd need to
duplicate any significant patches that Debian currently carries to them,
from what I can see, that's just these two:

1. 
https://salsa.debian.org/debian/python-certifi/-/blob/debian/master/debian/patches/0001-Use-Debian-provided-etc-ssl-certs-ca-certificates.cr.patch
2. 
https://salsa.debian.org/python-team/packages/python-urllib3/-/blob/debian/master/debian/patches/02_require-cert-verification.patch
 (which is possibly noop)

SR

[1]: 
https://lists.debian.org/msgid-search/20210902223835.gb2...@mithrandir.lan.emorrp1.name
[2]: 
https://lists.debian.org/msgid-search/20210827233103.72rnnuzdxhppv...@satie.tumbleweed.org.za
[3]: https://tracker.debian.org/pkg/dirtbike

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Python BoF at DebConf2021

2021-08-27 Thread Stefano Rivera
Hi debian-python (2021.08.26_07:14:20_+)
> I've taken it over, and started an Agenda:
> https://pad.dc21.debconf.org/p/20-python-team-bof

Notes from the BoF:
The video should be published in a couple of hours, to:
https://meetings-archive.debian.net/pub/debian-meetings/2021/DebConf21/debconf21-97-python-team-bof.webm

Attendees:
Diane Trout and her cat
Elana Hashman
Emmanuel Arias
Jonathan Carter
Kyle Robbertze
Nicolas Dandrimont
Romain Porte
Stefano Rivera
Thomas Goirand

State of Python in Debian
=
Python 3.9 is currently the default, with 3.10 available in
experimental.

We plan to make 3.10 supported in unstable in October and then make it
default once RC issues are resolved.

We have been trying to mend the rift between Debian and upstream. Hard
to tell if things are any better. Some people upstream still recommend
avoiding Debian/Ubuntu Python. See "Other upstream issues" below.
Adding python3-full for bullseye was part of this.

We aren't ready for all PEP517-packaged modules. See below.

Debian Python Team Status
=

Volunteers always needed for team-wide maintenance, removals, etc.

Should we push towards git sources, as in:
https://lists.debian.org/debian-python/2021/06/msg00026.html
Consensus was yes, even if watch files continue to point to PyPI.
* ACTION: (olasd to propose) document policy change

-dbg module package removal
===

pydebug doesn't involve an ABI change any more, so all C extensions are
compatible with the -dbg interpreter, out of the box. We can retire our
-dbg packages, and migrate to automatic -dbgsym packages.

* ACTION: need tracker/list to be set up for package removal (no volunteers)
* ACTION: (olasd to ask pollo to) add a lintian warning for python-foo-dbg 
packages

python2.7 removal
=
python2.7 is 99% removed, we're basically there.
We plan to remove python-is-python2 from bookworm.

pypy and pypy3 still build-depend on python2.7.
The rpython toolchain is being slowly ported to python 3, but the
upstream is in no hurry, as they maintain a Python 2.7 interpreter (but
provide no real security support for its standard library).

pypy can be migrated to be manually bootstrapped, or automatically
bootstrapped from cpython2.7 sources copied into the pypy source
package.

Is bookworm shipping with (CPython) 2.7?
We probably don't want to.
We may ship with a pypy 2.7, primarily for building pypy3.

Shall we keep virtualenv support for 2.7?
=
This will require a separate pip stack for virtualenv.
Stefano is tempted to, for pypy (2.7)
Consensus is NO, we don't need to spend time on this.

pip in Debian
=
Can't upgrade to the latest pip without dropping 2.7 support. Consensus
was to do this ASAP.

PEP 668 has been filed about making the ownership of packages between
apt and pip clearer:
https://discuss.python.org/t/graceful-cooperation-between-external-and-python-package-managers-pep-668/10302

pip has struggled to get sufficient maintenance over the years, more
maintainers would be appreciated.
A big part of its complexity is the de-vendoring of its dependencies.

Shall we vendor pip dependencies?
=
pip has a special place as the one and only tool you expect to have in
a virtualenv, so it vendors libraries that it depends on.
https://github.com/pypa/pip/tree/main/src/pip/_vendor
The de-vendoring mechanism was made in cooperation with upstream, but
they don't like it, and don't support our use of it.

It doesn't really provide the "single security update" benefit as
rebuilding the wheels needs a sourceful upload of pip

* ACTION: stefanor to open the conversation with the security team on what
  they think about us re-vendoring the deps of pip (in terms of impact
  on them).

PEP517 in Debian

The python world is moving to PEP517+518. They define how to build
python packages with tools like setuptools, however they only define the
process to build wheels, not to install packages into the system.
We need to create build tools that can drive pep517 + pypa/install and
then install the wheel, unpacked.

dh-python already supports flit, directly, not using the pep517
mechanisms.

Emmanuel is working on poetry support, and will look at more general
tooling after that.

Other upstream issues to be aware of:
https://bugs.python.org/issue43976 - Add vendor information
https://bugs.python.org/issue44982 - Allow Python distributors to add
custom site install schemes

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Python BoF at DebConf2021

2021-08-26 Thread Stefano Rivera
Hi Louis-Philippe (2021.08.14_20:01:27_+)
> Sadly, I have prior engagements and I won't be able to make it. Could
> someone else take on the task of coming up with an agenda and chairing
> the BoF?

I've taken it over, and started an Agenda:
https://pad.dc21.debconf.org/p/20-python-team-bof
Please add anything you think we should cover.

And then help me to prioritize what we should actually cover. I think
we've already got more in there than we can cover in the session, so we
should pick the topics that are most useful to discuss.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Plan to upload all packages still using Alioth in Maintainer/Uploaders

2021-08-14 Thread Stefano Rivera
Hi Sandro (2021.08.14_02:25:21_+)
> [1] https://lintian.debian.org/tags/python-teams-merged

There are more than those, some other variants made it into use too:

udd=> SELECT COUNT(*), maintainer_email FROM sources WHERE release='sid' AND 
maintainer_email LIKE '%python%' GROUP BY maintainer_email;
 count |maintainer_email 
---+-
 1 | gst-python...@packages.debian.org
 1 | pkg-python-debian-ma...@lists.alioth.debian.org
 1 | python-apps-t...@alioth-lists.debian.net
 1 | python-apps-t...@lists.alioth.debian.net
62 | python-apps-t...@lists.alioth.debian.org
15 | python-modules-t...@alioth-lists.debian.net
   713 | python-modules-t...@lists.alioth.debian.org
 9 | team+python-modu...@tracker.debian.org
   670 | team+pyt...@tracker.debian.org
(9 rows)

We should fix them all.

Generally +1 to your proposal.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Team membership request

2021-06-11 Thread Stefano Rivera
Hi Timo (2021.06.09_22:09:15_+)
> Right now, I would like to help maintain the
> outdated Tweepy package which I'm currently using, but more
> generally, I am an avid Python user, so it would be my pleasure to
> help keep the Python package ecosystem in good shape.
> I'm also member of the Science Team, where I help maintain a number
> of (ROS related) Python packages.

Added. Welcome!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: RFS: python-click-log/0.3.2-1 -- Logging integration for Click - Python 3.x

2021-06-05 Thread Stefano Rivera
Hi Nilesh (2021.06.05_15:21:22_+)
> > * What about adding an autopkgtest?
> 
> The test is running during build time.[1] I don't think running the same 
> thing as autopkgtest does a very significant improvement.

I think there's generally an advantage in running the same upstream
tests at build time, as well as in an autopkgtest:

1. If something regresses the test suite, it'll block migration of that
   package into testing.
2. It verifies that the package behaves correctly, as installed. (This
   can mean that you need to disable part of the test-suite, that can't
   handle the installed layout.)

Yes, it's also good to have other kinds of tests in autopkgtests, that
verify installed behaviour (e.g. calling --help on an executable, to see
that it can start-up, and smoke testing library public interfaces).

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Joining the Python Team

2021-05-25 Thread Stefano Rivera
Hi Kyle (2021.05.25_09:11:25_+)
> I wish to join to the Python team to maintain openswitcher [1] and jack
> mixer [2].
> 
> [1] #988182
> [2] https://rdio.space/jackmixer/
> 
> My salsa login is paddatrapper.
> 
> I have read the Debian Team Policy and accept it.

Added, welcome.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: joining the team

2021-05-25 Thread Stefano Rivera
Hi Salman (2021.05.24_10:55:23_+)
> I would like to join the team and help maintaining *prospector* package
> which has been removed from Stable and Testing but is still in Sid in a
> broken state.

Added, welcome.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Challenges packaging Python for a Linux distro - at Python Language Summit

2021-05-24 Thread Stefano Rivera
Hi Thomas (2021.05.12_23:06:45_+)
> This looks great. Is there a video of it somewhere?

The official blog post on it has been published:

https://pyfound.blogspot.com/2021/05/the-2021-python-language-summit_23.html

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: RFS: python-splinter 0.14.0 (new package)

2021-05-21 Thread Stefano Rivera
Hi Joseph (2021.05.20_00:53:31_+)
> I finished packaging splinter, a Python package for testing web applications
> using web browser automation (splinter uses selenium).

Had a quick look at it.

Had to rename things in the pristine-tar branch, to get a source
package to build.

Did you consider getting source from GitHub instead of PyPI? That way
you could get the upstream test suite, docs, and license text.
It would be nice to run the upstream test suite (if possible) and have
autopkgtests.

Did you need to list python3-selenium & python3-six in Depends? I would
have expected dh_python3 to pick them up and list them in
${python3:Depends}.

upstream/metadata:
I don't think of GitHub as being an Archive, as described by the
upstream metadata spec. But I can see why you may disagree.
You could list the PyPI Registry entry.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Joining the team

2021-05-21 Thread Stefano Rivera
Hi Pablo (2021.05.21_03:17:57_+)
> I'm Pablo Mestre, currently I maintein 4 packages in Debian[1]. I'd like
> to join the Debian Python team partly to help maintain the packages
> colortest-python[2] and python-language-server[3].

Added, welcome!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Joining the team

2021-05-21 Thread Stefano Rivera
Hi Dave (2021.05.20_16:56:59_+)
> I'm Dave Jones, currently at Canonical where I work on Raspberry Pi related
> things. I'm also the author of / contributor to a few (largely Pi related)
> Python packages, including gpiozero (which is currently in Debian). I'd like
> to join the Debian Python team partly to help maintain the packages where
> I'm involved with the upstream (such as gpiozero), and partly in the hopes
> of helping get some of the Python packages which only exist in Raspbian
> upstream to Debian.

Added, welcome.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join the Python Team

2021-05-20 Thread Stefano Rivera
Hi Carsten (2021.05.19_10:17:19_+)
> >> I'd like to join the Python team on Salsa.
> > 
> > Please read
> > https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
> > 
> > Hint: 3rd point about joining the team.
> 
> arg, my bad.
> 
> Of course I have before the policy and I agree on that.

Added, welcome :)

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join the Python Team

2021-05-18 Thread Stefano Rivera
Hi Carsten (2021.05.17_17:04:13_+)
> I'd like to join the Python team on Salsa.

Please read
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

Hint: 3rd point about joining the team.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join python team

2021-05-17 Thread Stefano Rivera
Hi Sérgio (2021.05.11_22:15:20_+)
> I would like to join the Debian Python team to help maintain typer and 
> crochet.
> 
> My Salsa login is sergiosacj.
> 
> I have read 
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
>  and accept it.

Added, welcome.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join the Python team

2021-05-17 Thread Stefano Rivera
Hi Roland (2021.05.17_16:20:19_+)
> So I hereby request to be added to the python-team group on salsa. My
> salsa login is "lolando", and I have read and accept the
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
> policy.

Added, welcome to the team.

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Request to join Debian Python Team

2021-05-17 Thread Stefano Rivera
Hi Joseph (2021.05.17_03:26:14_+)
> My Salsa username: @njoseph (https://salsa.debian.org/njoseph)
> 
> I hereby declare that I have read the Policy document of the Debian Python
> Team at 
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
> and that I accept it.

Added, welcome.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: request to join the team

2021-05-17 Thread Stefano Rivera
Hi Felix (2021.05.14_16:02:53_+)
> My salsa login: obfusk
> I have read and accepted 
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

Welcome, added to the team.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



Re: Challenges packaging Python for a Linux distro - at Python Language Summit

2021-05-12 Thread Stefano Rivera
Hi Thomas (2021.05.12_23:06:45_+)
> On 5/12/21 11:21 PM, Stefano Rivera wrote:
> > Matthias Klose gave a presentation at the Python Language Summit on the
> > Challenges packaging Python for a Linux distro.
> > [..]
> This looks great. Is there a video of it somewhere?

No, there won't be videos published, only blog posts written.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272



  1   2   3   >