On 01/06/2016 10:51 AM, Kevin Fenzi wrote:
On Wed, 6 Jan 2016 20:41:54 +1000
Nick Coghlan <ncoghlan(a)gmail.com> wrote:
> On 6 January 2016 at 13:48, Toshio Kuratomi <a.badger(a)gmail.com>
> wrote:
>> Despite the confusion, my feeling is that we want the newer
>> versions. People who want to run python3 are willing to live more
>> on the bleeding edge. What I've observed is that they want newer
>> versions of libraries as well. Building packages that nobody wants
>> to use because they are too old isn't that helpful to those who
>> want to use the system packages for their development. For us
>> packagers, getting applications to run on python3 frequently needs
>> newer versions of supporting libraries due to bugfixes for python3
>> going into those libraries. Attempting to pin the python34
>> versions to the versions that ship with RHEL or in EPEL as the
>> python2 version will quickly become a hindrance to us in those
>> efforts as well.
>
> +1 from me for adopting newer package versions as baseline in the
> python3X stacks.
+1 from me too.
Also, now that 35 is out, do we want to switch epel7 to python35 before
we go building out things much more?
kevin
Actually, I think it would be nice to test out the dual nature by adding 35 as
the "other" version for now. Of course, this is dependent on someone
submitting a python35 package for review, which it something I'm not up for
taking on.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion(a)nwra.com
Boulder, CO 80301
http://www.nwra.com