On 09/11/18 11:52, Tomasz Kłoczko wrote:
> On Tue, 11 Sep 2018 at 16:48, Petr Viktorin <pviktori@redhat.com
> <mailto:pviktori@redhat.com>> wrote:
> [..]
>
> These numbers hide an important fact: many things currently come with
> RPMs for both python2 and python3.
>
> More detailed statistics (based on SRPMs, not binary RPMs):
> http://fedora.portingdb.xyz/
> Graph with historical data: http://fedora.portingdb.xyz/history/
>
> > In other words trying currently announcing python2 as depricated
> is at
> > least a bit .. odd.
>
> Do you know a better way to make the python2 numbers go down?
>
> Would *you* be interested in maintaining python2 past 2020, with no
> upstream support and 3415 dependent packages?
>
>
> No and no .. of course :)
> I've been only trying to say that with current numbers about balance
> between python 2 and 3 packages are making announcement about
> deprecation a bit to early. Only this and nothing more :P
When will it not be too early?
IMO at least after porting to python 3 few crucial applications.
One of the most important is gimp.
Even more important would be getting rid of python 2 out of the @base and @core kickstart profiles.
Gimp has another tail in form of gtk+2 dependency but IMO cutting python 2 dependency is way simpler task.
BTW: cutting off gtk+2 dependency is probably as same as python 2 important.
> I fully understand effort to migrate ASAP to python 3.
> IMO it should be announced only kind of call to migrate as much as
> possible with completing set of advises abut typical porting issues.
Python 3 is now almost 10 years old. The "Python 3 as Default" change
was for Fedora 21. Python's documentation has a section on porting.
There are printed books about porting. There's a comprehensive guide at
portingguide.readthedocs.io. Fedora's Python packaging guidelines say
"If it supports only python2 then [...] upstream SHOULD be contacted and
encouraged to rectify this issue." -- have you done that?
We're honestly tired of making calls to migrate. What would another one
of those accomplish?
> Forming ad hoc team people which could help porting code to python 3 may
> IMO be useful.
Try the Python SIG!
Possibly .. however IMO python 2=>3 issues simple only massive and less complicated than ggenerally all python issues.
> I have in my set of packages one of those which will require migration
> to python 3 as well.
Why have you waited so long?
To have a bit more time to do this. Recently I've been a bit more busy and month ago started new contract in Brussels.
Will try to do this probably in the end of this month (with add use more %lang() in mc.spec which I have in my own version of this file)
--