Hey all,
I'm wondering who has tried to make NumPy work with Python 3.3. The Unicode
handling was significantly improved in Python 3.3 and the array-scalar code
(which assumed a certain structure for UnicodeObjects) is not working now.
It would be nice to get 1.7.0 working with Python 3.3
On Thu, Jul 26, 2012 at 9:26 PM, Tom Aldcroft wrote:
> There was a thread in January discussing the non-obvious behavior of
> numpy.mean() for large arrays of float32 values [1]. This issue is
> nicely discussed at the end of the numpy.mean() documentation [2] with
> an example:
>
> >>> a = np.z
There was a thread in January discussing the non-obvious behavior of
numpy.mean() for large arrays of float32 values [1]. This issue is
nicely discussed at the end of the numpy.mean() documentation [2] with
an example:
>>> a = np.zeros((2, 512*512), dtype=np.float32)
>>> a[0, :] = 1.0
>>> a[1, :]
On Thu, Jul 26, 2012 at 2:29 PM, Prakash Joshi wrote:
> Hi All,
>
> I am building numpy 1.6.2 on 64 bit Mac OSX/CentOS and I found many
> warnings and errors of similar kind, however the numpy passes all the
> tests.
> Please let me know if I can consider this build as good?
>
>
> llvm-gcc-4.2: _
On Fri, Jul 27, 2012 at 12:05 AM, Colin J. Williams
wrote:
> On 26/07/2012 4:57 PM, Benjamin Root wrote:
>
>
> On Thu, Jul 26, 2012 at 4:45 PM, Colin J. Williams wrote:
>>
>> It seems that these standards have been adopted, which is good:
>>
>> The following import conventions are used throughout
On 26/07/2012 4:57 PM, Benjamin Root
wrote:
On Thu, Jul 26, 2012 at 4:45 PM, Colin J.
Williams
wrote:
It seems that these standards have been
adopted, which is good:
Sent from my BlackBerry® PlayBook™
www.blackberry.com
--
*From:* "Benjamin Root"
*To:* "Discussion of Numerical Python"
*Sent:* 26 July 2012 16:57
*Subject:* Re: [Numpy-discussion] Synonym standards
On Thu, Jul 26, 2012 at 4:45 PM, Colin J. Williams wrote:
> It s
On Thu, Jul 26, 2012 at 4:45 PM, Colin J. Williams wrote:
> It seems that these standards have been adopted, which is good:
>
> The following import conventions are used throughout the NumPy source and
> documentation:
>
> import numpy as np
> import matplotlib as mpl
> import matplotlib.pyplot
It seems that these standards
have been adopted, which is good:
The following import conventions are used throughout the NumPy
source and documentation:
import numpy as np
import matplotlib as mpl
import matplotlib.pyplot as plt
Source: https://gi
Hi All,
I am building numpy 1.6.2 on 64 bit Mac OSX/CentOS and I found many
warnings and errors of similar kind, however the numpy passes all the
tests.
Please let me know if I can consider this build as good?
llvm-gcc-4.2: _configtest.c
_configtest.c:5: error: size of array Œtest_array¹ is neg
Hi all,
After run the command below (numpy 1.6.2):
python setup.py build
I receive the following message error:
gcc: build/src.linux-x86_64-2.5/numpy/core/src/npymath/ieee754.c
In file included from numpy/core/src/npymath/ieee754.c.src:8:
numpy/core/src/npymath/npy_math_private.h:452: error: ex
On a Linux machine:
> uname -srvop
Linux 2.6.18-308.8.2.el5 #1 SMP Tue May 29 11:54:17 EDT 2012 x86_64
GNU/Linux
this example shows an apparent problem with the where function:
Python 2.7.1 (r271:86832, Dec 21 2010, 11:19:43)
[GCC 4.1.2 20080704 (Red Hat 4.1.2-48)] on linux2
Type "help", "copy
Forwarding Jordi's message on the trac migration, he's having issues
sending it directly.
-- Forwarded message --
From: Jordi Torrents
Date: 2012/7/26
Subject: Re: [Numpy-discussion] Github notifications and
trac-to-github migration
To: Aric Hagberg
Cc: Discussion of Numerical Py
13 matches
Mail list logo