On Tue, Dec 8, 2009 at 8:03 PM, Francesc Alted wrote:
>
> That's true, but at least this can be attributed to a poor programming
> practice. The same happens with:
>
> array([1]).dtype == 'int32' # in 32-bit systems
> array([1]).dtype == 'int64' # in 64-bit systems
>
> and my impression is tha
A Monday 07 December 2009 16:32:50 Pauli Virtanen escrigué:
> ma, 2009-12-07 kello 09:50 -0500, Michael Droettboom kirjoitti:
> > Pauli Virtanen wrote:
>
> [clip]
>
> > > The character 'B' is already by unsigned bytes -- I wonder if it's easy
> > > to support 'B123' and plain 'B' at the same time
Pauli Virtanen wrote:
> ma, 2009-12-07 kello 09:50 -0500, Michael Droettboom kirjoitti:
>
>> Pauli Virtanen wrote:
>>
> [clip]
>
>>> The character 'B' is already by unsigned bytes -- I wonder if it's easy
>>> to support 'B123' and plain 'B' at the same time, or whether we have to
>>> pic
ma, 2009-12-07 kello 09:50 -0500, Michael Droettboom kirjoitti:
> Pauli Virtanen wrote:
[clip]
> > The character 'B' is already by unsigned bytes -- I wonder if it's easy
> > to support 'B123' and plain 'B' at the same time, or whether we have to
> > pick a different letter for "byte strings". 'y'
Pauli Virtanen wrote:
> ma, 2009-12-07 kello 09:12 -0500, Michael Droettboom kirjoitti:
>
>>> We need character arrays for the astro people. I assume these will be
>>> byte arrays. Maybe Michael will weigh in here.
>>>
>> I can't find in the thread where removing byte arrays (meaning arr
ma, 2009-12-07 kello 09:12 -0500, Michael Droettboom kirjoitti:
> > We need character arrays for the astro people. I assume these will be
> > byte arrays. Maybe Michael will weigh in here.
>
> I can't find in the thread where removing byte arrays (meaning arrays of
> fixed-length non-unicode stri
Charles R Harris wrote:
>
>
>
> We need character arrays for the astro people. I assume these will be
> byte arrays. Maybe Michael will weigh in here.
I can't find in the thread where removing byte arrays (meaning arrays of
fixed-length non-unicode strings) was suggested -- though changing the
d
su, 2009-12-06 kello 12:54 +0900, David Cournapeau kirjoitti:
> On Sun, Dec 6, 2009 at 9:41 AM, Pauli Virtanen wrote:
> > Hi,
> >
> > I'd like to commit my Py3 Numpy branch to SVN trunk soon:
> >
> >http://github.com/pv/numpy-work/commits/py3k
>
> Awesome - I think we should merge this AS
On Sat, Dec 5, 2009 at 10:54 PM, David Cournapeau wrote:
> On Sun, Dec 6, 2009 at 9:41 AM, Pauli Virtanen wrote:
>> Hi,
>>
>> I'd like to commit my Py3 Numpy branch to SVN trunk soon:
>>
>> http://github.com/pv/numpy-work/commits/py3k
>
> Awesome - I think we should merge this ASAP. In par
On Sun, Dec 6, 2009 at 9:41 AM, Pauli Virtanen wrote:
> Hi,
>
> I'd like to commit my Py3 Numpy branch to SVN trunk soon:
>
> http://github.com/pv/numpy-work/commits/py3k
Awesome - I think we should merge this ASAP. In particular, I would
like to start fixing platforms-specific issues.
Co
On Sat, Dec 5, 2009 at 7:18 PM, Charles R Harris
wrote:
>
>
> On Sat, Dec 5, 2009 at 5:41 PM, Pauli Virtanen wrote:
>
>> Hi,
>>
>> I'd like to commit my Py3 Numpy branch to SVN trunk soon:
>>
>>http://github.com/pv/numpy-work/commits/py3k
>>
>> For an overview, check the notes:
>>
>>
On Sat, Dec 5, 2009 at 5:41 PM, Pauli Virtanen wrote:
> Hi,
>
> I'd like to commit my Py3 Numpy branch to SVN trunk soon:
>
>http://github.com/pv/numpy-work/commits/py3k
>
> For an overview, check the notes:
>
>http://github.com/pv/numpy-work/blob/py3k/doc/Py3K.txt
>
>
That's a ni
Hi,
I'd like to commit my Py3 Numpy branch to SVN trunk soon:
http://github.com/pv/numpy-work/commits/py3k
For an overview, check the notes:
http://github.com/pv/numpy-work/blob/py3k/doc/Py3K.txt
None of the changes should affect behavior on Py2. The test status
currently is:
13 matches
Mail list logo
