Hello,
We are proud to announce v0.15.0 of pandas, a major release from 0.14.1.
This release includes a small number of API changes, several new features,
enhancements, and performance improvements along with a large number of bug
fixes.
This was 4 months of work with 420 commits by 79 authors e
On Sun, Oct 19, 2014 at 6:43 AM, Nathaniel Smith wrote:
> I feel strongly that we should come up with a syntax that is
>
unambiguous even *without* looking at the gufunc signature. It's easy
> for the computer to disambiguate stuff like this, but it'd be cruel to
> ask people trying to skim throu
On Sun, Oct 19, 2014 at 8:13 AM, Nathaniel Smith wrote:
> On Sun, Oct 19, 2014 at 3:37 AM, Charles R Harris
> wrote:
> >
> > On Sat, Oct 18, 2014 at 7:17 PM, Nathaniel Smith wrote:
> >>
> >> So here are my concerns:
> >>
> >> - We decided to revert the changes to np.gradient in 1.9.1 (at least
On Sun, Oct 19, 2014 at 3:37 AM, Charles R Harris
wrote:
>
> On Sat, Oct 18, 2014 at 7:17 PM, Nathaniel Smith wrote:
>>
>> So here are my concerns:
>>
>> - We decided to revert the changes to np.gradient in 1.9.1 (at least
>> by default). I'm not sure how much of that decision was based on the
>>
On Sun, Oct 19, 2014 at 8:25 AM, Stephan Hoyer wrote:
> On Sat, Oct 18, 2014 at 6:46 PM, Nathaniel Smith wrote:
>>
>> One thing we'll have to watch out for is that for reduction operations
>> (which are basically gufuncs with (n)->() signatures), we already
>> allow axis=(0,1) to mean "reshape ax
On Sat, Oct 18, 2014 at 6:46 PM, Nathaniel Smith wrote:
> One thing we'll have to watch out for is that for reduction operations
> (which are basically gufuncs with (n)->() signatures), we already
> allow axis=(0,1) to mean "reshape axes 0 and 1 together into one big
> axis, and then use that as
