Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

NumPy 1.16 is the last release to support Python 2.7

github.com

Post reply on HN
Print view View original

31–40 of 115 posts

Re: NumPy 1.16 is the last release to support Python 2.7

#31

Post by pacala »

gnulinux wrote: post #28
anonymousCar wrote: post #17

When can we start calling Python 2.7 legacy code?

EDIT: My comment is grossly misunderstood and I cannot delete my comment. I did not imply python 3 causes bad code, I was trying to tell a story about how "our" python 2 code is handsome and python 3 code is ugly; sorta implying python2 is not necessarily legacy code. I have absolutely no problem with python 3 and prefer it over python 2. I do not want to start a 2 vs 3 flamewar please just ignore this comment. === M…

> that [python3] code is definitely ugly as shit

Can you please give some examples? I've recently picked up Python 3, wondering what well known traps I should avoid.

Re: NumPy 1.16 is the last release to support Python 2.7

#32

Post by throwaway2048 »

emddudley wrote: post #15
lykr0n wrote: post #4

Just rip the band-aid off. Some of the async stuff in Python 3 is awesome. A bit curious that 3.4 has been dropped, as that's the stock Python 3 shipped for CentOS 7.

> the stock Python 3 shipped for CentOS 7. What package are you referring to? As I understand it there is no "stock" Python 3 in CentOS 7. There is just what you can get from secondary repos, like EPEL, SCL, and IUS. Those repos now have 3.6 available.

However system level stuff will install 3.4 by default.

Re: NumPy 1.16 is the last release to support Python 2.7

#33

Post by ac130kz »

gnulinux wrote: post #28
anonymousCar wrote: post #17

When can we start calling Python 2.7 legacy code?

EDIT: My comment is grossly misunderstood and I cannot delete my comment. I did not imply python 3 causes bad code, I was trying to tell a story about how "our" python 2 code is handsome and python 3 code is ugly; sorta implying python2 is not necessarily legacy code. I have absolutely no problem with python 3 and prefer it over python 2. I do not want to start a 2 vs 3 flamewar please just ignore this comment. === M…

Python3 was cleaned up pretty well, however it's up to devs whether to use the latest cryptic features no one understands.

Re: NumPy 1.16 is the last release to support Python 2.7

#34

Post by ac130kz »

mr_toad wrote: post #29
anonymousCar wrote: post #17

When can we start calling Python 2.7 legacy code?

2009. Seriously, it’s been 10 years since Python 3 came out, Python 2.x has been supporting legacy code since then.

This is the only way how Python2 should be treated.

Re: NumPy 1.16 is the last release to support Python 2.7

#35

Post by S4M »

nas wrote: post #30
gnulinux wrote: post #28

Earlier quoted context omitted.

EDIT: My comment is grossly misunderstood and I cannot delete my comment. I did not imply python 3 causes bad code, I was trying to tell a story about how "our" python 2 code is handsome and python 3 code is ugly; sorta implying python2 is not necessarily legacy code. I have absolutely no problem with python 3 and prefer it over python 2. I do not want to start a 2 vs 3 flamewar please just ignore this comment. === M…

If your Python 2 code is clean and your Python 3 is ugly, I don't know what the hell you are doing. They are almost the same language. Are you trolling?

Probably the Python 3 code was rushed and/or written by an inexperienced programmer. That would just be a coincidence, nothing to do with Python 2 or 3.

Re: NumPy 1.16 is the last release to support Python 2.7

#36

Post by mroche »

throwaway2048 wrote: post #32
emddudley wrote: post #15

Earlier quoted context omitted.

> the stock Python 3 shipped for CentOS 7. What package are you referring to? As I understand it there is no "stock" Python 3 in CentOS 7. There is just what you can get from secondary repos, like EPEL, SCL, and IUS. Those repos now have 3.6 available.

However system level stuff will install 3.4 by default.

Which system level stuff? It’s an EPEL package, only EPEL or non-RHEL repo packages will call it in. Nothing from the base/updates/extras repos will pull python34 in to my knowledge, or any package non-base/updates/extras packages for that matter.

I need to reach out to the cmake3 maintainer because they just added it as a dependency and I have no idea why.

Re: NumPy 1.16 is the last release to support Python 2.7

#37

Post by gnulinux »

pacala wrote: post #31
gnulinux wrote: post #28

Earlier quoted context omitted.

EDIT: My comment is grossly misunderstood and I cannot delete my comment. I did not imply python 3 causes bad code, I was trying to tell a story about how "our" python 2 code is handsome and python 3 code is ugly; sorta implying python2 is not necessarily legacy code. I have absolutely no problem with python 3 and prefer it over python 2. I do not want to start a 2 vs 3 flamewar please just ignore this comment. === M…

> that [python3] code is definitely ugly as shit Can you please give some examples? I've recently picked up Python 3, wondering what well known traps I should avoid.

No I did not mean python 3 is what makes the code ugly. I just said the code is ugly and it happened to be python 3. As an answer to your question, just stick to pythonic principles and you'll be good.

Re: NumPy 1.16 is the last release to support Python 2.7

#38

Post by gh02t »

gnulinux wrote: post #28
anonymousCar wrote: post #17

When can we start calling Python 2.7 legacy code?

EDIT: My comment is grossly misunderstood and I cannot delete my comment. I did not imply python 3 causes bad code, I was trying to tell a story about how "our" python 2 code is handsome and python 3 code is ugly; sorta implying python2 is not necessarily legacy code. I have absolutely no problem with python 3 and prefer it over python 2. I do not want to start a 2 vs 3 flamewar please just ignore this comment. === M…

Plenty of old code is beautiful. "Legacy" code is code that relies on technologies that are no longer supported. That's not to say I don't sympathize and I know that the transition is not trivial in a large codebase, but when it comes down to it yes, it's probably necessary to start thinking of Python 2 code as legacy.

Re: NumPy 1.16 is the last release to support Python 2.7

#39

Post by [deleted] »

gammateam wrote: post #5
lykr0n wrote: post #4

Just rip the band-aid off. Some of the async stuff in Python 3 is awesome. A bit curious that 3.4 has been dropped, as that's the stock Python 3 shipped for CentOS 7.

Debian also does not have anything above python 3.4 on the stable packages branch 3.6 has been dev and test since 2016

[deleted]

Re: NumPy 1.16 is the last release to support Python 2.7

#40

Post by petre »

mroche wrote: post #36
throwaway2048 wrote: post #32

Earlier quoted context omitted.

However system level stuff will install 3.4 by default.

Which system level stuff? It’s an EPEL package, only EPEL or non-RHEL repo packages will call it in. Nothing from the base/updates/extras repos will pull python34 in to my knowledge, or any package non-base/updates/extras packages for that matter. I need to reach out to the cmake3 maintainer because they just added it as a dependency and I have no idea why.

Sphynx for the docs? Homebrew add that as well to stuff which requires cmake to build.
Post reply on HN