Hi!

On Wed, 2024-08-14 at 20:47:56 -0500, eevelweezel wrote:
> Package: wnpp
> Severity: wishlist
> Owner: eevelweezel <eevel.wee...@gmail.com>
> X-Debbugs-Cc: debian-devel@lists.debian.org, eevel.wee...@gmail.com

> * Package name    : legacycrypt
>   Version         : 0.0.3
>   Upstream Contact: Christian Heimes <christ...@python.org>
> * URL             : https://github.com/tiran/legacycrypt
> * License         : PSF
>   Programming Lang: Python
>   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 module implements an interface to the crypt(3) routine, which is
> a one-way hash function based upon a modified DES algorithm; see the
> Unix man page for further details. Possible uses include storing
> hashed passwords so you can check passwords without storing the actual
> password, or attempting to crack Unix passwords with a dictionary.
> 
> Per discussion at the DebConf24 Python BOFs, I intend to package this
> as a temporary shim to ease 3.13 transition. I intend to maintain this
> package as part of the Debian Python Team.  I will require a sponsor
> for uploads.

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. :)

Thanks,
Guillem

Reply via email to