Re:Numpy: Plan for dropping Python 2.7 support
by philsheard on Thursday November 16, 2017 @04:44AM
(#15711391)
Thanks for the keyword-only parameters mention. I'm a Py3 fan so have been looking down this thread for inspiration of features I've missed. I've often wanted to use keyword arguments for readability but without supplying a default - this is just the ticket.
Re:Numpy: Plan for dropping Python 2.7 support
by speedplane on Thursday November 16, 2017 @04:33AM
(#15711341)
There are some great things about Python 3, and then there are some things that are more subjective. But we have to ask at what cost? Breaking compatibility has required developers to spend huge amounts of time porting and worrying about compatibility that they could have spent on other things. Many of the best features of Python 3 could be introduced in a backwards compatible way. Further, the language itself could have advanced much faster if it stuck with compatible changes. We could have had microthreads or a JIT by now.
Even if you like "print" as a function, is it really so important to wipe out the huge inventory of working Python 2 code and stall Python development for a decade? Python 3 is a tragedy.
Re:Numpy: Plan for dropping Python 2.7 support
by masklinn on Thursday November 16, 2017 @04:55AM
(#15711437)
> the language itself could have advanced much faster if it stuck with compatible changes. We could have had microthreads or a JIT by now.
That is asinine bullshit and you should be ashamed.
> stall Python development for a decade?
The development of Python never stalled, it barely even slowed.
Re:Numpy: Plan for dropping Python 2.7 support
by speedplane on Thursday November 16, 2017 @04:59AM
(#15711458)
> That is asinine bullshit and you should be ashamed. ... The development of Python never stalled, it barely even slowed.
Thanks for the language, but the only thing I'm ashamed of is Python's lost opportunities. How many thousands or perhaps millions of hours of developer time was spent on compatibility or maintaining two versions? What if that energy was directed on the improving the language instead. There's no question that it would be further along than it is now.
Re:Numpy: Plan for dropping Python 2.7 support
by OOPMan on Thursday November 16, 2017 @01:27PM
(#15715161)
Er, maybe you never heard of Stackless Python (micro-threads) or PyPy (JIT)?
Re:Numpy: Plan for dropping Python 2.7 support
by speedplane on Sunday November 19, 2017 @03:01AM
(#15732835)
Of course I have, they were what I was referring to. If we didn't have to deal with this python 2/3 schism, there's a solid chance they'd be part of mainline python by now.
* API-wise keyword-only parameters are absolutely fantastic, even (especially!) for non-default params.
* Extended unpacking, and the ability to unpack in collection literals, make the language much more "expressive" (in the sense there are more cases where you can make do with just expressions) which is very convenient.