[Numpy-discussion] Notes from the numpy dev meeting at scipy 2015
Feng Yu
rainwoodman at gmail.com
Tue Aug 25 15:46:11 EDT 2015
Hi Nathaniel,
Thanks for the notes.
In some sense, the new dtype class(es) will provided a way of
formalizing these `weird` metadata, and probably exposing them to
Python.
May I add that please consider adding a way to declare the sorting
order (priority and direction) of fields in a structured array in the
new dtype as well?
Regards,
Yu
On Tue, Aug 25, 2015 at 12:21 PM, Antoine Pitrou <solipsis at pitrou.net> wrote:
> On Tue, 25 Aug 2015 03:03:41 -0700
> Nathaniel Smith <njs at pobox.com> wrote:
>>
>> Supporting third-party dtypes
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
> [...]
>>
>> Some features that would become straightforward to implement
>> (e.g. even in third-party libraries) if this were fixed:
>> - missing value support
>> - physical unit tracking (meters / seconds -> array of velocity;
>> meters + seconds -> error)
>> - better and more diverse datetime representations (e.g. datetimes
>> with attached timezones, or using funky geophysical or
>> astronomical calendars)
>> - categorical data
>> - variable length strings
>> - strings-with-encodings (e.g. latin1)
>> - forward mode automatic differentiation (write a function that
>> computes f(x) where x is an array of float64; pass that function
>> an array with a special dtype and get out both f(x) and f'(x))
>> - probably others I'm forgetting right now
>
> It should also be the opportunity to streamline datetime64 and
> timedelta64 dtypes. Currently the unit information is IIRC hidden in
> some weird metadata thing called the PyArray_DatetimeMetaData.
>
> Also, thanks the notes. It has been an interesting read.
>
> Regards
>
> Antoine.
>
>
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion
More information about the NumPy-Discussion
mailing list