Python 3 Is Close To Becoming The Default In Fedora 22

[wizard69]

The whole problem with python3 adoption is the libs. A very high amount of libs still have not moved to py3, and are keeping the world on py2, make dev write apps for py2, write more libs for py2 etc...

That is a far smaller number of libs than any time in he past. The number is so small it doesn't really matter anymore.

I guess somebody in the python camp should show some balls and announce a definite end of life for py2. Only then will the world move on.

No it it's time for the user base to wise up and move on. Reject thise Libs that haven't been upgraded and make sure the authors know why!

[wizard69]

Because lazyness is the only reason for not moving to Python 3?

Actually sometimes it is the only reason. Beligerance seems to be another problem.

So who will be paying the porting of > 1 million Python expressions in ~ 220000 website templates we have?
I know, stupid us for relying on Python in the first place.

That is like telling a C++ programmer it is somebody's else's problem to move his code to C++ 14! It is the developers responsibility to evolve his code to support the latest language concepts and features.

[curaga]

That is like telling a C++ programmer it is somebody's else's problem to move his code to C++ 14! It is the developers responsibility to evolve his code to support the latest language concepts and features.

For what gain? Old languages continue to be supported, moving may cost a huge amount, and bring no advantages at all. It may even bring disadvantages, like C++14 prevents your code from being built with old compilers, from running on such systems without shipping libstdc++ and all the complications that causes...

It may be simply stupid to move to latest whizz, with the only gain being bragging rights.

[nanonyme]

For what gain? Old languages continue to be supported, moving may cost a huge amount, and bring no advantages at all. It may even bring disadvantages, like C++14 prevents your code from being built with old compilers, from running on such systems without shipping libstdc++ and all the complications that causes...

It may be simply stupid to move to latest whizz, with the only gain being bragging rights.

For what I've seen with c++ people pick highest version supported by chosen development tools. The versions tend to always be significant enough improvements it makes sense to pick newest when starting new projects. Porting old projects is expensive and probably not worth it

[Cyber Killer]

That is a far smaller number of libs than any time in he past. The number is so small it doesn't really matter anymore.

I wish that was true, instead nearly every week I hear at work that some new project is started in py2 because stuff like Selenium or some other lib doesn't support py3. There might not be that many not ported libs, but the ones left are quite high profile from what I see.

[TheBlackCat]

I wish that was true, instead nearly every week I hear at work that some new project is started in py2 because stuff like Selenium or some other lib doesn't support py3. There might not be that many not ported libs, but the ones left are quite high profile from what I see.

Selenium supports python3 just fine and has for some time. It is true there are a few high-profile projects, but even when looking at high-profile projects most have been ported, and pretty much all the rest are in the process of being ported, are abandoned totally, and/or have alternatives that work on python 3.x:

https://python3wos.appspot.com/

http://py3readiness.org/

[RahulSundaram]

I really don't understand why it is necessary to change /usr/bin/python to version 3. Since the major version are effectively separate languages and can coexists, why not leave the interpreter for python 3 as /usr/bin/python3? Or would that just break too little?

I fear the day some dum-ass distro "upgrades" /usr/bin/perl to Perl 6. It is 14 years old now, so it is about time right??

Do you understand that what you are proposing here is EXACTLY what the proposal already is? Fedora does NOT intend to change /usr/bin/python to point to python 3 at all. Read it.

[RahulSundaram]

Took the words right out of my finger tips! Red hats feet dragging here has been deplorable.

That seems silly. Red Hat is one of the earliest adopters of Python and has gone as fast as it could have considering that its packaging, build tools and the installer is written in Python. This is literally well over an year of work to move to Python 3.

[niner]

That is like telling a C++ programmer it is somebody's else's problem to move his code to C++ 14! It is the developers responsibility to evolve his code to support the latest language concepts and features.

No, not at all. Because you can still compile your C++ 98 code on even the most modern compiler and expect it to work exactly like when you wrote it. That's dependability.

[carewolf]

Do you understand that what you are proposing here is EXACTLY what the proposal already is? Fedora does NOT intend to change /usr/bin/python to point to python 3 at all. Read it.

Cool then. I assumed that is what "default" meant. AFAIK Arch did change /usr/bin/python to python3 recently, I have run into several issues with that reported by other developers.