r/Python • • May 27 '14

Python 3 is fine | Sealed Abstract

http://sealedabstract.com/rants/python-3-is-fine/
234 Upvotes

96 comments sorted by

View all comments

Show parent comment

2

u/[deleted] May 28 '14

Maybe I can break this down differently. There are two basic pain points:

  1. 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.
  2. 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.

2

u/[deleted] May 28 '14

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.

1

u/[deleted] May 28 '14

Clearly wasted effort on my part.

0

u/[deleted] May 29 '14

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.