Request to Join Debian Python Team
Hello, Python Team! My name is Thomas Ward, and I'm a Debian Maintainer on a few packages. I'd like to join the Debian Python team. My reasoning for joining is because I am in the process of working on an ITP [1] for a Python library - repolib - that originates from Pop-OS but would be beneficial for Debian and its derivatives. I would like to maintain this package alongside the Debian Python team, hence my request to join. I expect to have an upload to via the mentors process and then NEW processing within the next couple of weeks. My Salsa login is teward - I have several repositories where I have upload/maintainer access in order to properly handle my DM rights and uploads for various packages. Thomas Ward
Re: Request to Join Debian Python Team
PEB: I actually replied to Bo YU's request last night, but I guess it never reached here. I accept the policies as written and will work within their timeframes on work and tasks. (This does not change the 2-week readiness timeline I have for repolib as an ITP which I stated to Bo YU last night, because I'm fighting some stupidness with gbp and other tooling to exclude certain components in the git repository that need overridden entirely in Debian) Thomas (sent from parent account underneath my ubuntu.com address) From: Pierre-Elliott Bécue Sent: Tuesday, January 21, 2025 09:57 To: Thomas Ward Cc: debian-python@lists.debian.org; Thomas Ward Subject: Re: Request to Join Debian Python Team Hi, Thomas Ward wrote on 21/01/2025 at 00:32:07+0100: > Hello, Python Team! > > My name is Thomas Ward, and I'm a Debian Maintainer on a few > packages. I'd like to join the Debian Python team. > > My reasoning for joining is because I am in the process of working on > an ITP [1] for a Python library - repolib - that originates from > Pop-OS but would be beneficial for Debian and its derivatives. I > would like to maintain this package alongside the Debian Python team, > hence my request to join. I expect to have an upload to via the > mentors process and then NEW processing within the next couple of > weeks. > > My Salsa login is teward - I have several repositories where I have > upload/maintainer access in order to properly handle my DM rights and > uploads for various packages. Can you confirm that you read the team's policy and agree to work within its frame? In the meantime, I added you because I'm confident that I know the answer. Welcome! -- PEB
Re: Switch pyinstaller-hooks-contrib default branch to debian/master
Done. FYI https://salsa.debian.org/python-team/packages/pyinstaller-hooks-contrib/-/settings/repository#branch-defaults-settings is where you can do that if you have permissions. I just did this for you as a member of the Python team. Thomas On 2025-03-15 22:39, Soren Stoutner wrote: Can someone with permissions please set debian/master as the default branch for pyinstaller-hooks-contrib? https://salsa.debian.org/python-team/packages/pyinstaller-hooks-contrib/-/branches I made the mistake again of using gbp to make in initial push before the release was tagged, and it uploaded the upstream branch first. -- Soren Stoutner so...@debian.org
Re: python3.10
On 2025-03-10 14:36, Andrey Rakhmatullin wrote: On Mon, Mar 10, 2025 at 07:06:57PM +0100, Christian BAYLE wrote: I just encountered recently a few venv that require 3.10 to work in at least 2 ai stable diffusion software, really difficult to package right now. Not sure what do you mean by venv but for local use you aren't required to use Python interpreters from the distribution and can e.g. use pyenv to install any other one. I was in fact about to suggest the same thing Andrey did here. For any local-use stuff which requires one or more Python versions beyond the system-installed Python version, this is my recommended solution to use pyenv and then have the local installs alongside Debian's installed Python. I also want to make a few things known about 'downstream' 'in Ubuntu that you refer to. The problem we see routinely 'downstream' is people try and change their Python version away from the system preferred Python version, thus breaking things. It happens way more than I'd like to admit (just look at Ask Ubuntu and the number of python errors we can attribute to User Error in this exact way), and usually I suggest pyenv [1] to allow userspace installations of Python isolated from system Python that works for those cases you need older versions. I do this routinely even downstream on other distros. In fact, wherever you are required to use *older* Python or *newer* Python than is available in your distro - Debian, Ubuntu, Mint, etc. - I always point at PyEnv as a solution. Thomas [1]: https://github.com/pyenv/pyenv
