Bug#1078734: ITP: legacycrypt -- The legacycrypt module is a standalone version of https://docs.python.org/3/library/crypt.html (deprecated), to ease 3.13 transition.

[eevelweezel]

Package: wnpp
Severity: wishlist
Owner: eevelweezel <***@gmail.com>
X-Debbugs-Cc: debian-***@lists.debian.org, ***@gmail.com

* Package name : legacycrypt
Version : 0.0.3
Upstream Contact: Christian Heimes <***@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.

[Guillem Jover]

Hi!

Post by eevelweezel
Package: wnpp
Severity: wishlist
* Package name : legacycrypt
Version : 0.0.3
* 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

[Alexandre Detiste]

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

Post by Guillem Jover

Post by eevelweezel
* 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. :)

[eevelweezel]

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

Post by Alexandre Detiste
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

Post by Guillem Jover

Post by eevelweezel
* 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).

Post by Guillem Jover
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. :)

[Colin Watson]

Post by Alexandre Detiste
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.

I think that should only be done where the PyPI name starts with
"zombie-" (or I suppose where it doesn't exist - but if we need it and
it doesn't exist then IMO somebody should upload it to PyPI first, as
namespace clashes are no fun).

[eevelweezel]

Legacycrypt exists on PyPI, https://pypi.org/project/legacycrypt/

Post by Colin Watson

Post by Alexandre Detiste
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.

I think that should only be done where the PyPI name starts with
"zombie-" (or I suppose where it doesn't exist - but if we need it and
it doesn't exist then IMO somebody should upload it to PyPI first, as
namespace clashes are no fun).
--