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

[Spycrowsoft]

Given Slackware's long release cycles implied by its release philosophy 
(when it's done) and the fact that there is already talk about python 4 
buzzing around, I can see the value of "just sticking a version number 
on it".

It's almost a certainty that we will see one or maybe even two new major 
versions of Python in the Slackware 15 era. The duplicity might be 
worthwhile, because we will end up with multiple simultaneous versions 
in the repository anyway.

Spycrowsoft

Op 05-05-2021 om 00:54 schreef Edward Ender:
> Personally, I like and use python2- for python 2 libs, and python3- 
> for python 3 libs while python software has no prefix. I generally 
> avoid mixing them unless absolutely required like python-caja, there I 
> dont use a number. I think that in the distant future when python 4 
> arrives this will make it easier to transition, and easier to just 
> dump the previous versions. It may seem like almost duplicating 
> scripts, but I have managed to ditch *all* my own python2 scripts for 
> -current.
> But this is only my personal preference.
> *Sent:* Tuesday, May 04, 2021 at 8:08 AM
> *From:* "Arnaud via SlackBuilds-users" <slackbuilds-users at slackbuilds.org>
> *To:* "SlackBuilds.org Users List" <slackbuilds-users at slackbuilds.org>
> *Cc:* "Arnaud" <arnaud.garcia-fernandez at laposte.net>
> *Subject:* Re: [Slackbuilds-users] (re)naming of Python software
> 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 :
>
>     Hello,
>
>     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
>     help
>     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?
>
>     Cheers,
>     Didier
>
>     ------------------------------------------------------------------------
>     SlackBuilds-users mailing list
>     SlackBuilds-users at slackbuilds.org
>     https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     FAQ - https://slackbuilds.org/faq/
>
>
> --
> _______________________________________________ SlackBuilds-users 
> mailing list SlackBuilds-users at slackbuilds.org 
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users 
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ 
> FAQ - https://slackbuilds.org/faq/
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> 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/20210505/59e8ae35/attachment-0001.htm>