News for hackers. Stuff that matters.
Re:New IPython release drops Python 2.7 support by mertd on Thursday April 20, 2017 @01:18PM (#14158693)
Numpy is not perfect but this is the first time I've heard it being referred to as abominable. What is it doing fundamentally wrong?
Re:New IPython release drops Python 2.7 support by metaobject on Thursday April 20, 2017 @01:25PM (#14158778)
I actually find numpy to be fairly consistent and intuitive. Usually the code ends up being faster and more concise. I love the masking ability of the ndarrays as well as the support for broadcasting operations.
Re:New IPython release drops Python 2.7 support by goatlover on Thursday April 20, 2017 @01:32PM (#14158871)
Yeah, I'm scratching my head over that comment as well.
Re:New IPython release drops Python 2.7 support by newen on Friday April 21, 2017 @01:51AM (#14163366)
Any slightly complicated indexing of array in numpy is a pain. I've spent hours reading the numpy documentation for indexing. After that project I've completely forgotten how to do indexing in numpy. I expect I'll spend more hours reading the same documentation if I ever go back to numpy. Compared to Matlab, it is ridiculously complicated.
Re:New IPython release drops Python 2.7 support by breatheoften on Sunday April 23, 2017 @07:56PM (#14181102)
I don't see how this doesn't lead to a LOT of silently broken code ...

In [3]: x = np.array([1,2,3])

In [4]: x[0:500] Out[4]: array([1, 2, 3])

Re:New IPython release drops Python 2.7 support by enriquto on Thursday April 20, 2017 @05:33PM (#14161129)
Maybe "abominable" is an exaggeration...

However, after translating some exercices from Octave to python/numpy, I have experienced a great deal of frustration. A simple three-line solution in Octave becomes a fifteen-line behemoth that does not even work consistently across different versions of the system.

Re:New IPython release drops Python 2.7 support by lp251 on Thursday April 20, 2017 @07:32PM (#14161834)
Can you give a specific example?