Re: SciPy 1.0 released!
The DNA of this work goes much further back. After some discussion as mentioned, Jim Hugunin wrote a numerical extension (called Numerical) and after a bit I took over as its coordinator with financial support for my work from Lawrence Livermore National Laboratory. They also supported the Foundation. I do not remember the exact timing but certainly Numerical was running before the 4th International was held at the Lab in the early 90s. Guido put in the complex type and other things to help us. We had endless discussion amongst us as how to spell it: 1i or 1j! One should note that the Lab was breaking new ground in supporting an open source project. SciPy was born to try to improve and extend a product that was already crucial to a lot of people. Indeed, it is a big part of several ongoing projects. Even non-numerical applications are important there. I retired in 2005, and everyone who writes software knows that what they do is ephemeral, but I don’t want history to be lost so soon. Paul Dubois ... moving as we speak to La Mesa, CA On Wed, Oct 25, 2017 at 5:05 AM Ralf Gommers wrote: > Hi all, > > We are extremely pleased to announce the release of SciPy 1.0, 16 years > after > version 0.1 saw the light of day. It has been a long, productive journey > to > get here, and we anticipate many more exciting new features and releases in > the > future. > > > Why 1.0 now? > > > A version number should reflect the maturity of a project - and SciPy was a > mature and stable library that is heavily used in production settings for a > long time already. From that perspective, the 1.0 version number is long > overdue. > > Some key project goals, both technical (e.g. Windows wheels and continuous > integration) and organisational (a governance structure, code of conduct > and a > roadmap), have been achieved recently. > > Many of us are a bit perfectionist, and therefore are reluctant to call > something "1.0" because it may imply that it's "finished" or "we are 100% > happy > with it". This is normal for many open source projects, however that > doesn't > make it right. We acknowledge to ourselves that it's not perfect, and > there > are some dusty corners left (that will probably always be the case). > Despite > that, SciPy is extremely useful to its users, on average has high quality > code > and documentation, and gives the stability and backwards compatibility > guarantees that a 1.0 label imply. > > > Some history and perspectives > - > > - 2001: the first SciPy release > - 2005: transition to NumPy > - 2007: creation of scikits > - 2008: scipy.spatial module and first Cython code added > - 2010: moving to a 6-monthly release cycle > - 2011: SciPy development moves to GitHub > - 2011: Python 3 support > - 2012: adding a sparse graph module and unified optimization interface > - 2012: removal of scipy.maxentropy > - 2013: continuous integration with TravisCI > - 2015: adding Cython interface for BLAS/LAPACK and a benchmark suite > - 2017: adding a unified C API with scipy.LowLevelCallable; removal of > scipy.weave > - 2017: SciPy 1.0 release > > > **Pauli Virtanen** is SciPy's Benevolent Dictator For Life (BDFL). He > says: > > *Truthfully speaking, we could have released a SciPy 1.0 a long time ago, > so I'm > happy we do it now at long last. The project has a long history, and during > the > years it has matured also as a software project. I believe it has well > proved > its merit to warrant a version number starting with unity.* > > *Since its conception 15+ years ago, SciPy has largely been written by and > for > scientists, to provide a box of basic tools that they need. Over time, the > set > of people active in its development has undergone some rotation, and we > have > evolved towards a somewhat more systematic approach to development. > Regardless, > this underlying drive has stayed the same, and I think it will also > continue > propelling the project forward in future. This is all good, since not long > after 1.0 comes 1.1.* > > **Travis Oliphant** is one of SciPy's creators. He says: > > *I'm honored to write a note of congratulations to the SciPy developers and > the > entire SciPy community for the release of SciPy 1.0. This release > represents > a dream of many that has been patiently pursued by a stalwart group of > pioneers > for nearly 2 decades. Efforts have been broad and consistent over that > time > from many hundreds of people. From initial discussions to efforts coding > and > packaging to documentation efforts to extensive conference and community > building, the SciPy e
Re: Elementwise -//- first release -//- Element-wise (vectorized) function, method and operator support for iterables in python.
You're reinventing Numeric Python. On Tue, Dec 20, 2011 at 11:45 AM, Nathan Rice < nathan.alexander.r...@gmail.com> wrote: > Elementwise provides a proxy object for iterables which supports > chained method calls, as well as elementwise expressions and some > built-in functions. > > Example: > >class ExampleList(ElementwiseProxyMixin, list): >def __new__(cls, iterable): >return list.__new__(cls, iterable) >foo = ExampleList([1, 2, 3, 4]) > ># You could also do: efoo = ElementwiseProxy(foo) >efoo = foo.each > >assert list(efoo.bit_length()) == [1, 2, 2, 3] >print "bit length: ", list(efoo.bit_length()) >assert list(efoo + 1) == [2, 3, 4, 5] >print "with addition of 1: ", list(efoo + 1) >assert list(efoo * 2) == [2, 4, 6, 8] >print "with multiplication by 2: ", list(efoo * 2) >assert list(efoo == 2) == [False, True, False, False] >print "testing equality: ", efoo == 2 >assert list((efoo + 1) * 2 + 3) == [7, 9, 11, 13] >print "chaining addition and multiplication: ", (efoo + 1) * 2 + 3 > > Each ElementwiseProxy also has a "parent" attribute so you can > backtrack in the chain as needed rather than store each intermediate > value, if you think you might need them. > > There are still some issues with proper support of things like bool() > and int(), which refuse to return things that are not of the correct > type. > > Get it: > >PyPi: http://pypi.python.org/pypi/elementwise/0.111220 >GitHub: https://github.com/nathan-rice/Elementwise > > This was developed as a proof of concept for expanding the role of > element-wise syntax in python, and to that end I welcome comments. > > Nathan Rice > -- > http://mail.python.org/mailman/listinfo/python-announce-list > >Support the Python Software Foundation: >http://www.python.org/psf/donations/ > -- http://mail.python.org/mailman/listinfo/python-list
