Re: [Slackbuilds-users] six and python3-six
On 10/31/18, Tim Dickson via SlackBuilds-users wrote: > 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. That wouldn't happen. removepkg would notice the files exist in another package and it wouldn't remove them. That said, it'd be cleaner for each package to have its own set. Since 15.0 is going to ship python3, maybe combining all the and python3- builds is the way to go. No more "this requires blahblah, built with python3 support" in READMEs, you'd be able to just look at the REQUIRES and install those packages. Speaking as someone who only installs python & its modules as dependencies for apps I want to run, that would make life simpler. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] six and python3-six
On 31/10/2018 10:01, David Woodfall wrote: On Wednesday 31 October 2018 09:54, Slackbuilds Users put forth the proposition: On 30/10/2018 17:59, Benjamin Trigona-Harany wrote: On 2018-10-30 10:57 a.m., Heinz Wiesinger wrote: 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 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ -https://slackbuilds.org/faq/ 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 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 ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ -https://slackbuilds.org/faq/ thanks dave, 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. regards, Tim Regards, Tim ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] six and python3-six
On Wednesday 31 October 2018 09:54, Slackbuilds Users put forth the proposition: > On 30/10/2018 17:59, Benjamin Trigona-Harany wrote: > > On 2018-10-30 10:57 a.m., Heinz Wiesinger wrote: > > > > > > 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 > > > > 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 > > SlackBuilds-users@slackbuilds.org > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > > > > 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 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 signature.asc Description: PGP signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] six and python3-six
On 30/10/2018 17:59, Benjamin Trigona-Harany wrote: On 2018-10-30 10:57 a.m., Heinz Wiesinger wrote: 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 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/ 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 ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] six and python3-six
oups, sorry, thanks Matteo and Ben On Tue, 30 Oct 2018 10:59:44 -0700 Benjamin Trigona-Harany wrote: > On 2018-10-30 10:57 a.m., Heinz Wiesinger wrote: > > > > 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 > > 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 > SlackBuilds-users@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@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] six and python3-six
On 2018-10-30 10:57 a.m., Heinz Wiesinger wrote: 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 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 SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] six and python3-six
On Tuesday, 30 October 2018 17:55:59 CET Tim Dickson via SlackBuilds-users wrote: > On 29/10/2018 12:44, Rich Shepard wrote: > > On Mon, 29 Oct 2018, B Watson wrote: > >> Do we need separate six and python3-six builds? > >> > >> Right now, six will build & install python3 support if python3 is > >> installed on the build box. python3-six is identical, except (a) it > >> requires python3 in the .info file and (b) it builds only the python3 > >> stuff. > > > > I'm a Python end-user and support the idea of having one build that > > supports both Python2 and Python3. All my new code is Python3 but many > > applications remain bound to Python2. It will take a while for everyone to > > migrate to Python3. > > > > Rich > > ___ > > SlackBuilds-users mailing list > > SlackBuilds-users@slackbuilds.org > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > six is a special case, as it is provides compatibility for scripts > running different versions of python. > It is useful to be able to create 2 separate packages though, a python2 > version, and a python3 version (with different package names), because > you can have both installed at the same time. It would be hard to do > that with only one package with options, unless the options changed the > package name - which would then make it harder to manage with tools. 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 signature.asc Description: This is a digitally signed message part. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] six and python3-six
On Tue, 30 Oct 2018, Tim Dickson via SlackBuilds-users wrote: six is a special case, as it is provides compatibility for scripts running different versions of python. It is useful to be able to create 2 separate packages though, a python2 version, and a python3 version (with different package names), because you can have both installed at the same time. It would be hard to do that with only one package with options, unless the options changed the package name - which would then make it harder to manage with tools. Tim, Yes. I forgot that six is different from other python tools. Regards, Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] six and python3-six
On 29/10/2018 12:44, Rich Shepard wrote: On Mon, 29 Oct 2018, B Watson wrote: Do we need separate six and python3-six builds? Right now, six will build & install python3 support if python3 is installed on the build box. python3-six is identical, except (a) it requires python3 in the .info file and (b) it builds only the python3 stuff. I'm a Python end-user and support the idea of having one build that supports both Python2 and Python3. All my new code is Python3 but many applications remain bound to Python2. It will take a while for everyone to migrate to Python3. Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/ six is a special case, as it is provides compatibility for scripts running different versions of python. It is useful to be able to create 2 separate packages though, a python2 version, and a python3 version (with different package names), because you can have both installed at the same time. It would be hard to do that with only one package with options, unless the options changed the package name - which would then make it harder to manage with tools. Tim ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] six and python3-six
On 2018-10-29 5:44 a.m., Rich Shepard wrote: On Mon, 29 Oct 2018, B Watson wrote: Do we need separate six and python3-six builds? Right now, six will build & install python3 support if python3 is installed on the build box. python3-six is identical, except (a) it requires python3 in the .info file and (b) it builds only the python3 stuff. I'm a Python end-user and support the idea of having one build that supports both Python2 and Python3. All my new code is Python3 but many applications remain bound to Python2. It will take a while for everyone to migrate to Python3. For what it's worth, when 15.0 is released, I strongly advocate that Python SlackBuilds cover both Python 2 and 3 together in the same script - just like Pat is doing on current now. Yes, there are few cases where this won't be possible due to incompatibilities (for example IPython needs different versions for Python 2 and Python 3), but those are exceptions. For 14.2, there are several approaches being taken depending on the script maintainer, including various types of support for Python 3 in a Python 2 build script or having two scripts, one each for 2 and 3. My opinion is that we probably don't want to rock the boat too much during 14.2's lifetime but when we do switch to 15.0, I expect to see quite a bit of change in the Python SlackBuilds landscape. That being said, I have added *mandatory* Python 3 support to a few of my SlackBuild scripts to gauge whether it might make sense to start the conversion earlier (e.g. https://git.slackbuilds.org/slackbuilds/commit/?id=1ffc4da77ce21b851bb6dbb8fe01638a8b8d411b). So far no complaints. It's 2018 ... who still objects to having Python 3 installed? ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] six and python3-six
On Mon, 29 Oct 2018, B Watson wrote: Do we need separate six and python3-six builds? Right now, six will build & install python3 support if python3 is installed on the build box. python3-six is identical, except (a) it requires python3 in the .info file and (b) it builds only the python3 stuff. I'm a Python end-user and support the idea of having one build that supports both Python2 and Python3. All my new code is Python3 but many applications remain bound to Python2. It will take a while for everyone to migrate to Python3. Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] six and python3-six
On 10/29/18, B Watson wrote: > Do we need separate six and python3-six builds? Disregard previous email on this subject, I see that six has been updated to only install python2 modules. I was looking at the slackonly binary packages, not the latest SBo. Apologies if I raised anyone's blood pressure. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
