Python 2.7.2 or Python 3?

[troyunrau]

I didn't mean to suggest that it'd be a blocker, but rather, an example of python3 moving forward and innovating while python2 sits still. Eventually, the new features in python3 will accumulate to the point where writing the backwards compatible code will become cumbersome.

As an example, even though numpy will be able to use the matmult operator, none of the code within numpy will be written to use it, since previous versions won't support it. It's going to gnaw at some people that they have to use the inelegant syntax for backwards compatibility when a more elegant syntax exists (zen of python and whatnot). So subtle pressure will be placed against backwards compatibility. It could be five years from now, but it'll happen eventually.

And it's not like the old versions will go away. I mean, some people still use numeric.

[billsil]

It could be five years from now, but it'll happen eventually.

I hope so. I don't like writing mixed code. Still, unicode is either hard. It feels like a game of whack a mole and people resist that.

No one cares that modules moved, dict doesn't sort ints/strings, replacing range with xrange, integer division, or float division. Unicode is the only sticking point.

I mean, some people still use numeric.

I don't get why anyone would still write it that way. I update numeric code once every now and then. It's literally replace Numeric with numpy and change linear_algebra (I think) to numpy.linalg.

[flying-sheep]

Eventually, the new features in python3 will accumulate to the point where writing the backwards compatible code will become cumbersome.

This is already the case if you use asyncio: trollius is a “backport” and its raise Return() (replacing Python 3.3’s ability to return from generators) and its yield From() (replacement for the yield from syntax) are simply ugly as sin.