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 until it becomes too
>> > cumbersome to support.
>> >
>> >
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, Tho
On Sun, Feb 22, 2015 at 5:46 PM, Charles R Harris 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 wrote:
>>
>>> On Sun,
On Sun, Feb 22, 2015 at 2:52 PM, Nathaniel Smith wrote:
> On Sun, Feb 22, 2015 at 10:21 AM, Aldcroft, Thomas
> 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 [1, 2].
> >
&
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 t
On Tue, Aug 12, 2014 at 12:17 PM, Eelco Hoogendoorn <
hoogendoorn.ee...@gmail.com> wrote:
> Thanks. Prompted by that stackoverflow question, and similar problems I
> had to deal with myself, I started working on a much more general extension
> to numpy's functionality in this space. Like you noted
On Wed, Nov 26, 2014 at 8:24 AM, Charles R Harris wrote:
>
>
> On Wed, Nov 26, 2014 at 2:36 AM, Sebastian Berg <
> sebast...@sipsolutions.net> wrote:
>
>> On Mi, 2014-11-26 at 08:44 +, David Cournapeau wrote:
>> > Hi,
>> >
>> >
>> > Would anybody mind if I create a label "newcomers" on GH, an
On Fri, Jul 18, 2014 at 11:10 AM, Julian Taylor <
jtaylor.deb...@googlemail.com> wrote:
> On Thu, Jul 17, 2014 at 5:48 PM, Nathaniel Smith wrote:
> > On Tue, Jul 15, 2014 at 4:29 PM, Charles R Harris
> > wrote:
> >> Thinking more about it, the easiest thing to do might be to make the S
> dtype
>
On Thu, Jul 17, 2014 at 11:52 AM, Nathaniel Smith wrote:
> On Tue, Jul 15, 2014 at 7:40 PM, Aldcroft, Thomas
> wrote:
> >
> > On Sat, Jul 12, 2014 at 8:02 PM, Nathaniel Smith wrote:
> >>
> >> OTOH, fixed length nul padded latin1 would be useful for va
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`
On Wed, Jul 16, 2014 at 6:48 AM, Todd wrote:
> On Jul 16, 2014 11:43 AM, "Chris Barker" 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 running py3 to see what 'S' does now,
On Sat, Jul 12, 2014 at 8:02 PM, Nathaniel Smith wrote:
> On 12 Jul 2014 23:06, "Charles R Harris"
> 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, the unicode type is stored as
On Tue, Jan 21, 2014 at 8:55 AM, Charles R Harris 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.h
On Mon, Jan 20, 2014 at 6:12 PM, Charles R Harris 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 wrote:
>>
>>> On Mon, Jan 20, 2014 at 10:28 PM, Charles R Harris
>>> wrote:
>>>
On Mon, Jan 20, 2014 at 10:40 AM, Oscar Benjamin 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
> > wrote:
> > > How significant are the performance issues? Does anyone really use
> numpy
&
On Mon, Jan 20, 2014 at 5:11 AM, Oscar Benjamin
wrote:
> 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 new one to
> > ad
On Fri, Jan 17, 2014 at 5:30 PM, 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 new one to
> address this one question (i.e. dont bring up genfromtext here):
>
> Would it b
On Fri, Jan 17, 2014 at 4:43 PM, wrote:
> On Fri, Jan 17, 2014 at 4:20 PM, Chris Barker
> wrote:
> > On Fri, Jan 17, 2014 at 12:36 PM, wrote:
> >>
> >> > ('S' ?) -- which is probably not what you want particularly if you
> >> > specify
> >> > an encoding. Though I can't figure out at the moment
On Fri, Jan 17, 2014 at 5:59 AM, Pauli Virtanen wrote:
> Julian Taylor 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 to deal with or 4
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 limitation
On Thu, Jun 13, 2013 at 5:06 PM, wrote:
> On Thu, Jun 13, 2013 at 4:47 PM, Eric Firing wrote:
> > On 2013/06/13 10:36 AM, Benjamin Root wrote:
> >>
> >> On Thu, Jun 13, 2013 at 9:36 AM, Aldcroft, Thomas
> >> mailto:aldcr...@head.cfa.harvard.edu>>
>
On Wed, Jun 12, 2013 at 2:55 PM, Eric Firing 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 existing 'ma.fille
On Mon, Jun 10, 2013 at 3:47 PM, Nathaniel Smith 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 masked arr
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 wrote:
>
>> On Thu, May 30, 2013 at 9:21 PM, Aldcroft, Thomas
>> wrote:
>> > I'm seeing some behavio
On Thu, May 30, 2013 at 4:27 PM, Robert Kern wrote:
> On Thu, May 30, 2013 at 9:21 PM, Aldcroft, Thomas
> 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() is calli
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 simple
26 matches
Mail list logo
