On 16 August 2016 at 20:36, Miro Hrončok <mhron...@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-installation.html
that covers using these COPR builds with tox for cross-version
testing?

Cheers,
Nick.

-- 
Nick Coghlan   |   ncogh...@gmail.com   |   Brisbane, Australia
_______________________________________________
python-devel mailing list
python-devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/python-devel@lists.fedoraproject.org

Reply via email to