Re: [Numpy-discussion] SciPy 1.0 released!

[Dillon Niederhut]

Woohoo!

On Wed, Oct 25, 2017, 12:10 Charles R Harris 
wrote:

> On Wed, Oct 25, 2017 at 4:14 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 effort has been a global phenomenon that it has been a
>> privilege to participate in.*
>>
>> *The idea of SciPy was already in multiple people’s minds in 1997 when I
>> first
>> joined the Python community as a young graduate student who had just
>> fallen in
>> love with the expressibility and extensibility of Python.   The internet
>> was
>> just starting to bringing together like-minded mathematicians and
>> scientists in
>> nascent electronically-connected communities.   In 1998, there was a
>> concerted
>> discussion on the matrix-SIG, python mailing list with people like Paul
>> Barrett, Joe Harrington, Perry Greenfield, Paul Dubois, Konrad Hinsen,
>> David
>> Ascher, and others.   This discussion encouraged me in 1998 and 1999 to
>> procrastinate my PhD and spend a lot of time writing extension modules to
>> Python that mostly wrapped battle-tested Fortran and C-code making it
>> available
>> to the Python user.   This work attracted the help of others like Robert
>> Kern,
>> Pearu Peterson and Eric Jones who joined their efforts with mine in 2000
>> so
>> that by 2001, the first SciPy release was ready.   This was long before
>> Github
>> simplified collaboration and 

Re: [Numpy-discussion] SciPy 1.0 released!

[Charles R Harris]

On Wed, Oct 25, 2017 at 4:14 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 effort has been a global phenomenon that it has been a
> privilege to participate in.*
>
> *The idea of SciPy was already in multiple people’s minds in 1997 when I
> first
> joined the Python community as a young graduate student who had just
> fallen in
> love with the expressibility and extensibility of Python.   The internet
> was
> just starting to bringing together like-minded mathematicians and
> scientists in
> nascent electronically-connected communities.   In 1998, there was a
> concerted
> discussion on the matrix-SIG, python mailing list with people like Paul
> Barrett, Joe Harrington, Perry Greenfield, Paul Dubois, Konrad Hinsen,
> David
> Ascher, and others.   This discussion encouraged me in 1998 and 1999 to
> procrastinate my PhD and spend a lot of time writing extension modules to
> Python that mostly wrapped battle-tested Fortran and C-code making it
> available
> to the Python user.   This work attracted the help of others like Robert
> Kern,
> Pearu Peterson and Eric Jones who joined their efforts with mine in 2000 so
> that by 2001, the first SciPy release was ready.   This was long before
> Github
> simplified collaboration and input from others and the "patch" command and
> email was how you helped a project improve.*
>
> *Since that time, hundreds of people have spent an enormous amount of time
> improving the SciPy library and the community 

Re: [Numpy-discussion] SciPy 1.0 released!

[Ian Henriksen]

Many thanks to Ralf for managing this release! Thanks to the many
contributors too! This is a major milestone.

Best,

Ian Henriksen

On Wed, Oct 25, 2017 at 5:48 AM Francesc Alted  wrote:

> ​Congrats everybody!​
>
>
> 2017-10-25 12:14 GMT+02:00 Ralf Gommers :
>
>> 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 effort has been a global phenomenon that it has been a
>> privilege to participate in.*
>>
>> *The idea of SciPy was already in multiple people’s minds in 1997 when I
>> first
>> joined the Python community as a young graduate student who had just
>> fallen in
>> love with the expressibility and extensibility of Python.   The internet
>> was
>> just starting to bringing together like-minded mathematicians and
>> scientists in
>> nascent electronically-connected communities.   In 1998, there was a
>> concerted
>> discussion on the matrix-SIG, python mailing list with people like Paul
>> Barrett, Joe Harrington, Perry Greenfield, Paul Dubois, Konrad Hinsen,
>> David
>> Ascher, and others.   This discussion encouraged me in 1998 and 1999 to
>> procrastinate my PhD and spend a lot of time writing extension modules to
>> Python that mostly wrapped battle-tested Fortran and C-code making it
>> available
>> to the Python user.   This work attracted the help of others like Robert
>> Kern,
>> Pearu Peterson and Eric Jones who joined their efforts with mine 

Re: [Numpy-discussion] SciPy 1.0 released!

[Francesc Alted]

​Congrats everybody!​


2017-10-25 12:14 GMT+02:00 Ralf Gommers :

> 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 effort has been a global phenomenon that it has been a
> privilege to participate in.*
>
> *The idea of SciPy was already in multiple people’s minds in 1997 when I
> first
> joined the Python community as a young graduate student who had just
> fallen in
> love with the expressibility and extensibility of Python.   The internet
> was
> just starting to bringing together like-minded mathematicians and
> scientists in
> nascent electronically-connected communities.   In 1998, there was a
> concerted
> discussion on the matrix-SIG, python mailing list with people like Paul
> Barrett, Joe Harrington, Perry Greenfield, Paul Dubois, Konrad Hinsen,
> David
> Ascher, and others.   This discussion encouraged me in 1998 and 1999 to
> procrastinate my PhD and spend a lot of time writing extension modules to
> Python that mostly wrapped battle-tested Fortran and C-code making it
> available
> to the Python user.   This work attracted the help of others like Robert
> Kern,
> Pearu Peterson and Eric Jones who joined their efforts with mine in 2000 so
> that by 2001, the first SciPy release was ready.   This was long before
> Github
> simplified collaboration and input from others and the "patch" command and
> email was how you helped a project improve.*
>
> *Since that time, hundreds of people have spent an enormous amount of time
> improving the SciPy library and the 

[Numpy-discussion] SciPy 1.0 released!

[Ralf Gommers]

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 effort has been a global phenomenon that it has been a
privilege to participate in.*

*The idea of SciPy was already in multiple people’s minds in 1997 when I
first
joined the Python community as a young graduate student who had just fallen
in
love with the expressibility and extensibility of Python.   The internet was
just starting to bringing together like-minded mathematicians and
scientists in
nascent electronically-connected communities.   In 1998, there was a
concerted
discussion on the matrix-SIG, python mailing list with people like Paul
Barrett, Joe Harrington, Perry Greenfield, Paul Dubois, Konrad Hinsen, David
Ascher, and others.   This discussion encouraged me in 1998 and 1999 to
procrastinate my PhD and spend a lot of time writing extension modules to
Python that mostly wrapped battle-tested Fortran and C-code making it
available
to the Python user.   This work attracted the help of others like Robert
Kern,
Pearu Peterson and Eric Jones who joined their efforts with mine in 2000 so
that by 2001, the first SciPy release was ready.   This was long before
Github
simplified collaboration and input from others and the "patch" command and
email was how you helped a project improve.*

*Since that time, hundreds of people have spent an enormous amount of time
improving the SciPy library and the community surrounding this library has
dramatically grown. I stopped being able to participate actively in
developing
the SciPy library around 2010.  Fortunately, at that time, Pauli Virtanen
and
Ralf Gommers picked up the pace of development supported by dozens of other
key
contributors such as David Cournapeau, Evgeni