From ericq at caltech.edu  Wed May  4 17:12:52 2016
From: ericq at caltech.edu (Eric Quintero)
Date: Wed, 4 May 2016 14:12:52 -0700
Subject: [SciPy-Dev] scipy.signal filtering API
Message-ID: <9630B223-6B7E-43FF-8AAE-27C5F8F47727@caltech.edu>

Hi All,

I would like to bring the following Github issue to your attention, where I would like to start a discussion on unifying the API of filter/LTI system design and analysis in scipy.signal:

https://github.com/scipy/scipy/issues/6137

I appreciate any and all feedback that users and developers may have!

Thanks for your time,
Eric Quintero

From evgeny.burovskiy at gmail.com  Thu May  5 03:12:01 2016
From: evgeny.burovskiy at gmail.com (Evgeni Burovski)
Date: Thu, 5 May 2016 08:12:01 +0100
Subject: [SciPy-Dev] scipy 0.17.1 release
In-Reply-To: <CAMRo0itRT_x_xDNv8k5UqbN-As3O3KSd2G1RjwomCsSAJOE6Ug@mail.gmail.com>
References: <CAMRo0iuiyyJQeDDCwQdW2tGFtPQ3nn17hajupQGEQ_q78f5oVA@mail.gmail.com>
 <CAMRo0itRT_x_xDNv8k5UqbN-As3O3KSd2G1RjwomCsSAJOE6Ug@mail.gmail.com>
Message-ID: <CAMRo0ivxDdsB6SNt2egWOj-FFYbEYrz6DOAPaUJoJtzvi73xog@mail.gmail.com>

On Tue, Apr 26, 2016 at 1:21 PM, Evgeni Burovski
<evgeny.burovskiy at gmail.com> wrote:
> On Sun, Apr 10, 2016 at 6:53 PM, Evgeni Burovski
> <evgeny.burovskiy at gmail.com> wrote:
>> Hi,
>>
>> I'm planning to cut the point release of scipy 0.17.1 by the end of this week.
>> Thoughts?
>>
>> Regressions in 0.17.0 so far seem reasonably mild:
>> https://github.com/scipy/scipy/milestones/0.17.1
>> If there's anything else you think should be included in 0.17.1,
>> please mention it in this email thread or on Github.
>
>
> Quite obviously, it did not happen by the end of the week before last :-).
>
> At the moment though, the remaining blocker is the backwards
> compatibility break in `stats.mannwhitneyu` where the default
> hypothesis differ in 0.16.1 and 0.17.0.
>
> The PR with the fix which restores the backwards compat is
> https://github.com/scipy/scipy/pull/6100
>
> My plan is to merge it and finalize 0.17.1 soon (tm). Please speak up
> if you have comments about this fix and/or would like more time to
> review it.


The mannwhitneyu fix has been merged, thanks to Tavi, and Josef and
Alex for the review.

In the meantime, there is one more small issue which I'd like to hold
0.17.1 for, https://github.com/scipy/scipy/issues/6134.
This seems fairly straightforward, so a pull request would help
spinning the wheels.

Cheers,

Evgeni


From davidgshi at yahoo.co.uk  Tue May 10 19:08:12 2016
From: davidgshi at yahoo.co.uk (David Shi)
Date: Tue, 10 May 2016 23:08:12 +0000 (UTC)
Subject: [SciPy-Dev] Looking for an example of using PchipInterpolator
References: <1309661986.69677.1462921692591.JavaMail.yahoo.ref@mail.yahoo.com>
Message-ID: <1309661986.69677.1462921692591.JavaMail.yahoo@mail.yahoo.com>

Hello, Friends,
I am looking for an example of using Scipy ?PchipInterpolator.
However, when I used?matplotlib to plot the data, the last section of the line is missing. ?Only data points are present.
Looking forward to hearing from you.
Regards.
David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20160510/990f13fc/attachment.html>

From warren.weckesser at gmail.com  Tue May 10 21:56:14 2016
From: warren.weckesser at gmail.com (Warren Weckesser)
Date: Tue, 10 May 2016 21:56:14 -0400
Subject: [SciPy-Dev] Looking for an example of using PchipInterpolator
In-Reply-To: <1309661986.69677.1462921692591.JavaMail.yahoo@mail.yahoo.com>
References: <1309661986.69677.1462921692591.JavaMail.yahoo.ref@mail.yahoo.com>
 <1309661986.69677.1462921692591.JavaMail.yahoo@mail.yahoo.com>
Message-ID: <CAGzF1ucFkX6ZgjJY+xq2V8ShUXRLSU=Rzzi+fNkqmLb1Z8oSow@mail.gmail.com>

On Tue, May 10, 2016 at 7:08 PM, David Shi <davidgshi at yahoo.co.uk> wrote:

> Hello, Friends,
>
> I am looking for an example of using Scipy  PchipInterpolator.
>


My answers to these questions on stackoverflow show examples of the use of
PchipInterpolator:

*
http://stackoverflow.com/questions/12935098/how-to-plot-line-polygonal-chain-with-numpy-scipy-matplotlib-with-minimal-smoo
*
http://stackoverflow.com/questions/20919038/interpolation-method-that-does-not-add-unnecessary-extremums

Warren



>
> However, when I used matplotlib to plot the data, the last section of the
> line is missing.  Only data points are present.
>
> Looking forward to hearing from you.
>
> Regards.
>
> David
>
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev at scipy.org
> https://mail.scipy.org/mailman/listinfo/scipy-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20160510/3378b411/attachment.html>

From charlesnwoods at gmail.com  Tue May 10 22:20:33 2016
From: charlesnwoods at gmail.com (Nathan Woods)
Date: Tue, 10 May 2016 20:20:33 -0600
Subject: [SciPy-Dev] (no subject)
Message-ID: <CAAYHtCT+rtVGQ=ATYsKdWbO3Sn2ktgJ6OM6JEn87FB_5Z+cJ_g@mail.gmail.com>

There have been a number of problems (e.g. GitHub issues #5002, #4831) with
the C interface of scipy.integrate.quad since work was done a couple of
years ago to allow performance optimizations (
https://github.com/scipy/scipy/commit/f5183a34a959d625c6b534e99df5db7ca49bf1ec).
Specifically, the QuadPack Fortran library does not really accommodate
multivariate integrand functions, which leads to all sorts of monkey
business in the API to hide that multivariate-ness. This is further
complicated by the fact that the QuadPack interface is one of the oldest
parts of SciPy and uses the Python C API directly, which many (most?) of us
are unfamiliar with.

I'd really like to figure out some kind of "good" solution to this. I think
that the requirements of the problem are fairly simple: connect the
existing scipy.integrate.quad routine to the underlying Fortran code, while
allowing users to use compiled function pointers as integrand functions, if
they want to (and are willing to put in some effort).

I guess that the question here is, what is the best way to go about this?
Should we simply find a way to fix the existing interface code? Should we
roll back the changes and disallow the use of function pointers in quad?
Should we replace the existing API with something else, using Cython or
f2py? Should we alter the QuadPack code itself (perhaps by adding a void*
argument to the function) to make it more friendly to multivariate
functions in general?

The current state of affairs bothers me, especially since I was involved in
the PR that  caused the new problems, but I haven't been able to come up
with a good way to fix things yet. I'd love to get some ideas and feedback
on how this could be resolved.

Nathan Woods
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20160510/d92e8f9e/attachment.html>

From cimrman3 at ntc.zcu.cz  Thu May 12 03:51:35 2016
From: cimrman3 at ntc.zcu.cz (Robert Cimrman)
Date: Thu, 12 May 2016 09:51:35 +0200
Subject: [SciPy-Dev] ANN: SfePy 2016.2
Message-ID: <57343607.2020100@ntc.zcu.cz>

I am pleased to announce release 2016.2 of SfePy.

Description
-----------

SfePy (simple finite elements in Python) is a software for solving systems of
coupled partial differential equations by the finite element method or by the
isogeometric analysis (preliminary support). It is distributed under the new
BSD license.

Home page: http://sfepy.org
Mailing list: http://groups.google.com/group/sfepy-devel
Git (source) repository, issue tracker, wiki: http://github.com/sfepy

Highlights of this release
--------------------------

- partial shell10x element implementation
- parallel computation of homogenized coefficients
- clean up of elastic terms
- read support for msh file mesh format of gmsh

For full release notes see http://docs.sfepy.org/doc/release_notes.html#id1
(rather long and technical).

Best regards,
Robert Cimrman on behalf of the SfePy development team

---

Contributors to this release in alphabetical order:

Robert Cimrman
Vladimir Lukes


From evgeny.burovskiy at gmail.com  Thu May 12 09:02:03 2016
From: evgeny.burovskiy at gmail.com (Evgeni Burovski)
Date: Thu, 12 May 2016 14:02:03 +0100
Subject: [SciPy-Dev] scipy 0.17.1 release
Message-ID: <CAMRo0ivDDsDeSdSo91LDk4_Wo3aXRi+yrKpvHe1pnYYRkm8dzQ@mail.gmail.com>

Hi,

On behalf of the scipy development team, I'm pleased to announce the
availability of scipy 0.17.1.

This is a bugfix release with no new features compared to 0.17.0.

Source tarballs and OS X wheels are available from PyPI or from GitHub
releases at https://github.com/scipy/scipy/releases/tag/v0.17.1

We recommend that all users upgrade from scipy 0.17.0.

Cheers,

Evgeni



==========================
SciPy 0.17.1 Release Notes
==========================

SciPy 0.17.1 is a bug-fix release with no new features compared to 0.17.0.


Issues closed for 0.17.1
------------------------

- `#5817 <https://github.com/scipy/scipy/issues/5817>`__: BUG: skew,
kurtosis return np.nan instead of "propagate"
- `#5850 <https://github.com/scipy/scipy/issues/5850>`__: Test failed
with sgelsy
- `#5898 <https://github.com/scipy/scipy/issues/5898>`__:
interpolate.interp1d crashes using float128
- `#5953 <https://github.com/scipy/scipy/issues/5953>`__: Massive
performance regression in cKDTree.query with L_inf distance...
- `#6062 <https://github.com/scipy/scipy/issues/6062>`__: mannwhitneyu
breaks backward compatibility in 0.17.0
- `#6134 <https://github.com/scipy/scipy/issues/6134>`__: T test does
not handle nans


Pull requests for 0.17.1
------------------------

- `#5902 <https://github.com/scipy/scipy/pull/5902>`__: BUG:
interpolate: make interp1d handle np.float128 again
- `#5957 <https://github.com/scipy/scipy/pull/5957>`__: BUG: slow down
with p=np.inf in 0.17 cKDTree.query
- `#5970 <https://github.com/scipy/scipy/pull/5970>`__: Actually
propagate nans through stats functions with nan_policy="propagate"
- `#5971 <https://github.com/scipy/scipy/pull/5971>`__: BUG: linalg:
fix lwork check in *gelsy
- `#6074 <https://github.com/scipy/scipy/pull/6074>`__: BUG: special:
fixed violation of strict aliasing rules.
- `#6083 <https://github.com/scipy/scipy/pull/6083>`__: BUG: Fix dtype
for sum of linear operators
- `#6100 <https://github.com/scipy/scipy/pull/6100>`__: BUG: Fix
mannwhitneyu to be backward compatible
- `#6135 <https://github.com/scipy/scipy/pull/6135>`__: Don't pass
null pointers to LAPACK, even during workspace queries.
- `#6148 <https://github.com/scipy/scipy/pull/6148>`__: stats: fix
handling of nan values in T tests and kendalltau


From ralf.gommers at gmail.com  Sat May 14 11:30:41 2016
From: ralf.gommers at gmail.com (Ralf Gommers)
Date: Sat, 14 May 2016 17:30:41 +0200
Subject: [SciPy-Dev] scipy 0.17.1 release
In-Reply-To: <CAMRo0ivDDsDeSdSo91LDk4_Wo3aXRi+yrKpvHe1pnYYRkm8dzQ@mail.gmail.com>
References: <CAMRo0ivDDsDeSdSo91LDk4_Wo3aXRi+yrKpvHe1pnYYRkm8dzQ@mail.gmail.com>
Message-ID: <CABL7CQhZ85MsmkPAEYFCVtQ=PosXVozmo=LR8+JsHiWb+ZYQ9g@mail.gmail.com>

On Thu, May 12, 2016 at 3:02 PM, Evgeni Burovski <evgeny.burovskiy at gmail.com
> wrote:

> Hi,
>
> On behalf of the scipy development team, I'm pleased to announce the
> availability of scipy 0.17.1.
>
> This is a bugfix release with no new features compared to 0.17.0.
>
> Source tarballs and OS X wheels are available from PyPI or from GitHub
> releases at https://github.com/scipy/scipy/releases/tag/v0.17.1
>
> We recommend that all users upgrade from scipy 0.17.0.
>
> Cheers,
> Evgeni
>
>
Thanks Evgeni for getting this one out the door! And apologies for not
lending a hand - I was distracted by real life / day job, but will be
getting back to Scipy development this weekend.

Cheers,
Ralf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20160514/ba3d94e4/attachment.html>

From charlesr.harris at gmail.com  Wed May 18 17:09:36 2016
From: charlesr.harris at gmail.com (Charles R Harris)
Date: Wed, 18 May 2016 15:09:36 -0600
Subject: [SciPy-Dev] Scipy 2016 attending
Message-ID: <CAB6mnxKhTBVHPZzx_Rf_hTQnt-hD6-xQ2iBDEbEpJANd0+3qrg@mail.gmail.com>

Hi All,

Out of curiosity, who all here intends to be at Scipy 2016?

Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20160518/b0c4b07d/attachment.html>

From njs at pobox.com  Wed May 18 18:03:31 2016
From: njs at pobox.com (Nathaniel Smith)
Date: Wed, 18 May 2016 15:03:31 -0700
Subject: [SciPy-Dev] [Numpy-discussion] Scipy 2016 attending
In-Reply-To: <CALGmxELyPiZ57RGLh8ucsVFXp7=8RtfOfsnoB4r_1q61aS3jiw@mail.gmail.com>
References: <CAB6mnxKhTBVHPZzx_Rf_hTQnt-hD6-xQ2iBDEbEpJANd0+3qrg@mail.gmail.com>
 <CALGmxELyPiZ57RGLh8ucsVFXp7=8RtfOfsnoB4r_1q61aS3jiw@mail.gmail.com>
Message-ID: <CAPJVwBmJM7CevJ8+O6Szwhn4bHJy_QuaxanBUDYTHvKsyQMZdw@mail.gmail.com>

Me too.

On Wed, May 18, 2016 at 3:02 PM, Chris Barker <chris.barker at noaa.gov> wrote:
> I'll be there.
>
> -CHB
>
>
> On Wed, May 18, 2016 at 2:09 PM, Charles R Harris
> <charlesr.harris at gmail.com> wrote:
>>
>> Hi All,
>>
>> Out of curiosity, who all here intends to be at Scipy 2016?
>>
>> Chuck
>>
>> _______________________________________________
>> NumPy-Discussion mailing list
>> NumPy-Discussion at scipy.org
>> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>>
>
>
>
> --
>
> Christopher Barker, Ph.D.
> Oceanographer
>
> Emergency Response Division
> NOAA/NOS/OR&R            (206) 526-6959   voice
> 7600 Sand Point Way NE   (206) 526-6329   fax
> Seattle, WA  98115       (206) 526-6317   main reception
>
> Chris.Barker at noaa.gov
>
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at scipy.org
> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>



-- 
Nathaniel J. Smith -- https://vorpus.org


From tyler.je.reddy at gmail.com  Thu May 19 08:56:31 2016
From: tyler.je.reddy at gmail.com (Tyler Reddy)
Date: Thu, 19 May 2016 13:56:31 +0100
Subject: [SciPy-Dev] [Numpy-discussion] Scipy 2016 attending
In-Reply-To: <CAPJVwBmJM7CevJ8+O6Szwhn4bHJy_QuaxanBUDYTHvKsyQMZdw@mail.gmail.com>
References: <CAB6mnxKhTBVHPZzx_Rf_hTQnt-hD6-xQ2iBDEbEpJANd0+3qrg@mail.gmail.com>
 <CALGmxELyPiZ57RGLh8ucsVFXp7=8RtfOfsnoB4r_1q61aS3jiw@mail.gmail.com>
 <CAPJVwBmJM7CevJ8+O6Szwhn4bHJy_QuaxanBUDYTHvKsyQMZdw@mail.gmail.com>
Message-ID: <CAHPuU_ZqmB=779D5pG3qBRYLTYMTr_UTfJYEacqq-DUGnx44+w@mail.gmail.com>

I'll be at PyCon instead this year.

On 18 May 2016 at 23:03, Nathaniel Smith <njs at pobox.com> wrote:

> Me too.
>
> On Wed, May 18, 2016 at 3:02 PM, Chris Barker <chris.barker at noaa.gov>
> wrote:
> > I'll be there.
> >
> > -CHB
> >
> >
> > On Wed, May 18, 2016 at 2:09 PM, Charles R Harris
> > <charlesr.harris at gmail.com> wrote:
> >>
> >> Hi All,
> >>
> >> Out of curiosity, who all here intends to be at Scipy 2016?
> >>
> >> Chuck
> >>
> >> _______________________________________________
> >> NumPy-Discussion mailing list
> >> NumPy-Discussion at scipy.org
> >> https://mail.scipy.org/mailman/listinfo/numpy-discussion
> >>
> >
> >
> >
> > --
> >
> > Christopher Barker, Ph.D.
> > Oceanographer
> >
> > Emergency Response Division
> > NOAA/NOS/OR&R            (206) 526-6959   voice
> > 7600 Sand Point Way NE   (206) 526-6329   fax
> > Seattle, WA  98115       (206) 526-6317   main reception
> >
> > Chris.Barker at noaa.gov
> >
> > _______________________________________________
> > NumPy-Discussion mailing list
> > NumPy-Discussion at scipy.org
> > https://mail.scipy.org/mailman/listinfo/numpy-discussion
> >
>
>
>
> --
> Nathaniel J. Smith -- https://vorpus.org
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev at scipy.org
> https://mail.scipy.org/mailman/listinfo/scipy-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20160519/6ffe3411/attachment.html>

From cgodshall at enthought.com  Thu May 19 14:09:12 2016
From: cgodshall at enthought.com (Courtenay Godshall (Enthought))
Date: Thu, 19 May 2016 13:09:12 -0500
Subject: [SciPy-Dev] SciPy 2016 Conference (Scientific Computing with
	Python): Tutorials and Talks Announced
In-Reply-To: <011c01d1b1f9$7b622e20$72268a60$@enthought.com>
References: <010c01d1b1f9$58adc010$0a094030$@enthought.com>
 <011401d1b1f9$6a748810$3f5d9830$@enthought.com>
 <011c01d1b1f9$7b622e20$72268a60$@enthought.com>
Message-ID: <012401d1b1f9$8c646da0$a52d48e0$@enthought.com>

**ANN: SciPy 2016 Conference (Scientific Computing with Python): Tutorials
and Talks Announced**

 

We're excited to announce this year's accepted Talks
<http://scipy2016.scipy.org/ehome/146062/332963/> & Posters and Tutorial
Schedule <http://scipy2016.scipy.org/ehome/146062/332960/> !  This year's 3
major talk tracks include Python in Data Science, High Performance
Computing, and general Scientific Computing. Our six mini-symposia include:
Earth and Space Science, Engineering, Medicine and Biology, Case Studies in
Industry, Education, and Reproducibility. For tutorials, you can choose from
<http://scipy2016.scipy.org/ehome/146062/332960/>  18 different SciPy
tutorials, including a  <https://katyhuff.github.io/2016-07-11-scipy> 1 day
Software Carpentry Scientific Python course that assumes some programming
experience but no Python knowledge, or a 2-day Software Carpentry Instructor
Training.

 

We hope you'll join us - early bird registration ENDS May 22, 2016. Register
at: http://scipy2016.scipy.org/ehome/146062/332936/

 

About SciPy 2016

SciPy 2016 <http://www.scipy2016.scipy.org> , the 15th annual Scientific
Computing with Python conference, will be held July 11-17, 2016 in Austin,
Texas. SciPy is a community dedicated to the advancement of scientific
computing through open source Python software for mathematics, science, and
engineering. The annual SciPy Conference brings together over 650
participants from industry, academia, and government to showcase their
latest projects, learn from skilled users and developers, and collaborate on
code development. The full program will consist of
<http://scipy2016.scipy.org/ehome/146062/332960/>  2 days of tutorials (July
11-12), <http://scipy2016.scipy.org/ehome/146062/332963/>  3 days of talks
(July 13-15), and 2days of
<http://scipy2016.scipy.org/ehome/146062/332969/?&&>  developer sprints
(July 16-17). More info is available on the conference website at
<http://www.scipy2016.scipy.org>  http://scipy2016.scipy.org (where you can
sign up for the mailing list); or follow <https://twitter.com/scipyconf>
@scipyconf on Twitter.  

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20160519/0e1f473b/attachment.html>

From nikolay.mayorov at zoho.com  Sun May 22 03:14:17 2016
From: nikolay.mayorov at zoho.com (Nikolay Mayorov)
Date: Sun, 22 May 2016 12:14:17 +0500
Subject: [SciPy-Dev] Boundary conditions for CubicSpline
Message-ID: <154d7507f20.b7eee50311717.762598624587853833@zoho.com>

Hi! 



There is some discussion going on about how to implement periodic boundary conditions for CubicSpline class, which to appear in 0.18.0 scipy release: https://github.com/scipy/scipy/pull/6181



If it's of interest to you, please take a look and comment. Any other feedback is also welcome.





Nikolay.



Sent using Zoho Mail





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20160522/7845f82c/attachment.html>

From charlesr.harris at gmail.com  Thu May 26 22:42:02 2016
From: charlesr.harris at gmail.com (Charles R Harris)
Date: Thu, 26 May 2016 20:42:02 -0600
Subject: [SciPy-Dev] Numpy 1.11.1rc1 release
Message-ID: <CAB6mnxLjtKjP4suuSJfZ8=0eXvbvOTFDh8XjbBRqw6wmO1XOAg@mail.gmail.com>

Hi All,

I am pleased to announce the release of Numpy 1.11.1rc1. The sources may be
found on sourceforge
<https://sourceforge.net/projects/numpy/files/NumPy/1.11.1rc1/> and wheels
for OS X, Windows, and Linux will be available on pypi sometime in the next
few days. The pypi release is delayed due to the decision that the wheels
should go up before the sources in order that people not get a source
install when what they want are wheels. The Python versions supported are
2.6-2.7 and 3.2-3.5.

This release has mostly small fixes and build enhancements and should be
good out of the starting gate, but prudence requires a release candidate as
there are a few bits not tested in master. The following fixes have been
applied:

   - #7506 BUG: Make sure numpy imports on python 2.6 when nose is
   unavailable.
   - #7530 BUG: Floating exception with invalid axis in np.lexsort.
   - #7535 BUG: Extend glibc complex trig functions blacklist to glibc <
   2.18.
   - #7551 BUG: Allow graceful recovery for no compiler.
   - #7558 BUG: Constant padding expected wrong type in constant_values.
   - #7578 BUG: Fix OverflowError in Python 3.x. in swig interface.
   - #7590 BLD: Fix configparser.InterpolationSyntaxError.
   - #7597 BUG: Make np.ma.take work on scalars.
   - #7608 BUG: linalg.norm(): Don't convert object arrays to float.
   - #7638 BLD: Correct C compiler customization in system_info.py.
   - #7654 BUG: ma.median of 1d array should return a scalar.
   - #7656 BLD: Remove hardcoded Intel compiler flag -xSSE4.2.
   - #7660 BUG: Temporary fix for str(mvoid) for object field types.
   - #7665 BUG: Fix incorrect printing of 1D masked arrays.
   - #7670 BUG: Correct initial index estimate in histogram.
   - #7671 BUG: Boolean assignment no GIL release when transfer needs API.
   - #7676 BUG: Fix handling of right edge of final histogram bin.
   - #7680 BUG: Fix np.clip bug NaN handling for Visual Studio 2015.


The following people have contributed to this release


   - Allan Haldane
   - Amit Aronovitch
   - Charles Harris
   - Eric Wieser
   - Evgeni Burovski
   - Lo?c Est?ve
   - Mathieu Lamarre
   - Matthew Brett
   - Matthias Geier
   - Nathaniel J. Smith
   - Nikola Forr?
   - Ralf Gommers
   - Robert Kern
   - Sebastian Berg
   - Simon Conseil
   - Simon Gibbons
   - Sorin Sbarnea
   - chiffa

Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20160526/9a57ee01/attachment.html>