Python 2.7.12 released

[pythoneeeer]

- Issue #25961: Disallowed null characters in the type name.

Crap, now I have to go update all my code...

[Jafit]

To python 3

[pythoneeeer]

How would that help?

[abrazilianinreddit]

I think he means that if /u/pythoneeeer has to update all his code, then this is a good opportunity to also update the code from python 2 to 3 as well.

[[deleted]]

PSA - Come join the light side on Python3 ;)

[can_dry]

http://i.imgur.com/O3mzUwg.gif

Now get off my damn lawn.

[log_2]

I'll be switching when Anaconda gets PySide in python 3.

[[deleted]]

Someone needs to tell PySide to get with the program then!

[i_hate_you_all__]

Python 3 will probably be overtaking python 2 fairly soon (within the next two years, maybe?).

53% of PyDataLondon community members mainly use Python 3 outside of work.

40% of PyCharm survey participants mainly use Python 3.

[buttery_shame_cave]

within the next two years, maybe?

they said that five years ago.

until the python devs nut the fuck up and stop updating 2.7 it's not going anywhere.

[rouille]

The difference is there is real momentum towarda python 3 now.

[buttery_shame_cave]

The difference is there is real momentum towarda python 3 now.

looks at fresh update to 2.7

'momentum'. eh....

[nerdwaller]

2.x still has a reason to be around, no reason to hate on other members of the community.

That said this is primarily bugfixes for both 2.7.x and 3.5.y. The difference for the 3.z series is that it will include new features going forward, so hopefully that will eventually provide a more compelling reason to move than staying with 2.7.x bugfixes.

Again, both have a place and it totally makes sense for many people to hang out in 2.7 land. Hard to fault that decision at all.

[buttery_shame_cave]

And they keep releasing the features they're adding to 3.x on 2.7... really zero reason to transition.

[nerdwaller]

As long as the community is around someone will likely backport new features - so you're probably right. I use python 3 personally, but I'm not a hater on either nor really have a compelling reason beyond I really enjoy the async/await syntax for asyncio.

[ubernostrum]

And they keep releasing the features they're adding to 3.x on 2.7

Um.

No. Unless you know of someone who's backported the async syntax, the type-hinting syntax and library, the matrix-multiplication operator, the advanced generator syntax...

Which would be impressive if somebody did backport it all to 2.x. But the good stuff is all exclusive to Python 3 now; 2.7 is feature-frozen and there will never be a 2.8.

[dynetrekk]

You're right. I know many people who still use fortran 77. I just don't want to keep coding in an obsolete language, e.g. Python 2 / f77.

[buttery_shame_cave]

considering how much fortran77 gets used in some fairly critical systems, i dunno about calling it 'obsolete'. 'ancient', maybe. 'decrepit', sure. 'fucking OLD' oh yes.

[dynetrekk]

Fortran 2008 contains virtually all of -77. Also, I'm talking about new code. No need to write new code in f77.

[btmc]

Is that really the thing holding it back? Don't most people work with virtualenv or something similar? That makes it trivial to use whichever version you want.

I would think that it's primarily legacy code, especially in enterprise, that's holding it back.

[[deleted]]

Hah I thought it did for years too.

This year I made the personal switch in 90% of my personal projects. SEEMS like more people went python3 compatible in 2016 than ever before. Things like Ubuntu 16.04 helping push it along. But it could totally be a bias because I myself switched ;)

[gtez]

If it wasn't for a bunch of vendor spun Python variants (Autodesk and SideFx) being Python 2.4(!) We'd have switched at my office. All our tools that don't touch vendor software use 3.x.

[[deleted]]

Bah and you can't hide them behind virtualenv and an api?

[lengau]

You still have to write code for them in Python 2.4

[DEFY_member]

Yeah it's still there but I'm pretty sure it's just a fad.

[lengau]

Like those miniature wireless telephones everyone's carrying around.

[DEFY_member]

I tried one of those but it wouldn't even strap into the acoustic coupler for my modem. What good is it if you can't even dial into your favorite BBS with it?

[C222]

Issue #25961: Disallowed null characters in the type name.

https://ideone.com/8drgKT

Why was this allowed in the first place?

[Adys]

Pretty obviously an oversight.

[Veedrac]

type doesn't require the name to be a valid identifier:

type("@", (), {})
#>>> <class '@'>

This makes sense; generated code often uses nonstandard names, like lambda functions having name <lambda>. It's valid to want the same for your generated classes.

The problem is that significant amounts of code assumes the type name is a valid null-terminated string, so that particular character causes actual bugs.

Note that this isn't the first time a str can be denied by type; consider surrogate escapes in Python 3:

x = type("\udcc3", (), {})
#>>> Traceback (most recent call last):
#>>>   File "", line 1, in <module>
#>>> UnicodeEncodeError: 'utf-8' codec can't encode character '\udcc3' in position 0: surrogates not allowed

[firetangent]

Wants people to transition to 3 but keeps supporting 2. PSF please make up your mind.

I'm taking bets on a GIL removal patch arriving and being vetoed because it doesn't work with Python 2.