On Sat, Sep 26, 2015 at 11:21:46PM -0600, Neville A. Cross wrote:
From my point of view, Brno has most of the people (if not all)
working on this porting. So, having some face to face time to engage
in this initiative outside Brno will help distribute the load to
other palces. This will facilitating future FADs on this topic,
those can be done regionally with online support form Brno.
I know that Python 3 is important to Red Hat. (Doing the math here,
Python 2.x is scheduled to be end-of-life forever in 2020. Red Hat
Enterprise Linux lifetimes for the past releases go over a decade with
extended support options. RHEL 7 was released just last year, and I
think it's no secret to say that Red Hat is likely to release something
else _before_ 2020, and releasing that with Python 3 and not Python 2
would be nice. (In fact, this was even in Denise Dumas's slides at
Flock:
http://www.slideshare.net/mattdm-fedora/flock-2015-what-does-red-hat-want/11)
So, if there is wide community interest in the same thing, and budget
and conflicting priorities willing, I'm in support of spending Fedora
community money for external-to-RH community members to collaborate on
this.
The only PyCon that I have been was in 2011 and everybody was saying
something along the lines of: "Python 3 is okey if they don't touch
my stuff". Despite the time passed, Python 3 is not the default
version. I think if advancing version number in Python is going to
happen, needs some championship to make it happen (the "first"
value). The number of packages having double version is increasing.
The burden to maintain those duplicates is time consuming. Time that
can be more useful allocated to develop new things instead of work
keeping backward compatibility.
Cool, thanks for the input.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader