On Wed, Feb 8, 2012 at 10:12 PM, julien tayon
What really should be discussed is inclusion of NumPy in the standard library (that is NumPy, not SciPy).
+1 for the inclusion of numpy in stdlib :)
There's more to stdlib inclusion than "hey, wouldn't it be nice if <X> was part of the stdlib?". It needs to make sense to do so, usually by providing a tangible benefit to the overall Python ecosystem. For smaller projects (especially predominantly single person projects), stdlib adoption comes with a guarantee of some level of long term support (in particular, making sure the module continues to work with newer versions of Python and on newer operating system releases). That isn't really the case with NumPy - it has a sizable developer base of its own, along with solid backing from Enthought. Incorporation into the standard library would be a *lot* of pain for minimal gain. If it helps, just consider SciPy Python's "stdlib++" if you're doing any kind of heavy number crunching with Python. There's a reason the PyPy folks were able to raise money to sponsor their NumPyPy compatibility effort - it's because the SciPy ecosystem is centred around NumPy, and NumPyPy promises to let developers enjoy the benefit's of PyPy without losing access to SciPy. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia