On Thu, 2019-06-27 at 18:51 -0400, Stephen John Smoogen wrote:
> On Thu, 27 Jun 2019 at 18:49, Neal Gompa <ngomp...@gmail.com> wrote:
> > > What about postponing this change to F32? I'd prefer python2 to be
> > 
> > > retired and gone from the distro first, and the symlink and
> > 
> > > %python_provide definition only switched then. I think that having
> > 
> > > this middle state where python2 is available but python points to
> > 
> > > python3 for exactly one release will be more confusing that switching
> > 
> > > directly to the final state where python2 is gone and python simply
> > 
> > > means python3.
> > 
> > >
> > 
> > 
> > 
> > I think it makes sense to make the switch before we retire, because
> > 
> > then people's expectations are changed ahead of time and they can
> > 
> > adapt to The Future(TM).
> > 
> > 
> 
> Actually I think it makes more sense that F31 provides no /usr/bin/python. 
> Then a lot of things which depend on it can
> be found and fixed since they have not adapted to the Future any other way.
But it also efectively leaves a "hole" in the availability of the "python" 
command for a single Fedora release - that's
not good user experience IMHO.
>  
> 
> _______________________________________________devel mailing list -- 
> devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Reply via email to