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

Didier Spaier didier at slint.fr
Tue May 4 11:39:10 UTC 2021


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 against
python2 only.

I ask as I am in the process of upgrading Python3 in Slint to 3.9.x (I won't
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 to 
users check if a software "packaged" by SBo is included in Slint and avoid
installing a software twice.

Also, how to best handle the transition in case of a renaming?


More information about the SlackBuilds-users mailing list