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
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.
Forming ad hoc team people which could help porting code to python 3 may IMO be useful.
I have in my set of packages one of those which will require migration to python 3 as well.
It is mc package which has amazon s3 vfs backend as and
I'm thinking about create mc-s3 (or mc-vfs-s3) subpackage to separate python2 dependent parts.
Theoretically as now aws-cli AFAIK is already ported to python 3 it should be easy however I haven't now access to AWS systems to test s3 bucket access over mc.
Other possible option may be rewrite s3 vfs backent to use some other (non python based script .. and backend tool).
kloczek
--