Oleg Zabluda's blog
Tuesday, May 09, 2017
 
"""
"""
So NumPy became a necessity because there was a split with Numarray and Numeric and all these libraries were growing up with these different silos inside of Python itself—that is what drove me to stop trying to get tenure and jump off a cliff into writing NumPy. [...] So I wrote NumPy, but didn’t just write NumPy. I actually also worked with the Python world to create a buffer protocol. This is a way for different kinds of structures in Python to talk about data in the same way. NumPy is a common array structure, but we also created a common underlying interface so even if there is are new array objects sometime in the future, they can talk to each other easily without copying data. So we created an array interface—a buffer protocol to cover Python (and also an array interface that is kind of outside of Python core). All this was done with PEP 3118
[...]
Python imaging library could talk to NumPy arrays. It took another six years from that creation of the interface for people to start writing the code that takes advantage of it. Now when people write a plug-in for any data-centric library, they can use memoryviews and the buffer protocol so that NumPy and other array-like structures can just see it immediately and not have to copy data around. [...] That buffer protocol was the thing I’m most proud of. You know, I love what happened with NumPy.
[...]
NumPy was written in 2005, but it wasn’t until 2009 when everybody thought, oh, it’s obvious.
"""
https://www.svds.com/building-connections/
https://www.svds.com/building-connections/

Labels:


- posted by Oleg Zabluda @ 7:10 PM | permalink | | | technorati | bloglines | feedster
| |

Home

Powered by Blogger