On 2015/01/28 6:29 PM, Charles R Harris wrote:
>
>
> And as for "The 64 bits of long long really isn't enough and leads
> to all sorts of compromises". not long enough for what? I've always
> thought that what we need is the ability to set the epoch. Does
> anyone ever need picoseco
On Wed, Jan 28, 2015 at 6:13 PM, Chris Barker wrote:
> Sorry not to notice this for a while -- I've been distracted by
> python-ideas. (Nathaniel knows what I'm talking about ;-) )
>
> I do like the idea of prototyping some DateTime stuff -- it really isn't
> clear what's needed or how to do it
On Wed, Jan 28, 2015 at 5:13 PM, Chris Barker wrote:
> I tend to agree with Nathaniel that a ndarray subclass is less than ideal
> -- they tend to get ugly fast. But maybe that is the only way to do
> anything in Python, short of a major refactor to be able to write a dtype
> in Python -- which w
Sorry not to notice this for a while -- I've been distracted by
python-ideas. (Nathaniel knows what I'm talking about ;-) )
I do like the idea of prototyping some DateTime stuff -- it really isn't
clear what's needed or how to do it at this point. Though we did more or
less settle on a reasonable
HI all,
There has been some recent discussion going on on the limitations that
numpy imposes to taking views of an array with a different dtype.
As of right now, you can basically only take a view of an array if it has
no Python objects and neither the old nor the new dtype are structured.
Furthe
Den 27-01-2015 kl. 12:25 skrev Jaime Fernández del Río:
On Mon, Jan 26, 2015 at 10:28 PM, Jens Jørgen Mortensen
mailto:je...@fysik.dtu.dk>> wrote:
On 01/26/2015 11:02 AM, Jaime Fernández del Río wrote:
> On Mon, Jan 26, 2015 at 1:41 AM, Sebastian Berg
> mailto:sebast...@sipsolutions
