<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">On 31/10/2018 10:01, David Woodfall
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20181031100114.GA22119@blackswan.r0t.uk">
<pre class="moz-quote-pre" wrap="">On Wednesday 31 October 2018 09:54,
Slackbuilds Users <a class="moz-txt-link-rfc2396E" href="mailto:slackbuilds-users@slackbuilds.org" moz-do-not-send="true"><slackbuilds-users@slackbuilds.org></a> put forth the proposition:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">On 30/10/2018 17:59, Benjamin Trigona-Harany wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">On 2018-10-30 10:57 a.m., Heinz Wiesinger wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">We have both python2 and python3 versions of six in a single package in -
current and it works just fine. I don't see why the package would need to be
treated differently from other python libs. What am I missing here?
Grs,
Heinz
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">I don't think you are missing anything. As long as the *version* of a Python module is the same for
Python 2 and Python 3, then it makes sense to have them in a single package or SlackBuild. As I
mentioned in my other email, there are rare cases where this isn't possible: IPython won't go above 5.x
for Python 2 but is on 7.x for Python 3.
Otherwise, keeping them together is usually the way to go.
Ben
_______________________________________________
SlackBuilds-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:SlackBuilds-users@slackbuilds.org" moz-do-not-send="true">SlackBuilds-users@slackbuilds.org</a>
<a class="moz-txt-link-freetext" href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" moz-do-not-send="true">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a>
Archives - <a class="moz-txt-link-freetext" href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/" moz-do-not-send="true">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a>
FAQ - <a class="moz-txt-link-freetext" href="https://slackbuilds.org/faq/" moz-do-not-send="true">https://slackbuilds.org/faq/</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">there seems to be a variation of support in the python scripts. Having the script produce both pthon2 and
python3 files would be useful. I am in the process of updating thonny ( a python ide) which has new deps,
and pyserial is an example where it only does python2. Repeating the python setup.py install --root=$PKG in
the slackbuild
but changing python to python3 fixes that, but I created a separate slackbuild,(not yet submitted) because
most of the python packages I have seen so fave have two separate packages, a pkgname and a
python3-pkgname.
Should I make new python packages create both sets of files, or create separate python2 and python3
packages ?
(i'm working on mypy and mypy_extensions at the moment)
regards, Tim
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">What I did with pudb, the python debugger, is have options for
building either or both, so the user can decide. If someone only
wants to debug python3 code I'm not going to foist an extra load of
python2 code on them.
Dave
--
You or I must yield up his life to Ahrimanes. I would rather it were
you. I should have no hesitation in sacrificing my own life to spare
yours, but we take stock next week, and it would not be fair on the
company.
-- J. Wellington Wells
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
SlackBuilds-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:SlackBuilds-users@slackbuilds.org" moz-do-not-send="true">SlackBuilds-users@slackbuilds.org</a>
<a class="moz-txt-link-freetext" href="https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" moz-do-not-send="true">https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a>
Archives - <a class="moz-txt-link-freetext" href="https://lists.slackbuilds.org/pipermail/slackbuilds-users/" moz-do-not-send="true">https://lists.slackbuilds.org/pipermail/slackbuilds-users/</a>
FAQ - <a class="moz-txt-link-freetext" href="https://slackbuilds.org/faq/" moz-do-not-send="true">https://slackbuilds.org/faq/</a>
</pre>
</blockquote>
thanks dave,<br>
currently i need python3 versions of docutils, pyserial, mypy and
mypy_extensions. I am happy to submit separate python3 versions, or
I could request Robby Workman and Cristiano Urban update their
builds to add python3 support (for the first 2). I'm just trying to
find out what the "normal" should be. That also effects
documentation, because if one script generates both (python2 and 3
files) you only need one set of documentation, but if you use two
build scripts, the documentation would need to be in different
places to avoid loosing it if you had both installed, and just
removepkg one of them.<br>
regards, Tim<br>
Regards, Tim<br>
</body>
</html>