<html><head></head><body>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><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: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Hello,<br><br>Now that Python 2 is end-of-life and its support ended how should we <br>handle the<br>naming of Python packages? I'd be tempted to us python for python3 <br>packages and<br>packages still built against both 2 and 3 and python2 when built against<br>python2 only.<br><br>I ask as I am in the process of upgrading Python3 in Slint to 3.9.x (I won't<br>wait until Slackware 15 be released because we ship 3.5.9, really too <br>old) and<br>would like that the naming in Slint be consistent with the one in SBo to <br>help<br>users check if a software "packaged" by SBo is included in Slint and avoid<br>installing a software twice.<br><br>Also, how to best handle the transition in case of a renaming?<br><br>Cheers,<br>Didier<hr>SlackBuilds-users mailing list<br>SlackBuilds-users@slackbuilds.org<br><a href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>Archives - <a href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>FAQ - <a href="https://slackbuilds.org/faq/">https://slackbuilds.org/faq/</a><br><br></pre></blockquote></div><br>-- <br></body></html>