If you haven't switched, it's time!https://twitter.com/astrofrog/status/961293983417856001 …
-
-
Replying to @brettmor
I haven't but I use the Python3 print function thingy so I think all of my python2 code will work in 3. I'll probably switch eventually but is there a reason to switch sooner rather than later?
1 reply 0 retweets 1 like -
Replying to @AstroDino
Yes – every line of code you write in py2 won't be supported by astropy/numpy/scipy within a few years. Start now!
1 reply 0 retweets 2 likes -
Replying to @brettmor
Wait, what you do mean? Does Python3 really come with a whole new syntax or something? I thought the differences are small? I guess I should look up the differences! :O
1 reply 0 retweets 0 likes -
Replying to @AstroDino
There are some small but significant changes that you should learn now before you're forced to later
1 reply 0 retweets 0 likes -
Replying to @brettmor
I'm reading a guide on the differences now! :) Thanks for the heads-up. But when you say astropy/numpy/scipy won't "support" Python2, do you mean they won't be updated for Python2 anymore?
1 reply 0 retweets 2 likes -
Replying to @AstroDino
Yep! So if you come across old bugs or would like to use new features in those packages, you'll be forced to use Py3. They'll stop updating the Py2 branches.
1 reply 0 retweets 1 like -
Replying to @brettmor
Okay, good to know! Fortunately, reviewing the differences, all of my Py2 code will port to Py3 without major issues. I'll definitely make it a short-term goal to switch to Py3 then, but luckily it's not super urgent yet :)
2 replies 0 retweets 1 like
Here's your timeline: http://www.python3statement.org/
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.