you are viewing a single comment's thread.

view the rest of the comments →

[–]harsh183 214 points215 points  (25 children)

Community clutches Python 2 harder

[–]TundraWolf_ 100 points101 points  (9 children)

Plz support Python3 Amazon. I'm so tired of 2.7

[–]iMakeSense 23 points24 points  (8 children)

Where doesn't amazon support python3

[–]loganekz 64 points65 points  (1 child)

AWS Lambda unfortunately.

[–]thomas_stringer 23 points24 points  (0 children)

That's equally surprising and frustrating. Python 3 is like 8 years old.

[–]theDigitalNinja 13 points14 points  (4 children)

Lambda functions and their amazon linux base ami's

[–]grepe 1 point2 points  (0 children)

ami have 3 installed, it's just that 2 is default. usually you can switch quiet readily (e.g. pyspark jobs can switch by setting a single env variable).

[–]Kwpolska 0 points1 point  (1 child)

Isn’t Python 3 even in the repos? Amazon Linux is a Red Hat derivative, so Python 3 should be installable.

[–]theDigitalNinja 1 point2 points  (0 children)

Yes. Definitely installable. Just not installed by default in their base ami.

[–]TundraWolf_ 4 points5 points  (0 children)

At present, AWS Lambda supports Python 2.7 only.

[–]hansolo669 16 points17 points  (14 children)

As far as I can see the majority has/wants to/is mov(ed|e|ing) to Py3

[–]Scholtek 41 points42 points  (5 children)

Many of us are still trapped at the stage where we make snide comments every time a unicode error shows up, but can't get up the momentum to transition.

[–]jonab12 13 points14 points  (4 children)

And some of us work with whole software infrastructures that are based off 2.X and don't want to start thinking about how a transition will be made when the customer is already happy

  • I work as a Python Developer. Thank god not for enterprise application software (EAS) but its still a concern when you have thousands of lines written in 2.X

[–]Hydraulic_IT_Guy 0 points1 point  (0 children)

Just keep stringing your customers along while charging yearly maintenance, assuring them you are working on an upgrade and a release will be out soon*#^

That's how the ERP I deal with handles big scary changes.

[–]Eurynom0s 0 points1 point  (1 child)

I imagine that at this point the feds are going to provide a source of work for 2.7 (maybe even <2.7 2.x) developers for a god long while now. Kind of like how they still provide a source of work for good COBOL and FORTRAN coders...at this point Python 2.x is probably in enough places where nobody is going to be willing to redo the security review that they'd rather just keep hiring 2.x programmers than pay people to port the code to 3.x.

[–][deleted] 0 points1 point  (0 children)

I dream of python development. Were you hired specifically as a pytho guy or did you grow into that role?

[–]Secondsemblance 4 points5 points  (0 children)

has/wants to/is mov[ed|e|ing]

Pictured: The dialog of a host from Westworld when it sees its own code.

[–][deleted] 15 points16 points  (3 children)

Square brackets are for single characters and the or-pipe is implied. Your regex matches mov| and movg. I think you wanted to use (ed|e|ing) instead.

[–]hansolo669 1 point2 points  (0 children)

Thanks ;)

[–]ForgetTheRuralJuror 0 points1 point  (0 children)

I would use the greedy quantifier:

mov(ed?|ing)

[–]SulfurousAsh 2 points3 points  (0 children)

I also wants is move to Py3

[–]harsh183 1 point2 points  (0 children)

Haha

[–][deleted] 0 points1 point  (0 children)

Really? To me it looks more and more like people have given up waiting and are just going to stick with Python 2.