Numerical Python 20.1 compiles and passes all its tests with 2.2a1. It is about 10% slower than 2.1 both with and without optimization in exe= cuting the test suite. That test suite uses PyUnit and most of the operations in= volve small arrays so I suspect most of its time is in Python not the C code fo= r Numeric.=20
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4