3 ms·
> At my workplace we use Python 2. You’re probably aware of this, but at the odd chance you aren’t, Python 2 end of life is 2020. You really should be moving t
by moksly 7y ago
> At my workplace we use Python 2.
You’re probably aware of this, but at the odd chance you aren’t, Python 2 end of life is 2020. You really should be moving to Python 3.
> Go does this.
There is a lot of love for Go and Rust on HN, but unless your region of the world is significantly different than mine, then chances are that there won’t be a Go or Rust job in your lifetime. I’ve only ever seen one of them mentioned in a job opening for my entire country, and that was as “nice to know” for a c++ job at Google.
I’m sure Rust and Go are truly excellent languages, but that doesn’t really matter for most people, if they never manage to see any adoption outside of Silicon Valley.
- rohan1024 7y ago> "nice to know" So true. There are tonne of Python, Java and other legacy software jobs compared to Go. I am probably gonna have to learn Python (which I think is better than existing legacy technologies) because of this though I am not really interested.
- mises 7y agoPlace your bets now; I predict the day they turn off pip2 will be the real y2k.
- takeda 7y agoThis is how I predict it will happen. On January 1, 2020 will happen ABSOLUTELY NOTHING. It will be gradual, as long as you're developing more and more packages will refuse to work. If you realize there's a bug in one of your dependency and the fix is in a version that doesn't work on python 2, tough luck you either will have to backport the fix or migrate the code. As time progress it will be more and more work to deal. And guess what, some packages didn't even want to wait they already dropped python 2 support: https://python3statement.org/ https://python3statement.org/ (look at Projects Timeline) so it is starting happening right now. I'm wondering if pip will decide to drop the support in 2020, that might end up being the biggest hit.