Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #16373 > unrolled thread

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.

Started byGuillem Jover <guillem@debian.org>
First post2024-10-18 14:40 +0200
Last post2024-10-22 15:50 +0200
Articles 5 — 4 participants

Back to article view | Back to linux.debian.maint.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  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. Guillem Jover <guillem@debian.org> - 2024-10-18 14:40 +0200
    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. Alexandre Detiste <alexandre.detiste@gmail.com> - 2024-10-18 14:50 +0200
      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 <eevel.weezel@gmail.com> - 2024-10-22 03:50 +0200
      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. Colin Watson <cjwatson@debian.org> - 2024-10-22 14:10 +0200
        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 <eevel.weezel@gmail.com> - 2024-10-22 15:50 +0200

#16373 — 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.

FromGuillem Jover <guillem@debian.org>
Date2024-10-18 14:40 +0200
SubjectBug#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.
Message-ID<JyUqR-2s3j-1@gated-at.bofh.it>
Hi!

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

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

[toc] | [next] | [standalone]


#16374

FromAlexandre Detiste <alexandre.detiste@gmail.com>
Date2024-10-18 14:50 +0200
Message-ID<JyUAy-2s6U-5@gated-at.bofh.it>
In reply to#16373
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 <guillem@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. :)

[toc] | [prev] | [next] | [standalone]


#16394

Fromeevelweezel <eevel.weezel@gmail.com>
Date2024-10-22 03:50 +0200
Message-ID<JAcc1-3meT-1@gated-at.bofh.it>
In reply to#16374

[Multipart message — attachments visible in raw view] — view raw

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.detiste@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 <guillem@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. :)
>

[toc] | [prev] | [next] | [standalone]


#16395

FromColin Watson <cjwatson@debian.org>
Date2024-10-22 14:10 +0200
Message-ID<JAlS1-3sm1-13@gated-at.bofh.it>
In reply to#16374
On Fri, Oct 18, 2024 at 02:46:09PM +0200, Alexandre Detiste wrote:
> 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).

-- 
Colin Watson (he/him)                              [cjwatson@debian.org]

[toc] | [prev] | [next] | [standalone]


#16396

Fromeevelweezel <eevel.weezel@gmail.com>
Date2024-10-22 15:50 +0200
Message-ID<JAnqO-3tbP-1@gated-at.bofh.it>
In reply to#16395

[Multipart message — attachments visible in raw view] — view raw

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

On Tue, Oct 22, 2024, 07:04 Colin Watson <cjwatson@debian.org> wrote:

> On Fri, Oct 18, 2024 at 02:46:09PM +0200, Alexandre Detiste wrote:
> > 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).
>
> --
> Colin Watson (he/him)                              [cjwatson@debian.org]
>

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.maint.python


csiph-web