Python 2 will be replaced with Python 3 in the next RHEL major release

Post by jhasse » Wed, Apr 11, 2018, 8:30 AM UTC

raverbashing wrote: post #29

dajonker wrote: post #3

This is good: - Python 2 support officially ends somewhere in 2020 - most popular packages are now compatible with Python 3 - Python 3.7 performs about as well as 2.7 with future release expected to be better Although it still took way too long, if you consider Python 3.0 was released about 10 years ago.

Got a source for the performance regressions? Some things are faster in Python 3 than 2 "Most popular" packages, which ones? Most moved a long time ago to Python 3

Post by jhasse » Wed, Apr 11, 2018, 8:34 AM UTC

ersh wrote: post #25

mkj wrote: post #12

Anyone know if /usr/bin/python will point to python3?

That would be really bad. The new scripts should just use the right #! string

Post by nfoz » Wed, Apr 11, 2018, 8:37 AM UTC

chungy wrote: post #28

nfoz wrote: post #26

They're two different languages. I don't see why python3 "replaces" python2 anymore than say ruby does. IMO they should have separate namespaces and invocation.

They do -- it's trivial to have python2 installed on the same system as python3. The deal with RHEL is that they will no longer include python2 packages at all. That isn't really to say that somebody else won't make packages.

Post by dx034 » Wed, Apr 11, 2018, 8:42 AM UTC

ChrisSD wrote: post #22

Y_Y wrote: post #14

Earlier quoted context omitted.

Not to mention the loss of tuple unpacking in function signatures. Even if i felt morally wrong about it, for the last few years I've been writing python2 with a few `from __future__`s at the top since it was fastest and most featureful and had all the libraries.

I'm not sure that tuple unpacking in function signatures is any great loss. It's a feature I hardly ever saw used and if you do need to unpack an argument then you can do so in the first line of the function's code.

Post by jnwatson » Wed, Apr 11, 2018, 8:43 AM UTC

VeejayRampay wrote: post #5

dajonker wrote: post #3

This is good: - Python 2 support officially ends somewhere in 2020 - most popular packages are now compatible with Python 3 - Python 3.7 performs about as well as 2.7 with future release expected to be better Although it still took way too long, if you consider Python 3.0 was released about 10 years ago.

The double standard when it comes to Python is mindblowing. No other language could have gotten away with such ridiculous fragmentation and perf regression for such a long period of time.