[Slackbuilds-users] (re)naming of Python software

Arnaud arnaud.garcia-fernandez at laposte.net
Tue May 4 13:08:32 UTC 2021

I'm working on a lot of python stuff too.
And I do agree :
Python3 by default
Python3 MoDuLe is named python-module
Python2 MoDuLe is named python2-module
Python Software is named software (like mercurial for example)

It seems it is often pertinent de separate both because requirements differs, even if the version is the same fir Python 2 and 3.

That being said, I'd be glad to rename my different python MoDuLe called MoDuLe for consistency.

 - Arnaud.

Le May 4, 2021 11:39:10 AM UTC, Didier Spaier <didier at slint.fr> a écrit :
>Now that Python 2 is end-of-life and its support ended how should we 
>handle the
>naming of Python packages? I'd be tempted to us python for python3 
>packages and
>packages still built against both 2 and 3 and python2 when built
>python2 only.
>I ask as I am in the process of upgrading Python3 in Slint to 3.9.x (I
>wait until Slackware 15 be released because we ship 3.5.9, really too 
>old) and
>would like that the naming in Slint be consistent with the one in SBo
>users check if a software "packaged" by SBo is included in Slint and
>installing a software twice.
>Also, how to best handle the transition in case of a renaming?
>SlackBuilds-users mailing list
>SlackBuilds-users at slackbuilds.org
>Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>FAQ - https://slackbuilds.org/faq/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20210504/1cf29603/attachment.htm>

More information about the SlackBuilds-users mailing list