+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. Unfortunately this is not the case and now with Python3.12 we also have to deal with the removal of imp (which affects bug #1056419). I'd like to ask for help on debian-python list since I'm pretty overworked with other stuff. Please also review my rude patch[1] to hack around a shinx issue. It would be great to have some better solution here. You can find a full build log of the latest upstream version in Salsa CI[2]. I think the right thing here is to package the new uncertainties version which drops the past import: https://github.com/lebigot/uncertainties/releases/tag/3.1.7 Also we should probably get rid of python-future at some point. Cheers Jochen signature.asc Description: PGP signature
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 major restructuring, so it is entirely possible that something has changed that wasn't part of the advertised API or something like that. But that's for upstream pydevd developers to deal with. I've uploaded 0.14.0-2 that should fix this. As far as I've found that was only a minor fix in the Debian specific offset patch, sorry for the trouble. Cheers Jochen signature.asc Description: PGP signature
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 unwilling[2] to continue patching their build system in response to setuptools changes. While there may be merit in their position, this leaves Debian in a state where numpy is unbuildable, and the freeze is approaching. [2] https://github.com/numpy/numpy/issues/21114 I tried to look at addressing this problem myself, but i had no luck, so i'm here to ask for the help of the wider python team to address this issue. A build log from my machine is available here[3] (error is at the end of the page, as usual). [3] https://paste.debian.net/1259001/ My plan would be, once this is addressed, to package the latest 1.23.4 in experimental, ask for an archive rebuild and later upload 1.23.x to unstable in time for the freeze. This plan is currently on hold due to [1]. Thanks in advance for your help! export SETUPTOOLS_USE_DISTUTILS=stdlib in debian/rules does make it build for me. Do you consider that a fix? Cheers Jochen signature.asc Description: PGP signature
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 for pytest. . This is the Python 3 library. I've just pushed a new version but would prefer if someone closer to pytest would maintain this.
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.debian.org/python-team/packages/python-lsp-jsonrpc python-language-server -> python-lsp-server: https://salsa.debian.org/python-team/packages/python-lsp-server pyls-black -> python-lsp-black: https://salsa.debian.org/python-team/packages/python-lsp-black I kept the history of the old packages and also the maintainers and uploaders. Note that the Python modules and executables where renamed, so the new packages don't conflict with the old ones. Still I would propose to drop the old packages later as development stalled. I'm currently testing the new packages and plan to upload them to new in the coming days. Please tell me if you disagree or see other problems. I'm also planning to package these pylsp plugins: pylsp-mypy, pyls-flake8, pyls-isort and will fill ITPs for them soon. Cheers Jochen signature.asc Description: PGP signature
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 of this sort? https://www.debian.org/doc/packaging-manuals/python-policy/module_packages.html#package_names So python3-pyls-jsonrpc for the binary package is correct. Cheers Jochen signature.asc Description: PGP signature
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 version, or even if there's a better workaround. But perhaps pybuild should be doing this automatically between the dh_auto_install calls so that this kind of workarounds aren't necessary. Thanks for looking into this and providing a patch! I polished it a little: https://salsa.debian.org/science-team/ros-geometry2/-/commit/11739091abe58007485772492fddbdc1a12a59c6 and uploaded a working version to the archive. Will fix all ros-* packages now. Cheers Jochen signature.asc Description: PGP signature
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 source package into it? I did a: $ gbp import-dscs --pristine-tar --debsnap pssh and pushed it here: https://salsa.debian.org/python-team/applications/pssh * update to the latest upstream release (check #891340 or even https://github.com/ParallelSSH/parallel-ssh ?) Yes one has to do that. parallel-ssh seems to be a Python library and different code base, so I would rather go with the Github fork mentioned in #891340. But there are no new releases, so it's probably easiest to pull in the patches via debian/patches. There is a discussion to make it upstream, so I would propose to ask for a release after that is cleared: https://github.com/lilydjwg/pssh/issues/110#issuecomment-580609871 * upload to debian. Well, probably. I'd need a sponsor for initial upload as I'm just a DM. I'm happy to sponsor and help maintain as well. Do you have time later today or tomorrow to work on it together? Otherwise I will go ahead and do some cleanup. My hope would be to get a fixed version into unstable by the end of the weekend. Cheers Jochen signature.asc Description: PGP signature
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 signature.asc Description: PGP signature
