You right, the delay is not in the memmap:
...
_data = N.memmap(filename, dtype=frame_type, mode=mode, offset=fh_size,
shape=nframes)
data = _data['data']
The delay is in the 2nd line which selects a field from a recarray.
I use a common drawing application mypaint that uses nump
On Wed, Oct 14, 2015 at 5:38 PM, Nathaniel Smith wrote:
> On Oct 14, 2015 9:15 AM, "Chris Barker" wrote:
> >
> > On Mon, Oct 12, 2015 at 9:27 AM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
> >>
> >> * Compiling with msvc9 or msvc10 for 32 bit Windows now requires SSE2.
> >> This wa
On Wed, Oct 14, 2015 at 12:38 PM, Ralf Gommers
wrote:
> I'm actually not sure if anyone even uses the 32 bit builds at all :-)
>>>
>> There's a lot of 32 bit python use out there still, including numpy.
>>
>
> If you want a quick impression, there are download stats for our binaries:
> http://sou
On Wed, Oct 14, 2015 at 6:47 PM, Chris Barker wrote:
>
> On Wed, Oct 14, 2015 at 9:38 AM, Nathaniel Smith wrote:
>
>> I'm actually not sure if anyone even uses the 32 bit builds at all :-)
>>
> There's a lot of 32 bit python use out there still, including numpy.
>
If you want a quick impression
On Wed, Oct 14, 2015 at 10:34 AM, Phil Hodge wrote:
> On 10/14/2015 11:59 AM, Chris Barker wrote:
>
>> we have no way to know when there will be leap-seconds in the future
>>
>
> Leap seconds are announced about six months in advance.
exactly -- so more than six month, we have no idea.
and eve
On 10/14/2015 11:59 AM, Chris Barker wrote:
we have no way to know when there will be leap-seconds in the future
Leap seconds are announced about six months in advance.
Phil
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.sc
On Wed, Oct 14, 2015 at 9:38 AM, Nathaniel Smith wrote:
> The change in 1.10.1 only affects msvc, which is not what most people are
> using (IIUC Enthought Canopy uses msvc, but the pypi, gohlke, and Anaconda
> builds don't).
>
Anaconda uses MSVC for the most part -- they _may_ compile numpy itse
On Oct 14, 2015 9:15 AM, "Chris Barker" wrote:
>
> On Mon, Oct 12, 2015 at 9:27 AM, Charles R Harris <
charlesr.har...@gmail.com> wrote:
>>
>> * Compiling with msvc9 or msvc10 for 32 bit Windows now requires SSE2.
>> This was the easiest fix for what looked to be some miscompiled code
when
>>
On Mon, Oct 12, 2015 at 9:27 AM, Charles R Harris wrote:
> * Compiling with msvc9 or msvc10 for 32 bit Windows now requires SSE2.
> This was the easiest fix for what looked to be some miscompiled code when
> SSE2 was not used.
>
Note that there is discusion right now on pyton-dev about requi
On Tue, Oct 13, 2015 at 5:08 PM, Marten van Kerkwijk <
m.h.vankerkw...@gmail.com> wrote:
> Maybe not directly relevant, but also very clearly why one should ideally
>> not use these a
>>
> all!
>>
> I wouldn't say not at all -- I'd say "not in some circumstances"
> Perhaps even less relevant, but
On Tue, Oct 13, 2015 at 3:58 PM, Nathaniel Smith wrote:
> > However, numpy datetime is optimized for compact storage and fast
> computation of absolute deltas (actual hours, minutes, seconds... not
> calendar units like "the next day" ).
>
> Except that ironically it actually can't compute absolu
On 10/14/2015 01:23 AM, Nadav Horesh wrote:
>
> I have binary files of size range between few MB to 1GB, which I read process
> as memory mapped files (via np.memmap). Until numpy 1.9 the creation of
> recarray on an existing file (without reading its content) was instantaneous,
> and now it
12 matches
Mail list logo
