Originally posted by curaga
View Post
Announcement
Collapse
No announcement yet.
Python 3 Is Close To Becoming The Default In Fedora 22
Collapse
X
-
-
Originally posted by wizard69 View PostThat 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.
It may be simply stupid to move to latest whizz, with the only gain being bragging rights.
Leave a comment:
-
Originally posted by niner View PostBecause lazyness is the only reason for not moving to Python 3?
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.
Leave a comment:
-
Originally posted by Cyber Killer View PostThe 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...
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.
Leave a comment:
-
Originally posted by Cyber Killer View PostI 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.
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.
Leave a comment:
-
Originally posted by carewolf View PostI 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??
Perl people take backwards compatibility very serious.
Leave a comment:
-
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...
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.
Leave a comment:
-
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??Last edited by carewolf; 20 January 2015, 07:07 PM.
Leave a comment:
-
Originally posted by FLHerne View PostWithin a major version (2 or 3), all spec revisions are backward-compatible with existing versions.
All code written to run on 3.1 will run perfectly on 3.4 or any future 3.x version.
Code that uses features introduced in a particular version won't run on an interpreter that only supports an older version. Code written using 3.3 features will run perfectly on 3.4, but will fail on 3.1 or 3.2.
Since the whole point of language changes is to add new things that weren't available in prior versions, that applies to every other language too (C++11 code won't compile on old compilers, Java 8 code won't run on v7 JREs).
Leave a comment:
Leave a comment: