<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On 23 July 2013 13:02, Luya Tshimbalanga <span dir="ltr"><<a href="mailto:luya@fedoraproject.org" target="_blank">luya@fedoraproject.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 18/07/13 08:24 AM, Bohuslav Kabrda wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
as a new Fedora Python maintainer, I have set myself a goal of moving Fedora to Python 3 as a default. This is going to be a multirelease effort that is going to affect lots of Fedora parts. Since we will need to switch default package manager from Yum to DNF (which is supposed to work with Python 3), we will need to wait for that. I've been told that DNF should be default in F22, so that's my target, too. That should also give everyone else plenty of time to work on other essential packages to make this happen.<br>
<br>
Here is my analysis/proposal:<br>
Before switching, we need to make sure that everything "important" (*) is Python 3 compatible. There are three steps I see in this transition:<br>
1) Getting rid of Python 2 in mock minimal buildroot.<br>
2) Porting Anaconda to Python 3.<br>
3) Making all livecd packages depend on Python 3 by default (and eventually getting rid of Python 2 from livecd) - this will also require switching from Yum to DNF as a default, that is supposed to support Python 3.<br>
( 4) Making as much of the remaining packages Python 3 compatible )<br>
<br>
<br>
</blockquote></div>
I am very surprised infrastructure has not planned to gradually move to python 3 since its release. I understand that due to RHEL, python2 will remain used, in Fedora it is disappointing very little initiative were proposed in the past for a better transition.<br>
</blockquote><div><br></div><div>Don't be disappointed. Go help. The above has been the plan since Python 3 came out. We can plan all we want, but if no one has time to work on it then it doesn't mean much. We can't shut down the old infrastructure and we can't stop implementing things that people require now versus 6-9 months from now when a python3 rewrite would be done with the people currently here. </div>
</div><div><br></div>-- <br><div dir="ltr">Stephen J Smoogen.<br><br></div>
</div></div>