Re: Please push the changes to python-hatch-mypyc

Hi Michael (2024.09.06_23:29:38_+) Whoops, pushed. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Re: urllib3 v2.0.7-1

Hi Alexandre (2024.06.12_09:56:21_+) > Can we upload urllib3 v2.0.7 to unstable ? > (more recent versions breaks backward compatibility) Sounds reasonable to me. I can't remember my concerns with doing it before. Probably just seemed to risky to try without rebuilds. Stefano -- Stefano Rive

Re: dh_python3: file in /usr/lib/python3.12/dist-packages ?

Hi Carles (2024.02.25_00:14:46_+) > It generates a .deb file with a directory: > > /usr/lib/python3.12/dist-packages/ping3-4.0.4.dist-info/ > > With two files there: > -INSTALLER > -top_level.txt If there are files in /usr/lib/python3.*/dist-packages/ after running dh_python3, it means they

Re: Join Python Team

Hi Vasyl (2023.03.03_20:50:27_+) > Thanks for the link! So far: > > 1. I have read the Debian Python Team Policy and agree with it. > 2. My Salsa login is "basilgello" > 3. I need the access to contribute to the packages I am helping Yaroslav with > in NeuroDebian > (DataLad extensions and th

Re: Bug#1026312: Setuptools 65.5.0-1.1 breaks installing Python modules/extensions via meson

Hi Simon (2022.12.20_18:59:12_+) > This appears to be a behaviour change in the build system, and I think it's > triggered by the new setuptools. It is. The Debian detection in meson doesn't support the newer distutils that dynamically sources available schema from the sysconfig module. I'm wo

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

Hi Bo (2022.11.19_05:05:19_+) > One question: > If I put the packahe under Debian Python team, should to change > maintainer to DPT from QA team? Yes. And if it's in the Python Team it needs a human maintainer/uploader too. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Re: compreffor FTBFS with Python 3.11 as supported version

Hi Nilesh (2022.11.16_14:22:09_+) > This seems to stem from moving a header file in py3.11 > > $ apt-file search longintrepr.h > [...] > libpython3.10-dev: /usr/include/python3.10/longintrepr.h > libpython3.11-dev: /usr/include/python3.11/cpython/longintrepr.h > > Was this really intended? Y

Re: PYTHONPATH with cmake build

Hi PICCA (2022.08.31_09:05:43_+) > export PYBUILD_AFTER_BUILD=make -C {build_dir}/lib I didn't do anything to support parallel, there. It may be nice to (makes a huge difference to this package's build time). > export PYBUILD_BEFORE_TEST=cp {build_dir}/lib/lib/*.so {build_dir} > export PYBUIL

Re: joining the Python team

Hi Chin (2022.08.23_14:30:00_+) Please state that you agree with the policy, as specified in the joining section. SR > SR, > > Thank you! I have read the team policy and am looking forward to contributing. > > I checked the salsa python-team group > members

Re: Should we allow Janitor to commit directly to all DPT packages?

Hi Sandro (2022.03.29_21:46:29_+) Seeing Jelmer reminded me about this thread. I have no objection, so count this as an approval. I thought Janitor was already doing this, though... SR > Piotr, Stefano, Bernd, Scott, Ondrey, > as owners of the DPT salsa team ( > https://salsa.debian.org/gr

Re: Considering letting python-pip use vendored dependencies

Hi debian-security (2021.09.15_23:32:14_+) > 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. FYI,

Re: New pybuild plugin for PEP-517 pyproject.toml projects

Hi debian-python (2021.12.17_23:52:14_+) > - 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 At upstream's suggestion, this is renamed to pybuild-pl

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

Hi debian-python (2021.08.14_13:30:00_+) > 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_e

Re: upstream python concerns, python3-full package for bullseye

Hi Thomas (2021.02.12_00:11:07_+) > So indeed, it's a good thing to *not* include distutils and venv by > default when someone installs python. ... > > I propose that we add a python3-full* metapackage for > > bullseye. (*We can use a different name, but it must be a name not > > currentl

Re: help me update dateparser to 1.0.0 in time for bullseye

Hi Antoine (2021.02.08_16:53:57_+) > I have more cycles for this again, and see the 1.0 release still hasn't > hit unstable... need help? :) Uploaded. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272

Re: Future of PyPy (not PyPy3) in Debian

Hi Sandro (2020.06.05_00:00:30_+) > I'm now wondering: what should we do with the entire pypy ecosystem? Big picture: Upstream is continuing to support pypy (2.7) for the foreseeable future. I don't know what that will look like for stdlib support. But they need a 2.7 interpreter for the rpyth

Re: Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).

Hi Thomas (2020.04.21_21:20:16_+) > > But that still leaves the question of what to do about the dependency of > > pytest on pypy-funcsigs ? should pypy modules be removed from pytest and > > it's reverse-dependencies in the same way that regular python2 modules > > were? how feasible is that?