Re: [Numpy-discussion] fromnumeric.py internal calls

2016-02-28 Thread Stephan Hoyer
I think this is an improvement, but I do wonder if there are libraries out
there that use *args instead of **kwargs to handle these extra arguments.
Perhaps it's worth testing this change against third party array libraries
that implement their own array like classes? Off the top of my head, maybe
scipy, pandas, dask, astropy, pint, xarray?
On Wed, Feb 24, 2016 at 3:40 AM G Young  wrote:

> Hello all,
>
> I have PR #7325  up that
> changes the internal calls for functions in *fromnumeric.py* from
> positional arguments to keyword arguments.  I made this change for two
> reasons:
>
> 1) It is consistent with the external function signature
> 2)
>
> The inconsistency caused a breakage in *pandas* in its own implementation
> of *searchsorted* in which the *sorter* argument is not really used but
> is accepted so as to make it easier for *numpy* users who may be used to
> the *searchsorted* signature in *numpy*.
>
> The standard in *pandas* is to "swallow" those unused arguments into a
> *kwargs* argument so that we don't have to document an argument that we
> don't really use.  However, that turned out not to be possible when
> *searchsorted* is called from the *numpy* library.
>
> Does anyone have any objections to the changes I made?
>
> Thanks!
>
> Greg
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] ANN: pandas v0.18.0rc1 - RELEASE CANDIDATE

2016-02-28 Thread Jeff
So you are probably reading sas7bdat, which was put in AFTER 0.18.0rc1 was 
cut (if you are reading xport format then you are good to go), otherwise 
you may want to wait a bit for 0.18.0rc2.



On Sunday, February 28, 2016 at 1:42:53 PM UTC-5, John E wrote:
>
> OK, thanks, I got it.  Although... I would consider pandas.pydata.org to 
> be a common end user gateway and if one starts there they will read "We 
> recommend that *all *users upgrade to this version."  And then if they 
> scroll down a short distance they will see a single line instruction for 
> installing via conda: "conda install pandas=v0.18.0rc1 -c pandas". 
>
> And also somewhat confusing to me about pandas.pydata.org is that looking 
> to the right, you have a choice of RC, dev, and previous releases, but 
> nothing that says something like "current, stable release".
>
> Anyways  quite possibly this is confusing only to me, and not others, 
> but I thought I'd mention it just in case.  FWIW.
>
> I've now installed 0.18.0rc1 and will try to test out some of the newer 
> features.  I'm really interested to see how well the SAS reader works (i.e. 
> how fast).  I hate SAS myself, but this would be a really, really nice 
> feature for my organization and likely increase adoption of python & pandas.
>
>
>
> On Sunday, February 28, 2016 at 12:03:45 PM UTC-5, Jeff wrote:
>>
>>
>> These are pre-releases. In other words, we would want the community to 
>> test out before an official release, and see if there are any show 
>> stoppers. The docs are setup for the official releases. These are not put 
>> into official channels at all (that is the point), e.g. not on PyPi, nor in 
>> the conda main channels. Only official releases will go there.
>>
>> Generally we will try to do release candidates before major changes, but 
>> not before minor changes.
>>
>> So the official release of 0.18.0 has not happened yet! (in fact going to 
>> do a v0.18.0rc2 next week).
>>
>> We would love for you to test out!
>>
>> Jeff
>>
>>
>>
>>
>> On Sunday, February 28, 2016 at 11:50:57 AM UTC-5, John E wrote:
>>>
>>> I hope this doesn't come across as a trivial, semantical question, but...
>>>
>>> The initial releases of the last 2  or so versions have been labelled as 
>>> "release candidates" but still say "We recommend that all
>>> users upgrade to this version."
>>>
>>> So this is a little confusing to me for using pandas in a production 
>>> environment.  "Release candidate" seems to suggest that you should wait for 
>>> 0.18.1, but the note unambiguously says not to wait.  So which 
>>> interpretation is recommended for a production environment?
>>>
>>>
>>> On Saturday, February 13, 2016 at 7:53:18 PM UTC-5, Jeff wrote:

 Hi,

 I'm pleased to announce the availability of the first release candidate 
 of Pandas 0.18.0.
 Please try this RC and report any issues here: Pandas Issues 
 
 We will be releasing officially in 1-2 weeks or so.

 **RELEASE CANDIDATE 1**

 This is a major release from 0.17.1 and includes a small number of API 
 changes, several new features,
 enhancements, and performance improvements along with a large number of 
 bug fixes. We recommend that all
 users upgrade to this version.

 Highlights include:

- pandas >= 0.18.0 will no longer support compatibility with Python 
version 2.6 GH7718  or 
version 3.3 GH11273 
- Moving and expanding window functions are now methods on Series 
and DataFrame similar to .groupby like objects, see here 

 
.
- Adding support for a RangeIndex as a specialized form of the 
Int64Index for memory savings, see here 

 
.
- API breaking .resample changes to make it more .groupby like, see 
here 

 
- Removal of support for positional indexing with floats, which was 
deprecated since 0.14.0. This will now raise a TypeError, see here 

 
- The .to_xarray() function has been added for compatibility with 
the xarray package  see here 

 
.
- Addition of the .str.extractall() method 

 ,
  

Re: [Numpy-discussion] Generalized flip function

2016-02-28 Thread Stephan Hoyer
I also think this is a good idea -- the generalized flip is much more
numpythonic than the specialized 2d versions.
On Fri, Feb 26, 2016 at 11:36 AM Joseph Fox-Rabinovitz <
jfoxrabinov...@gmail.com> wrote:

> If nothing else, this is a nice complement to the generalized `stack`
> function.
>
> -Joe
>
> On Fri, Feb 26, 2016 at 11:32 AM, Eren Sezener 
> wrote:
> > Hi,
> >
> > In PR #7346 we add a flip function that generalizes fliplr and flipud for
> > arbitrary axes.
> >
> > flipud and fliplr reverse the elements of an array along axis=0 and
> axis=1
> > respectively. The new flip function reverses the elements of an array
> along
> > any given axis. In case flip is called with axis=0 or axis=1, the
> function
> > is equivalent to flipud and fliplr respectively.
> >
> > A similar function is also available in MATLABâ„¢.
> >
> > We use this function in PR #7347 to generalize the rot90 function to
> rotate
> > an arbitrary plane (defined by the axes argument) of a multidimensional
> > array. By that we fix issue #6506.
> >
> > Because flip function introduces a new API, @shoyer asked us to consult
> the
> > mailing list.
> >
> > Any objection to adding the generalized flip function?
> >
> > Best regards,
> > C. Eren Sezener & Denis Alevi
> >
> > ___
> > NumPy-Discussion mailing list
> > NumPy-Discussion@scipy.org
> > https://mail.scipy.org/mailman/listinfo/numpy-discussion
> >
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] ANN: pandas v0.18.0rc1 - RELEASE CANDIDATE

2016-02-28 Thread Jeff

These are pre-releases. In other words, we would want the community to test 
out before an official release, and see if there are any show stoppers. The 
docs are setup for the official releases. These are not put into official 
channels at all (that is the point), e.g. not on PyPi, nor in the conda 
main channels. Only official releases will go there.

Generally we will try to do release candidates before major changes, but 
not before minor changes.

So the official release of 0.18.0 has not happened yet! (in fact going to 
do a v0.18.0rc2 next week).

We would love for you to test out!

Jeff




On Sunday, February 28, 2016 at 11:50:57 AM UTC-5, John E wrote:
>
> I hope this doesn't come across as a trivial, semantical question, but...
>
> The initial releases of the last 2  or so versions have been labelled as 
> "release candidates" but still say "We recommend that all
> users upgrade to this version."
>
> So this is a little confusing to me for using pandas in a production 
> environment.  "Release candidate" seems to suggest that you should wait for 
> 0.18.1, but the note unambiguously says not to wait.  So which 
> interpretation is recommended for a production environment?
>
>
> On Saturday, February 13, 2016 at 7:53:18 PM UTC-5, Jeff wrote:
>>
>> Hi,
>>
>> I'm pleased to announce the availability of the first release candidate 
>> of Pandas 0.18.0.
>> Please try this RC and report any issues here: Pandas Issues 
>> 
>> We will be releasing officially in 1-2 weeks or so.
>>
>> **RELEASE CANDIDATE 1**
>>
>> This is a major release from 0.17.1 and includes a small number of API 
>> changes, several new features,
>> enhancements, and performance improvements along with a large number of 
>> bug fixes. We recommend that all
>> users upgrade to this version.
>>
>> Highlights include:
>>
>>- pandas >= 0.18.0 will no longer support compatibility with Python 
>>version 2.6 GH7718  or 
>>version 3.3 GH11273 
>>- Moving and expanding window functions are now methods on Series and 
>>DataFrame similar to .groupby like objects, see here 
>>
>> 
>>.
>>- Adding support for a RangeIndex as a specialized form of the 
>>Int64Index for memory savings, see here 
>>
>> 
>>.
>>- API breaking .resample changes to make it more .groupby like, see 
>>here 
>>
>> 
>>- Removal of support for positional indexing with floats, which was 
>>deprecated since 0.14.0. This will now raise a TypeError, see here 
>>
>> 
>>- The .to_xarray() function has been added for compatibility with the 
>> xarray 
>>package  see here 
>>
>> 
>>.
>>- Addition of the .str.extractall() method 
>>
>> ,
>>  
>>and API changes to the the .str.extract() method 
>>
>> ,
>>  
>>and the .str.cat() method 
>>
>> 
>>- pd.test() top-level nose test runner is available GH4327 
>>
>>
>> See the Whatsnew 
>>  for much 
>> more information. 
>>
>> Best way to get this is to install via conda 
>> 
>>  from 
>> our development channel. Builds for osx-64,linux-64,win-64 for Python 2.7 
>> and Python 3.5 are all available.
>>
>> conda install pandas=v0.18.0rc1 -c pandas
>>
>> Thanks to all who made this release happen. It is a very large release!
>>
>> Jeff
>>
>>___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion