<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>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.</div>
<div> </div>
<div>But this is only my personal preference.</div>
<div>
<div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Sent:</b> Tuesday, May 04, 2021 at 8:08 AM<br/>
<b>From:</b> "Arnaud via SlackBuilds-users" <slackbuilds-users@slackbuilds.org><br/>
<b>To:</b> "SlackBuilds.org Users List" <slackbuilds-users@slackbuilds.org><br/>
<b>Cc:</b> "Arnaud" <arnaud.garcia-fernandez@laposte.net><br/>
<b>Subject:</b> Re: [Slackbuilds-users] (re)naming of Python software</div>
<div name="quoted-content">I'm working on a lot of python stuff too.<br/>
And I do agree :<br/>
Python3 by default<br/>
Python3 MoDuLe is named python-module<br/>
Python2 MoDuLe is named python2-module<br/>
Python Software is named software (like mercurial for example)<br/>
<br/>
It seems it is often pertinent de separate both because requirements differs, even if the version is the same fir Python 2 and 3.<br/>
<br/>
That being said, I'd be glad to rename my different python MoDuLe called MoDuLe for consistency.<br/>
<br/>
- Arnaud.<br/>
<div class="gmail_quote">Le May 4, 2021 11:39:10 AM UTC, Didier Spaier <didier@slint.fr> a écrit :
<blockquote class="gmail_quote" style="margin: 0.0pt 0.0pt 0.0pt 0.8ex;border-left: 1.0px solid rgb(204,204,204);padding-left: 1.0ex;">
<pre class="k9mail">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</pre>
<hr/>SlackBuilds-users mailing list<br/>
SlackBuilds-users@slackbuilds.org<br/>
<a href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" target="_blank">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br/>
Archives - <a href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/" target="_blank">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br/>
FAQ - <a href="https://slackbuilds.org/faq/" target="_blank">https://slackbuilds.org/faq/</a><br/>
</blockquote>
</div>
<br/>
--<br/>
_______________________________________________ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org <a href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" target="_blank">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a> Archives - <a href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/" target="_blank">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a> FAQ - <a href="https://slackbuilds.org/faq/" target="_blank">https://slackbuilds.org/faq/</a></div>
</div>
</div>
</div></div></body></html>