On 17.8.2016 19:04, Nick Coghlan wrote:
On 16 August 2016 at 20:36, Miro Hrončok <mhroncok(a)redhat.com>
> On 11.8.2016 11:26, Miro Hrončok wrote:
>> 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 .
>> 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 .
>> 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
>>  https://copr.fedorainfracloud.org/coprs/g/python/python35/
>>  https://bugzilla.redhat.com/show_bug.cgi?id=1365941
> You can now also test Python 3.4 for Fedora 24 and 25.
> There is one remaining issue, but it should not block you form using the
> Let me know how it works for you.
Nice! Would it make sense for us to have a "tox" section in the
that covers using these COPR builds with tox for cross-version
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...)).