Hi,
As a follow up of our Flock discussion, I will build several Python versions in Copr, for development purposes (such as testing your code with tox on multiple Python versions).
Those builds will be installable alongside regular python3/python packages and will be normal packages, no software collections etc. One flat package (i.e. no -libs, -devel...) with bundled setuptools and pip.
First I've built Python 3.5 for Fedora 23, you can grab it here [1].
If you try to use tox with it, you'll have to use Python 3 version (python3-tox is the package and unfortunately also the command), due to a bug in virtualenv [2].
I would appreciate any feedback on the build, so I can build python34 package for Fedora 24+ in similar manner soon.
Also python33 and python26 are planned.
If those builds prove themselves useful I'll try to put them in Fedora (with a strict guideline that forbids any other package to depend on them).
[1] https://copr.fedorainfracloud.org/coprs/g/python/python35/ [2] https://bugzilla.redhat.com/show_bug.cgi?id=1365941
On 11.8.2016 11:26, Miro Hrončok wrote:
Hi,
As a follow up of our Flock discussion, I will build several Python versions in Copr, for development purposes (such as testing your code with tox on multiple Python versions).
Those builds will be installable alongside regular python3/python packages and will be normal packages, no software collections etc. One flat package (i.e. no -libs, -devel...) with bundled setuptools and pip.
First I've built Python 3.5 for Fedora 23, you can grab it here [1].
If you try to use tox with it, you'll have to use Python 3 version (python3-tox is the package and unfortunately also the command), due to a bug in virtualenv [2].
I would appreciate any feedback on the build, so I can build python34 package for Fedora 24+ in similar manner soon.
Also python33 and python26 are planned.
If those builds prove themselves useful I'll try to put them in Fedora (with a strict guideline that forbids any other package to depend on them).
[1] https://copr.fedorainfracloud.org/coprs/g/python/python35/ [2] https://bugzilla.redhat.com/show_bug.cgi?id=1365941
You can now also test Python 3.4 for Fedora 24 and 25.
https://copr.fedorainfracloud.org/coprs/g/python/python34/
There is one remaining issue, but it should not block you form using the package.
https://github.com/fedora-python/python34/issues/1
Let me know how it works for you.
On 16 August 2016 at 20:36, Miro Hrončok mhroncok@redhat.com wrote:
On 11.8.2016 11:26, Miro Hrončok wrote:
Hi,
As a follow up of our Flock discussion, I will build several Python versions in Copr, for development purposes (such as testing your code with tox on multiple Python versions).
Those builds will be installable alongside regular python3/python packages and will be normal packages, no software collections etc. One flat package (i.e. no -libs, -devel...) with bundled setuptools and pip.
First I've built Python 3.5 for Fedora 23, you can grab it here [1].
If you try to use tox with it, you'll have to use Python 3 version (python3-tox is the package and unfortunately also the command), due to a bug in virtualenv [2].
I would appreciate any feedback on the build, so I can build python34 package for Fedora 24+ in similar manner soon.
Also python33 and python26 are planned.
If those builds prove themselves useful I'll try to put them in Fedora (with a strict guideline that forbids any other package to depend on them).
[1] https://copr.fedorainfracloud.org/coprs/g/python/python35/ [2] https://bugzilla.redhat.com/show_bug.cgi?id=1365941
You can now also test Python 3.4 for Fedora 24 and 25.
https://copr.fedorainfracloud.org/coprs/g/python/python34/
There is one remaining issue, but it should not block you form using the package.
https://github.com/fedora-python/python34/issues/1
Let me know how it works for you.
Nice! Would it make sense for us to have a "tox" section in the sidebar at https://developer.fedoraproject.org/tech/languages/python/python-installatio... that covers using these COPR builds with tox for cross-version testing?
Cheers, Nick.
On 17.8.2016 19:04, Nick Coghlan wrote:
On 16 August 2016 at 20:36, Miro Hrončok mhroncok@redhat.com wrote:
On 11.8.2016 11:26, Miro Hrončok wrote:
Hi,
As a follow up of our Flock discussion, I will build several Python versions in Copr, for development purposes (such as testing your code with tox on multiple Python versions).
Those builds will be installable alongside regular python3/python packages and will be normal packages, no software collections etc. One flat package (i.e. no -libs, -devel...) with bundled setuptools and pip.
First I've built Python 3.5 for Fedora 23, you can grab it here [1].
If you try to use tox with it, you'll have to use Python 3 version (python3-tox is the package and unfortunately also the command), due to a bug in virtualenv [2].
I would appreciate any feedback on the build, so I can build python34 package for Fedora 24+ in similar manner soon.
Also python33 and python26 are planned.
If those builds prove themselves useful I'll try to put them in Fedora (with a strict guideline that forbids any other package to depend on them).
[1] https://copr.fedorainfracloud.org/coprs/g/python/python35/ [2] https://bugzilla.redhat.com/show_bug.cgi?id=1365941
You can now also test Python 3.4 for Fedora 24 and 25.
https://copr.fedorainfracloud.org/coprs/g/python/python34/
There is one remaining issue, but it should not block you form using the package.
https://github.com/fedora-python/python34/issues/1
Let me know how it works for you.
Nice! Would it make sense for us to have a "tox" section in the sidebar at https://developer.fedoraproject.org/tech/languages/python/python-installatio... that covers using these COPR builds with tox for cross-version testing?
It would. My long term plan here actually is to put this in Fedora proper and make tox Recommend all the Pythons, so you could just dnf install tox and it would bring all the runtimes (and you could prevent it if you didn't want (actually I have no idea if we ahve some --without-recommends flag for dnf, but anyway...)).
Cheers, Nick.
On Thu, Aug 18, 2016 at 9:04 AM, Miro Hrončok mhroncok@redhat.com wrote:
On 17.8.2016 19:04, Nick Coghlan wrote:
On 16 August 2016 at 20:36, Miro Hrončok mhroncok@redhat.com wrote:
On 11.8.2016 11:26, Miro Hrončok wrote:
Hi,
As a follow up of our Flock discussion, I will build several Python versions in Copr, for development purposes (such as testing your code with tox on multiple Python versions).
Those builds will be installable alongside regular python3/python packages and will be normal packages, no software collections etc. One flat package (i.e. no -libs, -devel...) with bundled setuptools and pip.
First I've built Python 3.5 for Fedora 23, you can grab it here [1].
If you try to use tox with it, you'll have to use Python 3 version (python3-tox is the package and unfortunately also the command), due to a bug in virtualenv [2].
I would appreciate any feedback on the build, so I can build python34 package for Fedora 24+ in similar manner soon.
Also python33 and python26 are planned.
If those builds prove themselves useful I'll try to put them in Fedora (with a strict guideline that forbids any other package to depend on them).
[1] https://copr.fedorainfracloud.org/coprs/g/python/python35/ [2] https://bugzilla.redhat.com/show_bug.cgi?id=1365941
You can now also test Python 3.4 for Fedora 24 and 25.
https://copr.fedorainfracloud.org/coprs/g/python/python34/
There is one remaining issue, but it should not block you form using the package.
https://github.com/fedora-python/python34/issues/1
Let me know how it works for you.
Nice! Would it make sense for us to have a "tox" section in the sidebar at https://developer.fedoraproject.org/tech/languages/python/python-installatio... that covers using these COPR builds with tox for cross-version testing?
It would. My long term plan here actually is to put this in Fedora proper and make tox Recommend all the Pythons, so you could just dnf install tox and it would bring all the runtimes (and you could prevent it if you didn't want (actually I have no idea if we ahve some --without-recommends flag for dnf, but anyway...)).
dnf --setopt=install_weak_deps=false install tox
Cheers, Nick.
-- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok _______________________________________________ python-devel mailing list python-devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/python-devel@lists.fedoraproject...
On 18.8.2016 10:12, Igor Gnatenko wrote:
On Thu, Aug 18, 2016 at 9:04 AM, Miro Hrončok mhroncok@redhat.com wrote:
On 17.8.2016 19:04, Nick Coghlan wrote:
On 16 August 2016 at 20:36, Miro Hrončok mhroncok@redhat.com wrote:
On 11.8.2016 11:26, Miro Hrončok wrote:
Hi,
As a follow up of our Flock discussion, I will build several Python versions in Copr, for development purposes (such as testing your code with tox on multiple Python versions).
Those builds will be installable alongside regular python3/python packages and will be normal packages, no software collections etc. One flat package (i.e. no -libs, -devel...) with bundled setuptools and pip.
First I've built Python 3.5 for Fedora 23, you can grab it here [1].
If you try to use tox with it, you'll have to use Python 3 version (python3-tox is the package and unfortunately also the command), due to a bug in virtualenv [2].
I would appreciate any feedback on the build, so I can build python34 package for Fedora 24+ in similar manner soon.
Also python33 and python26 are planned.
If those builds prove themselves useful I'll try to put them in Fedora (with a strict guideline that forbids any other package to depend on them).
[1] https://copr.fedorainfracloud.org/coprs/g/python/python35/ [2] https://bugzilla.redhat.com/show_bug.cgi?id=1365941
You can now also test Python 3.4 for Fedora 24 and 25.
https://copr.fedorainfracloud.org/coprs/g/python/python34/
There is one remaining issue, but it should not block you form using the package.
https://github.com/fedora-python/python34/issues/1
Let me know how it works for you.
Nice! Would it make sense for us to have a "tox" section in the sidebar at https://developer.fedoraproject.org/tech/languages/python/python-installatio... that covers using these COPR builds with tox for cross-version testing?
It would. My long term plan here actually is to put this in Fedora proper and make tox Recommend all the Pythons, so you could just dnf install tox and it would bring all the runtimes (and you could prevent it if you didn't want (actually I have no idea if we ahve some --without-recommends flag for dnf, but anyway...)).
dnf --setopt=install_weak_deps=false install tox
Cool, thanks :)
On 18 August 2016 at 17:04, Miro Hrončok mhroncok@redhat.com wrote:
On 17.8.2016 19:04, Nick Coghlan wrote:
Nice! Would it make sense for us to have a "tox" section in the sidebar at https://developer.fedoraproject.org/tech/languages/python/python-installatio... that covers using these COPR builds with tox for cross-version testing?
It would. My long term plan here actually is to put this in Fedora proper and make tox Recommend all the Pythons, so you could just dnf install tox and it would bring all the runtimes (and you could prevent it if you didn't want (actually I have no idea if we ahve some --without-recommends flag for dnf, but anyway...)).
Oh, that would be *very* handy :)
Cheers, Nick.
On 08/18/2016 09:04 AM, Miro Hrončok wrote:
On 17.8.2016 19:04, Nick Coghlan wrote:
[...]
Nice! Would it make sense for us to have a "tox" section in the sidebar at https://developer.fedoraproject.org/tech/languages/python/python-installatio...
that covers using these COPR builds with tox for cross-version testing?
It would. My long term plan here actually is to put this in Fedora proper and make tox Recommend all the Pythons, so you could just dnf install tox and it would bring all the runtimes (and you could prevent it if you didn't want (actually I have no idea if we ahve some --without-recommends flag for dnf, but anyway...)).
As a note to anyone interested in alternate versions: The Guidelines were recently changed, so the Fedora review should be easier than expected.
I find the new wording ambiguous, so I'd like to follow as much of the process as practical, but it should prevent an eager reviewer from nitpicking 10-year-old specfile warts in python-2.6. I'd rather focus spec cleanup efforts on python3 ;)
-------- Forwarded Message -------- Subject: [Guidelines change] Changes to the packaging guidelines Date: Thu, 18 Aug 2016 13:25:15 -0500 From: Jason L Tibbitts III tibbs@math.uh.edu Reply-To: devel@lists.fedoraproject.org To: devel-announce@lists.fedoraproject.org
Here are the recent changes to the packaging guidelines.
[...]
The review process document has been amended to note possible exceptions, and to indicate that review is not needed in certain situations where a different version of an existing package is being added.
* https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Package_Review_Pro... * https://fedorahosted.org/fpc/ticket/637
"PV" == Petr Viktorin pviktori@redhat.com writes:
PV> As a note to anyone interested in alternate versions: The Guidelines PV> were recently changed, so the Fedora review should be easier than PV> expected.
Yeah, we had done this before flock (which is why I mentioned that review wasn't necessary at flock) but didn't get to write it up at flock.
PV> I find the new wording ambiguous,
Would be happy to know what you find to be ambiguous. I will admit that the process isn't particularly good since the pkgdb request wants an review ticket, but that's kind of beyond the scope of the packaging guidelines.
- J<
On 08/22/2016 04:49 PM, Jason L Tibbitts III wrote:
"PV" == Petr Viktorin pviktori@redhat.com writes:
PV> As a note to anyone interested in alternate versions: The Guidelines PV> were recently changed, so the Fedora review should be easier than PV> expected.
Yeah, we had done this before flock (which is why I mentioned that review wasn't necessary at flock) but didn't get to write it up at flock.
PV> I find the new wording ambiguous,
Would be happy to know what you find to be ambiguous. I will admit that the process isn't particularly good since the pkgdb request wants an review ticket, but that's kind of beyond the scope of the packaging guidelines.
The Review Guidelines list cases in which you don't have to follow the Review Process, but don't say what you *should* do in these cases. The contributor is left to cherry-pick parts of the process that make sense. That's probably a good thing -- I reckon the idea is that it's still good to follow the process, but an exception allows you to skip any of its steps as you see fit. But that idea isn't communicated very clearly.
From the wording it's also unclear to me if the exception is meant to effectively change "MUST" items into "SHOULD". From the way the [[Packaging:ReviewGuidelines]] and [[Package_Review_Process]] pages link to each other, it's not clear if "Things To Check On Review" is just part of the process or something that can't be skipped even with an exception.
On 22.8.2016 12:16, Petr Viktorin wrote:
On 08/18/2016 09:04 AM, Miro Hrončok wrote:
On 17.8.2016 19:04, Nick Coghlan wrote:
[...]
Nice! Would it make sense for us to have a "tox" section in the sidebar at https://developer.fedoraproject.org/tech/languages/python/python-installatio...
that covers using these COPR builds with tox for cross-version testing?
It would. My long term plan here actually is to put this in Fedora proper and make tox Recommend all the Pythons, so you could just dnf install tox and it would bring all the runtimes (and you could prevent it if you didn't want (actually I have no idea if we ahve some --without-recommends flag for dnf, but anyway...)).
As a note to anyone interested in alternate versions: The Guidelines were recently changed, so the Fedora review should be easier than expected.
I find the new wording ambiguous, so I'd like to follow as much of the process as practical, but it should prevent an eager reviewer from nitpicking 10-year-old specfile warts in python-2.6. I'd rather focus spec cleanup efforts on python3 ;)
-------- Forwarded Message -------- Subject: [Guidelines change] Changes to the packaging guidelines Date: Thu, 18 Aug 2016 13:25:15 -0500 From: Jason L Tibbitts III tibbs@math.uh.edu Reply-To: devel@lists.fedoraproject.org To: devel-announce@lists.fedoraproject.org
Here are the recent changes to the packaging guidelines.
[...]
The review process document has been amended to note possible exceptions, and to indicate that review is not needed in certain situations where a different version of an existing package is being added.
https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Package_Review_Pro...
Here is the review request for 3.5: https://bugzilla.redhat.com/show_bug.cgi?id=1369688
On 11.8.2016 11:26, Miro Hrončok wrote:
Hi,
As a follow up of our Flock discussion, I will build several Python versions in Copr, for development purposes (such as testing your code with tox on multiple Python versions).
Those builds will be installable alongside regular python3/python packages and will be normal packages, no software collections etc. One flat package (i.e. no -libs, -devel...) with bundled setuptools and pip.
First I've built Python 3.5 for Fedora 23, you can grab it here [1].
If you try to use tox with it, you'll have to use Python 3 version (python3-tox is the package and unfortunately also the command), due to a bug in virtualenv [2].
I would appreciate any feedback on the build, so I can build python34 package for Fedora 24+ in similar manner soon.
Also python33 and python26 are planned.
If those builds prove themselves useful I'll try to put them in Fedora (with a strict guideline that forbids any other package to depend on them).
[1] https://copr.fedorainfracloud.org/coprs/g/python/python35/ [2] https://bugzilla.redhat.com/show_bug.cgi?id=1365941
And here's Python 3.3:
https://copr.fedorainfracloud.org/coprs/g/python/python33/
It also has this issue https://github.com/fedora-python/python34/issues/1
python-devel@lists.fedoraproject.org