On 2011-11-03 04:22, numpy-discussion-requ...@scipy.org wrote:
>
> Message: 1
> Date: Wed, 2 Nov 2011 22:20:15 -0500
> From: Benjamin Root
> Subject: Re: [Numpy-discussion] in the NA discussion, what can we
> agree on?
> To: Discussion of Numerical Python
> Message-ID:
>
> Content-Type
On 2011-06-24 17:30, Robert Kern wrote:
> On Fri, Jun 24, 2011 at 10:07, Laurent Gautier wrote:
>> > On 2011-06-24 16:43, Robert Kern wrote:
>>> >>
>>> >> On Fri, Jun 24, 2011 at 09:33, Charles R Harris
>>> >>wrote:
>>>
On 2011-06-24 16:43, Robert Kern wrote:
> On Fri, Jun 24, 2011 at 09:33, Charles R Harris
> wrote:
>> >
>> > On Fri, Jun 24, 2011 at 8:06 AM, Robert Kern
>> > wrote:
>>> >> The alternative proposal would be to add a few new dtypes that are
>>> >> NA-aware. E.g. an nafloat64 would reserve a
On 2011-06-24 13:59, Nathaniel Smith wrote:
> On Thu, Jun 23, 2011 at 5:56 PM, Benjamin Root wrote:
>> Lastly, I am not entirely familiar with R, so I am also very curious about
>> what this magical "NA" value is, and how it compares to how NaNs work.
>> Although, Pierre brought up the very good
Hi,
I did not find the following problem reported.
When trying to install Numpy 1.6 with Python 2.7.1+ (r271:86832), gcc
4.5.2, and pip 1.0.1 (through a virtualenv 1.4.2 Python) it fails fails
with:
File "/usr/lib/python2.7/distutils/command/config.py", line 103,
in _check_compiler
Thanks for the reply.
On 11/17/10 7:00 PM, Pauli Virtanen wrote:
>
> Wed, 17 Nov 2010 08:40:50 +0100, Laurent Gautier wrote:
> [clip]
>> > __main__:1: RuntimeWarning: Item size computed from the PEP 3118 buffer
>> > format string does not match the actual item s
Hi,
I am developping a package using the buffer interface, and with Python
2.7 - Numpy 1.5, the following annoying warning has been reported.
__main__:1: RuntimeWarning: Item size computed from the PEP 3118
buffer format string does not match the actual item size.
Beside warning it appears that
