Re: NumPy 2 transition is ongoing

Hi Thomas, * Thomas Goirand [2025-01-29 08:13]: If so, how come there's so many failures in unstable? Shouldn't they have been addressed before the upload to unstable? https://qa.debian.org/excuses.php?package=numpy Please give Timo some more time, the binNMUs are not done yet: https://rele

+1 (Re: Suggesting change in DPT policy)

* Thomas Goirand [2024-02-27 15:15]: So I'm 100% with you for the removal of this policy. +1 to everything. Cheers Jochen signature.asc Description: PGP signature

Re: Bug#1056419: [Help] Re: python-future: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

Hi Andreas, * Andreas Tille [2023-12-11 16:42]: Control: tags -1 help [Bug #1056419 in CC since the issue seems to be caused by python-future] Hi Vincent, I tried to upgrade python-future to the latest upstream version in the hope that this would solve the issue reported in bug #1042244. Unf

Re: Python 3.11 for bookworm?

Hi Julian, * Julian Gilbey [2022-12-19 09:41]: Quick update: with the updating of python3-bytecode from 0.13 to 0.14 in unstable/testing, which allows it to handle Python 3.11, something has changed and now pydevd doesn't even pass the tests on Python 3.10. The python3-bytecode underwent a maj

Re: Help needed: numpy FTBFS with newer setuptools

Hi Sandro, with the recent upload of setuptools/65.3.0 (and following) in unstable, numpy FTBFS[1]. The reason is that numpy build system (both used internally and by other packages) customizes setuptools/distutils. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020135 Upstream is unwi

Bug#1007716: RFA: python-pluggy -- plugin and hook calling mechanisms for Python - 3.x

Package: wnpp Severity: normal X-Debbugs-Cc: jspri...@debian.org, debian-python@lists.debian.org Control: affects -1 src:python-pluggy I request an adopter for the python-pluggy package. The package description is: pluggy is the cristallized core of plugin management as used by some 150 plugins

Debian python-language-server package forks

Hi, the Python language server packages where recently forked upstream (because the developers lost access to the original repos) and the development shifted there. I started working on new Debian packages for those (cf. #994007): python-jsonrpc-server -> python-lsp-jsonrpc: https://salsa.de

Re: Package naming advice: python3-pyls-jsonrpc or python3-jsonrpc-server?

Hi Otto, * Otto Kekäläinen [2020-11-01 19:36]: Upstream uses 'python-jsonrpc-server' as the repository and also the pip package name. Should we follow that in Debian or perhaps use the alternative name 'python3-pyls-jsonrpc'? Is there some existing naming convention/policy about Python modules

Re: Python3 modules not built for all supported Python versions

Hi Emilio, * Emilio Pozuelo Monfort [2020-03-30 17:47]: I've heard pybuild now has a cmake backend, so theoretically you could do something like %: dh $@ --buildsystem=pybuild --system=cmake [..] I don't know if I'm missing an argument to dh_python3 so that it knows the python versio

Re: ITS: pssh

Hi Hilmar, * Hilmar Preuße [2020-03-14 08:26]: Am 14.03.2020 um 01:29 teilte Sandro Tosi mit: On Thu, 20 Jun 2019 06:24:13 -0700 Mo Zhou wrote: * bring it under PAPT maintenance Is there more to do than creating a source package, adding a new package below the PAPT group and import the sour

Request to join DPMT and DPAP

Hi Python team, I would like to join the DPMT and DPAP teams on Salsa. I have read both policies and the Python policy and accept all of them. My Salsa account is jspricke. I want to package python-pcl (#909221) as part of DPMT and help packaging autosuspend in PAPT. Thanks Jochen signatu