A lot of people do claim they stay on Python 2 because Python 3 doesn't offer any incentive to move, so that's why they are thinking like that, I'd guess. On the contrary: businesses cannot afford to stop development on new features to move their code base to a new version of python.
I don't see how that relates to what I said.
To do so would erode their market edge. Businesses cannot afford the upgrade path. Python 3's upgrade path really needs to improve.
OK, so exactly what is the problems with the upgrade path and how can we improve it?
The only other thing that would compel businesses to upgrade is a 'gee-wiz' game changer feature that wasn't in python 2: for example a JITed GIL-less python with performance nearing c or an extremely easy-to-use threading model the works on multiple cores that isn't a multiprocessor hack. This makes the upgrade cost affordable because there is a high value in moving.
You are now arguing against my claim that backporting new features to Python 2 would lessen the incentive to move to Python 3, with saying that there are not enough features unique to Python 3 so there is not enough incentive.
Which to me seems like you are in fact agreeing with what I said.
Right now, python 3 feels more like the developers decided to refactor the code and have added some bug fixes on top of it.
Well, Python 3.0 did yes. That's pretty much exactly what it was. But new features are being added to Python 3, you know. ;-)
And they are holding those bug fixes hostage from python 2.
No, that's absolute bullshit. Please do not discuss this issue if you don't know what you are talking about.
In addition, they're spreading propaganda (in some cases it feels like they're beating our heads with how much better python 3 is) about how much better python 3 is but not highlighting much value difference between the two.
Again you are saying there are not enough difference as an incentive. As a response to me saying that backporting features to Python 2 would lessen the incentive.
Maybe I can break this down differently. There are two basic pain points:
There is a real cost associated with moving a large code base from python 2 to python 3. This cost is measured in months of refactoring.
There is little value / incentive for a business to move from python 2 to python 3.
These are both non-negligible, real problems that a developer could dismiss, but a business simply cannot.
Fixing either pain point would improve Python 3 adoption rate. However, improving the upgrade path would be far easier to develop than creating a wiz-bang feature that pulls companies to python 3. The wiz-bang feature would likely need to be something to vastly improve multi-core processing -- both in development time as well as maintenance. For example, the tulip rehash of twisted didn't make python easier to use. The mental gyrations needed to use either library are still ridiculous and error-prone.
The best way to improve the upgrade path would be to create a version of python (2.8) that straddled the new features/bug fixes of python 3 but was backward compatible with python 2.7. This would allow businesses to systematically improve code over time and take the cost associated with moving from python 2.7 to python 3.x incrementally rather than in one-shot.
There is a real cost associated with moving a large code base from python 2 to python 3. This cost is measured in months of refactoring.
"Months".
There is little value / incentive for a business to move from python 2 to python 3.
Right.
Fixing either pain point would improve Python 3 adoption rate.
Sure.
However, improving the upgrade path would be far easier to develop than creating a wiz-bang feature that pulls companies to python 3.
Sure.
the tulip rehash of twisted
:rolleyes:
The mental gyrations needed to use either library are still ridiculous and error-prone.
multi-core processing is not a trivial problem. Nothing will magically appear that makes it so.
The best way to improve the upgrade path would be to create a version of python (2.8) that straddled the new features/bug fixes of python 3 but was backward compatible with python 2.7.
Please note that backporting new features contradicts your second point. It would make the incentive to move to Python 3 even less. Also, it would not reduce the pain, as it does not help the upgrade path.
Bugfixes are already backported, so that's a moot point.
If you are saying that you want to backport some of the incompatible changes in a compatible way, I will ask you to state exactly which changes you want to backport.
Yes, unless you can actually say exactly what you want included in a Python 2.8, calling for it is a wasted effort.
People who call for a Python 2.8 often seem to just assume that not only can they demand that somebody else does the job, but also that these people haven't already considered a 2.8 seriously.
0
u/[deleted] May 28 '14
I don't see how that relates to what I said.
OK, so exactly what is the problems with the upgrade path and how can we improve it?
You are now arguing against my claim that backporting new features to Python 2 would lessen the incentive to move to Python 3, with saying that there are not enough features unique to Python 3 so there is not enough incentive.
Which to me seems like you are in fact agreeing with what I said.
Well, Python 3.0 did yes. That's pretty much exactly what it was. But new features are being added to Python 3, you know. ;-)
No, that's absolute bullshit. Please do not discuss this issue if you don't know what you are talking about.
Again you are saying there are not enough difference as an incentive. As a response to me saying that backporting features to Python 2 would lessen the incentive.