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

On Fri, Dec 4, 2015 at 6:13 AM, David Cournapeau wrote: > > > On Fri, Dec 4, 2015 at 11:06 AM, Nathaniel Smith wrote: > >> On Fri, Dec 4, 2015 at 1:27 AM, David Cournapeau >> wrote: >> > I would be in favour of dropping 3.3, but not 2.6

[Numpy-discussion] One-byte string dtype: third time's the charm?

The idea of a one-byte string dtype has been extensively discussed twice before, with a lot of good input and ideas, but no action [1, 2]. tl;dr: Perfect is the enemy of good. Can numpy just add a one-byte string dtype named 's' that uses latin-1 encoding as a bridge to enable Python 3 usage in

Re: [Numpy-discussion] One-byte string dtype: third time's the charm?

On Sun, Feb 22, 2015 at 5:56 PM, Aldcroft, Thomas aldcr...@head.cfa.harvard.edu wrote: On Sun, Feb 22, 2015 at 5:46 PM, Charles R Harris charlesr.har...@gmail.com wrote: On Sun, Feb 22, 2015 at 3:40 PM, Aldcroft, Thomas aldcr...@head.cfa.harvard.edu wrote: On Sun, Feb 22, 2015

Re: [Numpy-discussion] One-byte string dtype: third time's the charm?

On Sun, Feb 22, 2015 at 2:52 PM, Nathaniel Smith n...@pobox.com wrote: On Sun, Feb 22, 2015 at 10:21 AM, Aldcroft, Thomas aldcr...@head.cfa.harvard.edu wrote: The idea of a one-byte string dtype has been extensively discussed twice before, with a lot of good input and ideas, but no action

Re: [Numpy-discussion] One-byte string dtype: third time's the charm?

On Sun, Feb 22, 2015 at 5:46 PM, Charles R Harris charlesr.har...@gmail.com wrote: On Sun, Feb 22, 2015 at 3:40 PM, Aldcroft, Thomas aldcr...@head.cfa.harvard.edu wrote: On Sun, Feb 22, 2015 at 2:52 PM, Nathaniel Smith n...@pobox.com wrote: On Sun, Feb 22, 2015 at 10:21 AM, Aldcroft

Re: [Numpy-discussion] String type again.

On Tue, Jul 15, 2014 at 11:15 AM, Charles R Harris charlesr.har...@gmail.com wrote: On Tue, Jul 15, 2014 at 5:26 AM, Sebastian Berg sebast...@sipsolutions.net wrote: On Sa, 2014-07-12 at 12:17 -0500, Charles R Harris wrote: As previous posts have pointed out, Numpy's `S` type is

Re: [Numpy-discussion] String type again.

On Thu, Jul 17, 2014 at 11:52 AM, Nathaniel Smith n...@pobox.com wrote: On Tue, Jul 15, 2014 at 7:40 PM, Aldcroft, Thomas aldcr...@head.cfa.harvard.edu wrote: On Sat, Jul 12, 2014 at 8:02 PM, Nathaniel Smith n...@pobox.com wrote: OTOH, fixed length nul padded latin1 would be useful

Re: [Numpy-discussion] String type again.

On Wed, Jul 16, 2014 at 6:48 AM, Todd toddr...@gmail.com wrote: On Jul 16, 2014 11:43 AM, Chris Barker chris.bar...@noaa.gov wrote: So numpy should have dtypes to match these. We're a bit stuck, however, because 'S' mapped to the py2 string type, which no longer exists in py3. Sorry not

Re: [Numpy-discussion] String type again.

On Sat, Jul 12, 2014 at 8:02 PM, Nathaniel Smith n...@pobox.com wrote: On 12 Jul 2014 23:06, Charles R Harris charlesr.har...@gmail.com wrote: As previous posts have pointed out, Numpy's `S` type is currently treated as a byte string, which leads to more complicated code in python3. OTOH,

Re: [Numpy-discussion] A one-byte string dtype?

On Mon, Jan 20, 2014 at 6:12 PM, Charles R Harris charlesr.har...@gmail.com wrote: On Mon, Jan 20, 2014 at 3:58 PM, Charles R Harris charlesr.har...@gmail.com wrote: On Mon, Jan 20, 2014 at 3:35 PM, Nathaniel Smith n...@pobox.com wrote: On Mon, Jan 20, 2014 at 10:28 PM, Charles R

Re: [Numpy-discussion] A one-byte string dtype?

On Tue, Jan 21, 2014 at 8:55 AM, Charles R Harris charlesr.har...@gmail.com wrote: On Tue, Jan 21, 2014 at 5:54 AM, Aldcroft, Thomas aldcr...@head.cfa.harvard.edu wrote: On Mon, Jan 20, 2014 at 6:12 PM, Charles R Harris charlesr.har...@gmail.com wrote: On Mon, Jan 20, 2014 at 3

Re: [Numpy-discussion] A one-byte string dtype?

On Mon, Jan 20, 2014 at 5:11 AM, Oscar Benjamin oscar.j.benja...@gmail.comwrote: On Fri, Jan 17, 2014 at 02:30:19PM -0800, Chris Barker wrote: Folks, I've been blathering away on the related threads a lot -- sorry if it's too much. It's gotten a bit tangled up, so I thought I'd start a

Re: [Numpy-discussion] A one-byte string dtype?

On Mon, Jan 20, 2014 at 10:40 AM, Oscar Benjamin oscar.j.benja...@gmail.com wrote: On Mon, Jan 20, 2014 at 10:00:55AM -0500, Aldcroft, Thomas wrote: On Mon, Jan 20, 2014 at 5:11 AM, Oscar Benjamin oscar.j.benja...@gmail.comwrote: How significant are the performance issues? Does anyone

Re: [Numpy-discussion] using loadtxt to load a text file in to a numpy array

On Fri, Jan 17, 2014 at 5:59 AM, Pauli Virtanen p...@iki.fi wrote: Julian Taylor jtaylor.debian at googlemail.com writes: [clip] - inconvenience in dealing with strings in python 3. bytes are not strings in python3 which means ascii data is either a byte array which can be inconvenient

Re: [Numpy-discussion] using loadtxt to load a text file in to a numpy array

On Fri, Jan 17, 2014 at 4:43 PM, josef.p...@gmail.com wrote: On Fri, Jan 17, 2014 at 4:20 PM, Chris Barker chris.bar...@noaa.gov wrote: On Fri, Jan 17, 2014 at 12:36 PM, josef.p...@gmail.com wrote: ('S' ?) -- which is probably not what you want particularly if you specify an

Re: [Numpy-discussion] A one-byte string dtype?

On Fri, Jan 17, 2014 at 5:30 PM, Chris Barker chris.bar...@noaa.gov wrote: Folks, I've been blathering away on the related threads a lot -- sorry if it's too much. It's gotten a bit tangled up, so I thought I'd start a new one to address this one question (i.e. dont bring up genfromtext

[Numpy-discussion] Join and stacking for structured arrays

For the astropy Table class (which wraps numpy structured arrays), I wrote functions that perform table joins and concatenate tables along rows or columns. These are reasonably full-featured and handle most of the common needs for these operations. The join function here addresses some

Re: [Numpy-discussion] numpy.filled, again

On Thu, Jun 13, 2013 at 5:06 PM, josef.p...@gmail.com wrote: On Thu, Jun 13, 2013 at 4:47 PM, Eric Firing efir...@hawaii.edu wrote: On 2013/06/13 10:36 AM, Benjamin Root wrote: On Thu, Jun 13, 2013 at 9:36 AM, Aldcroft, Thomas aldcr...@head.cfa.harvard.edu mailto:aldcr

Re: [Numpy-discussion] numpy.filled, again

On Wed, Jun 12, 2013 at 2:55 PM, Eric Firing efir...@hawaii.edu wrote: On 2013/06/12 8:13 AM, Warren Weckesser wrote: That's why I suggested 'filledwith' (add the underscore if you like). This also allows a corresponding masked implementation, 'ma.filledwith', without clobbering the

Re: [Numpy-discussion] empty_like for masked arrays

On Mon, Jun 10, 2013 at 3:47 PM, Nathaniel Smith n...@pobox.com wrote: Hi all, Is there anyone out there using numpy masked arrays, who has an opinion on how empty_like (and its friends ones_like, zeros_like) should handle the mask? Right now apparently if you call np.ma.empty_like on a

[Numpy-discussion] __getitem__ and creating an array of objects

I'm seeing some behavior that I can't understand when creating a numpy array of Python objects. Basically it seems that np.array() is calling the object __getitem__ method for one object class but not another class, and I can't understand the difference. Here is an example, starting with a

Re: [Numpy-discussion] __getitem__ and creating an array of objects

On Thu, May 30, 2013 at 4:27 PM, Robert Kern robert.k...@gmail.com wrote: On Thu, May 30, 2013 at 9:21 PM, Aldcroft, Thomas aldcr...@head.cfa.harvard.edu wrote: I'm seeing some behavior that I can't understand when creating a numpy array of Python objects. Basically it seems that np.array

Re: [Numpy-discussion] __getitem__ and creating an array of objects

On Thu, May 30, 2013 at 4:58 PM, Aldcroft, Thomas aldcr...@head.cfa.harvard.edu wrote: On Thu, May 30, 2013 at 4:27 PM, Robert Kern robert.k...@gmail.comwrote: On Thu, May 30, 2013 at 9:21 PM, Aldcroft, Thomas aldcr...@head.cfa.harvard.edu wrote: I'm seeing some behavior that I can't