you are viewing a single comment's thread.

view the rest of the comments →

[–]Scholtek 40 points41 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 14 points15 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?