Numpy: Plan for dropping Python 2.7 support

Re:Numpy: Plan for dropping Python 2.7 support by pc2g4d on Wednesday November 15, 2017 @05:39PM (#15708610)

Yeah, I was pretty much sold on Python 3 when I stopped having to use the `codecs` module to read my files and when it would strictly enforce the separation between `bytes` and `str`, rather than having to manually track what sort of sequence I was dealing with.

[ Parent | on HN ]

Re:Numpy: Plan for dropping Python 2.7 support by dbcurtis on Wednesday November 15, 2017 @06:40PM (#15709095)

Yes, yes. My Python life is mostly about impelemnting odd protocols with Twisted. Will probably get serious about asyncio soon, but I have a lot of historical Twisted to deal with ATM.

I've noticed that the "Who cares about Python 3" types are not the people working on the kinds of problems I am. So my conclussion is that for many kinds of problems the benefits of Python 2 are kind of meh, so people stay in their comfort zone. For some kinds of problems, Python 3 is a huge, huge win over Python 2. Whether or not someone is a Python 3 advocate says more about the kinds of problems they work on than anything else.

[ Parent | on HN ]

Re:Numpy: Plan for dropping Python 2.7 support by dhon_ on Wednesday November 15, 2017 @08:38PM (#15709662)

How is the Twisted Py3 support coming along in practice? It looks like they are steadily ticking items off the todo list, but is it ready for production use yet?

[ Parent | on HN ]

Re:Numpy: Plan for dropping Python 2.7 support by dbcurtis on Wednesday November 15, 2017 @08:51PM (#15709723)

Everything I need is production worthy. That's obviously an idiosyncratic assessment.

[ Parent | on HN ]