On Wed, May 29, 2013 at 12:25 PM, Julian Taylor
wrote:
> On 05/29/2013 06:12 AM, josef.p...@gmail.com wrote:
>>
>> On Tue, May 28, 2013 at 6:31 PM, Charles R Harris
>> wrote:
>>>
>>> Hi All,
>>>
>>> There is a PR adding quickselect to numpy as a function `partition`.
>>> Comments on name and expo
On 05/29/2013 06:12 AM, josef.p...@gmail.com wrote:
> On Tue, May 28, 2013 at 6:31 PM, Charles R Harris
> wrote:
>> Hi All,
>>
>> There is a PR adding quickselect to numpy as a function `partition`.
>> Comments on name and exposure in the numpy API are welcome.
>
> I think the name is fine. It's p
On Tue, May 28, 2013 at 9:06 PM, Nathaniel Smith wrote:
> On Fri, May 24, 2013 at 3:12 PM, Richard Hattersley
> wrote:
>> Hi all,
>>
>> I'm in the process of defining some new dtypes to handle non-physical
>> calendars (such as the 360-day calendar used in the climate modelling
>> world). This is
Hi Andrew,
> Maybe a stupid question, but do you know a reference I could look at
> for the metadata and c_metadata fields you described?
Sorry ... no. I've not found anything. :-(
If I remember correctly, I got wind of the metadata aspect from the
mailing list discussions of datetime64. So for
Hi Nathaniel,
Thanks for the useful feedback - it'll definitely save me some time
chasing around the code base.
> dtype callbacks and ufuncs don't in general get access to the
> dtype object, so they can't access whatever parameters exist
Indeed - it is a little awkward. But I'm hoping I can use
