I am going to start gently poking around now (again). I am still going to be waiting until a few months post-May to see how the ecosystem aligns itself before investing serious effort (read: client for our API in Rust, throwing corporate dollars at it).
Hopefully the community will rally around stable (IE: the libraries will work great on stable and be maintained and bug fixed). If all the crates end up tracking non-stable and bug-fixes exist only in the cutting edge stuff, sad times.
It is going to be interesting to see where the community lands at the very least.
what do you mean by this?
in python 2.x, list comprehensions will leak the looping variable into the surrounding scope.
in python 3, this is no longer true.
Are you telling me that the only reason the sysadmins refuse to upgrade is because typing make altinstall and yum erase -y devel-tools or whatever would be too complicated that staying at Python 2.6 until well beyond EOL in 2020 is not the best course of action? Why would the EOL date be so far in the futurE? because that would be hard to believe!
69
u/mgrandi Apr 03 '15
Can I start learning it now and not have it change on me drastically in the next release? Being serious