Re: [Numpy-discussion] Memory mapping and NPZ files

On 10/12/2015 13:55, Sturla Molden wrote: Mathieu Dubois wrote: Does it make sense? No. Memory mapping should just memory map, not do all sorts of crap. The point is precisely that, you can't do memory mapping with Npz files (while it works with Npy

Re: [Numpy-discussion] Memory mapping and NPZ files

On 10/12/2015 15:35, Sebastian Berg wrote: On Mi, 2015-12-09 at 15:51 +0100, Mathieu Dubois wrote: Dear all, If I am correct, using mmap_mode with Npz files has no effect i.e.: f = np.load("data.npz", mmap_mode="r") X = f['X'] will load all the data in memory. My take on it is, that no, I

Re: [Numpy-discussion] Should dtypes have an ndim attribute?

On Dec 10, 2015 4:11 AM, "Andy Ray Terrel" wrote: > > That's essentially what datashape did over in the blaze ecosystem. It gets a bit fancier to support ragged arrays and optional types. > > http://datashape.readthedocs.org/en/latest/ IIUC this is a much more modest

[Numpy-discussion] volunteers for 1.11.0 release manager?

Hi All, Thought I'd bring this up. I think the 1.11.0 release should be fairly easy as releases go, so if someone wants to get some practice with making releases this is probably a good one to start with. We should branch 1.11.x sometime before the end of January. It is almost in branchable

[Numpy-discussion] Numpy intermittent seg fault

Hi, I'm experiencing random segmentation faults from numpy. I have generated a core dumped and extracted a stack trace, the following: #0 0x7f3a8d921d5d in getenv () from /lib64/libc.so.6 #1 0x7f3a843bde21 in blas_set_parameter () from

Re: [Numpy-discussion] Numpy intermittent seg fault

On Thu, Dec 10, 2015 at 4:05 PM, Jacopo Sabbatini wrote: > Hi, > > I'm experiencing random segmentation faults from numpy. I have generated a > core dumped and extracted a stack trace, the following: > > #0 0x7f3a8d921d5d in getenv () from /lib64/libc.so.6 >

[Numpy-discussion] Should dtypes have an ndim attribute?

Hi, I have made a modest proposal in issue #6752 . Basically, the proposal is to add an `ndim` attribute to dtypes. Currently, arrays have a shape and an ndim attribute, where ndim equals len(shape). dtype objects have a shape attribute, but no

Re: [Numpy-discussion] Should dtypes have an ndim attribute?

That's essentially what datashape did over in the blaze ecosystem. It gets a bit fancier to support ragged arrays and optional types. http://datashape.readthedocs.org/en/latest/ On Dec 10, 2015 5:14 AM, "Gerrit Holl" wrote: > Hi, > > I have made a modest proposal in issue

Re: [Numpy-discussion] When to stop supporting Python 2.6?

On 12/09/2015 12:10 AM, Ralf Gommers wrote: On Wed, Dec 9, 2015 at 12:01 AM, Chris Barker > wrote: drop 2.6 I still don't understand why folks insist that they need to run a (very)) old python on an old OS, but need the latest

Re: [Numpy-discussion] Memory mapping and NPZ files

Mathieu Dubois wrote: > Does it make sense? No. Memory mapping should just memory map, not do all sorts of crap. Sturla ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org

Re: [Numpy-discussion] When to stop supporting Python 2.6?

On Thu, Dec 10, 2015 at 4:20 AM, Julian Taylor < jtaylor.deb...@googlemail.com> wrote: > On 12/09/2015 12:10 AM, Ralf Gommers wrote: > >> >> >> On Wed, Dec 9, 2015 at 12:01 AM, Chris Barker > > wrote: >> >> drop 2.6 >> >> I still don't

Re: [Numpy-discussion] When to stop supporting Python 2.6?

> On 11 Dec 2015, at 07:52, Paul Hobson wrote: > > > > On Thu, Dec 10, 2015 at 4:20 AM, Julian Taylor > wrote: > On 12/09/2015 12:10 AM, Ralf Gommers wrote: > > > On Wed, Dec 9, 2015 at 12:01 AM,

Re: [Numpy-discussion] Memory mapping and NPZ files

On Mi, 2015-12-09 at 15:51 +0100, Mathieu Dubois wrote: > Dear all, > > If I am correct, using mmap_mode with Npz files has no effect i.e.: > f = np.load("data.npz", mmap_mode="r") > X = f['X'] > will load all the data in memory. > My take on it is, that no, I do not want implicit