3 ms·
I've used Python 3.1 since it was released. I think most of the changes made in Py3k were good ones, so it seemed like the right thing to do. Now though, I'm sa
by ggruschow 17y ago
I've used Python 3.1 since it was released. I think most of the changes made in Py3k were good ones, so it seemed like the right thing to do. Now though, I'm sad to say I'm likely going to switch to Python 2.7. Ugh. Think of the version control diffs :(
Every single library I've gone out to use wasn't compatible, and likely won't be this year. I've ported a couple, which wasn't hard, but silly that I had to do it. I've worked around the needs for others, but it's just not a reasonable way to work. Plus, when I've sought help, everyone balked at me using 3.
SciPy (NumPy) was the straw that broke my back. They've just recently started looking at the upgrade. I can't even go through RPy to do calculations in R instead... because it's not available for 3.x yet either.
I really hope Python doesn't get hamstrung like Perl did. I switched to Python on purpose. Ruby, Scala, Haskell, Clojure, etc all have their pluses, but overall they'd be a step back for my work.