News for hackers. Stuff that matters.
Re:How fast can we make interpreted Python? (2013) by joelg236 on Monday April 18, 2016 @05:00PM (#11523124)
Be aware that python opencv uses c++ calls, it's only a wrapper. SciPy or numpy might be better examples.
Re:How fast can we make interpreted Python? (2013) by joshvm on Monday April 18, 2016 @05:43PM (#11523373)
I was under the impression that Numpy also just calls BLAS underneath? Hence why doing element-wise calls in Numpy is far, far faster than simply doing nested for loops.

But I think this is the great strength of Python. It's a glue language. If you need speed, you can always write a wrapper around a C/C++ library.

Re:How fast can we make interpreted Python? (2013) by dietrichepp on Tuesday April 19, 2016 @12:57AM (#11524978)
Funny you should say C/C++, because BLAS is Fortran.
Re:How fast can we make interpreted Python? (2013) by howeman on Tuesday April 19, 2016 @10:19AM (#11527112)
Actually, it's mostly assembly (depending on the particular implementation). Lapack is Fortran though.
Re:How fast can we make interpreted Python? (2013) by ihnorton on Monday April 18, 2016 @05:03PM (#11523142)
> SciPy or numpy might be better examples.

Python comprises less than 50% of the code in both of those repositories, but they are certainly great for learning the CPython API.