Sorry, just now seeing this. This package has been in the NEW queue since 10/10 as python3-legacycrypt.
I volunteered to package it with the exclusive intent of ensuring it goes away later. Best, ./wzl On Fri, Oct 18, 2024, 07:46 Alexandre Detiste <alexandre.deti...@gmail.com> wrote: > Thank you for keeping an eye on this. > > There was an even more specific proposal of the Python Team to use the > "python-zombie-*" > namespace for all the modules removed by PEP594 and further future > deprecation PEPs; > this is based on the model of existing python-zombie-imp. > > https://peps.python.org/pep-0594/ > > I packaged python-zombie-telnetlib as a "native" package; > it's a single file that will likely never change anymore. > > Someone could create a project on Pypi, maybe... we'll see. > > Here legacycrypt is an already established name, > it can stay as python-legacycrypt. (?) > > Greetings > > Le ven. 18 oct. 2024 à 14:36, Guillem Jover <guil...@debian.org> a écrit : > > > * URL : https://github.com/tiran/legacycrypt > > > Description : The legacycrypt module is a standalone version of > https://docs.python.org/3/library/crypt.html (crypt was removed in Python > 3.13). > > > > This seems to be a python module only package, but its source package > > name is not currently namespaced. Given that it has not yet passed NEW, > > please namespace it with python- to avoid taking on the global namespace, > > so that we do not "prevent" packaging something that for example installs > > a command with the same name (or having to end up using a non-obvious one > > for that, or requiring a future rename), so that it's easier to see what > > it is about when doing archive-wide analysis from Sources, or dd-lists, > > or even reading changelogs via stuff like apt-listchanges, like the rest > > of the language specific teams are doing. :) >
