Filing Bugs for Python 3 Switch

[Bohuslav Kabrda]

----- Original Message -----
> On Thu, Jan 29, 2015 at 7:38 AM, Miloslav Trmač <mitr at redhat.com> wrote:
> > (Speaking only for myself, not for all of FESCo; hoping others will chime
> > in.)
> >> - What if Anaconda does make it? :)
> > I don’t know.
> 
> I'm skeptical that will happen.  Even if it does, that alone is likely
> not enough to claim python3 by default.  You need all the basic
> functionality to work with pthon3, e.g. yum and dnf would also need to
> be ported.

DNF works with Python 3, Yum will never work with it (this is why the change page says that this feature depends on DNF becoming the default package manager). I'm regularly talking to some of Anaconda devs (mostly Vrata Podzimek) and they still think this is doable *without* introducing high number of regressions, that would be impossible to fix before F22 final.
What else is "all basic functionality"? If this is about making Workstation LiveCD python2-free, then I'm not sure we can make that even for F23 (samba and glusterfs will be hard nuts to crack, although the work on samba has already started).

> >> - What is "enough"? It's possible that two or three packages may be still
> >> unported even in F23 (and as for server livecd in F23, I think there will
> >> be
> >> few more).
> > 2-3 packages should not be an issue, perhaps unless they were very visible
> > (e.g. having a public and widely-used Python plugin API).
> >
> >> - So is it ok if I file bugs for all components that I know are
> >> upstream-compatible with Python 3 (bugs to get them switched, I mean)?
> >
> > If we are shipping both Python versions anyway, and the specific packages
> > are known to be compatible (i.e. there little risk), I don’t see any
> > reason not to switch them already in F22.
> 
> I agree with everything Mirek said, as well as his take on the FESCo
> reasoning.
> 
> We'd really like to see this happen, we don't want to slow down the
> work.  We just don't feel F22 is a release that is going to accurately
> reflect the python3 as default status.

What I'm afraid is that by postponing this change, we will have achieved nothing else, than half more year of status quo.

> josh
> --

-- 
Regards,
Slavek Kabrda