Re: Join the Python team

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

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

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

Re: Request to join Debian Python Team

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

Re: Request to join the team

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

Re: Request to join the team

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.

Re: Joining Debian Python team

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

Re: packaging help request: paths for build_py and build_scripts phases

Hi Jonathan, * Jonathan Dowland [2021-10-18 11:04]: Here, the scripts are copied to a path *not* rooted in <>. So far as I can tell, both phases are normal parts of the setuptools/distutils build lifecycle, and I haven't spotted anything obviously non-standard about the way that is specified.

packaging help request: paths for build_py and build_scripts phases

Hello, I am attempting to package the latest upstream version of "trash-cli"¹, which differs quite a lot from the current package on the build side of things. https://github.com/andreafrancia/trash-cli The problem occurs during the post-build test phase. The tests cannot find the scripts they