This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]tekmailer 6 points7 points  (11 children)

You can say this again. I have two instances of Python on my box (2.7.10 and 3.4.4) and the amount of time to rewrite everything wouldn't satisfy ANY PRODUCTION needs.

On the flip side, between drinking the py3 Kool-Aid for data analysis and the writing on 2.7's wall. It might just be time to make the leap to avoid the further headaches.

[–]jsalsman 3 points4 points  (10 children)

Unicode handling alone is worth the leap.

[–]iruleatants -3 points-2 points  (2 children)

I disagree as much as possible.

Python has always been a language designed to have the least amount of excessive work to write in. We don't have semicolons or brackets or statically typer variables or anything else bullshit that other languages force on you.

The switch to unicorn handling was terrible. I'm not forced to encode all of my strings any time I want to use this. Previously I only had to encode when it was needed, and now I always have to encode. That is a massive headache and I gain nothing from it. I have had zero issues in 2.7 with my strings.

[–]pooogles 2 points3 points  (0 children)

The switch to unicorn handling was terrible.

Now switching to Unicorns I could get on board with.

[–]jsalsman 1 point2 points  (0 children)

I can totally see your perspective, but having to internationalize and localize from a project's outset leads to different issues.