If not now, when?
Thanks,
Dick Moores
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
What is the difference between these two versions? I usually check out the svn
version (now 2.0) and it compiles well with python 2.6, 2.7 and 3.1.
Nadav.
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/li
On Sun, Jul 18, 2010 at 3:36 PM, Pauli Virtanen wrote:
> Hi,
>
> The current way of Numpy handles ordering of complex nan is not very well
> defined. We should attempt to clarify this for 1.5.0.
>
> For example, what should these return:
>
>r1 = np.maximum(complex(1, nan), complex(2, 0))
>
>
mac os x leopard 10.5..
EPD installed
i just don't understand why i get one thing when i ask for another.
i can get what i want, but only by not asking for it.
thanks,
Ross
On Sun, Jul 18, 2010 at 6:02 PM, Pauli Virtanen wrote:
> Sun, 18 Jul 2010 17:26:13 -0500, Ross Harder wrote:
>> I don't u
On Sun, Jul 18, 2010 at 5:00 PM, Pauli Virtanen wrote:
> Sun, 18 Jul 2010 15:57:47 -0600, Charles R Harris wrote:
> > On Sun, Jul 18, 2010 at 3:36 PM, Pauli Virtanen wrote:
> [clip]
> >> I suggest the following, aping the way the real nan works:
> >>
> >> - (z, nan), (nan, z), (nan, nan), where
Sun, 18 Jul 2010 15:57:47 -0600, Charles R Harris wrote:
> On Sun, Jul 18, 2010 at 3:36 PM, Pauli Virtanen wrote:
[clip]
>> I suggest the following, aping the way the real nan works:
>>
>> - (z, nan), (nan, z), (nan, nan), where z is any fp value, are all
>> equivalent representations of "cnan",
Sun, 18 Jul 2010 17:26:13 -0500, Ross Harder wrote:
> I don't understand the following.
>>> a=np.zeros( (3,3,3), dtype='Complex128')
a
> array([[[0.0+0.0j, 0.0+0.0j, 0.0+0.0j],
> [0.0+0.0j, 0.0+0.0j, 0.0+0.0j],
> [0.0+0.0j, 0.0+0.0j, 0.0+0.0j]],
>
>[[0.0+0.0j, 0.0+0.0j
I don't understand the following.
>> a=np.zeros( (3,3,3), dtype='Complex128')
>>> a
array([[[0.0+0.0j, 0.0+0.0j, 0.0+0.0j],
[0.0+0.0j, 0.0+0.0j, 0.0+0.0j],
[0.0+0.0j, 0.0+0.0j, 0.0+0.0j]],
[[0.0+0.0j, 0.0+0.0j, 0.0+0.0j],
[0.0+0.0j, 0.0+0.0j, 0.0+0.0j],
[0.0+
On 7/18/2010 2:20 PM, David Cournapeau wrote:
On Sun, Jul 18, 2010 at 8:34 PM, Peter
wrote:
On Sun, Jul 18, 2010 at 6:02 PM, cool-RR wrote:
Hello.
I'd appreciate if the NumPy team could provide an MSI installer
for Python 2.7.
Thanks,
Ram Rachum.
You're not the only person who would like
On Sun, Jul 18, 2010 at 3:36 PM, Pauli Virtanen wrote:
> Hi,
>
> The current way of Numpy handles ordering of complex nan is not very well
> defined. We should attempt to clarify this for 1.5.0.
>
> For example, what should these return:
>
>r1 = np.maximum(complex(1, nan), complex(2, 0))
>
>
Hi,
The current way of Numpy handles ordering of complex nan is not very well
defined. We should attempt to clarify this for 1.5.0.
For example, what should these return:
r1 = np.maximum(complex(1, nan), complex(2, 0))
r2 = np.complex64(complex(1, nan)) < np.complex64(complex(2, 0))
o
On Sun, Jul 18, 2010 at 8:34 PM, Peter
wrote:
> On Sun, Jul 18, 2010 at 6:02 PM, cool-RR wrote:
>> Hello.
>> I'd appreciate if the NumPy team could provide an MSI installer
>> for Python 2.7.
>> Thanks,
>> Ram Rachum.
>
> You're not the only person who would like this - it was discussed
> here ju
On Sun, Jul 18, 2010 at 6:02 PM, cool-RR wrote:
> Hello.
> I'd appreciate if the NumPy team could provide an MSI installer
> for Python 2.7.
> Thanks,
> Ram Rachum.
You're not the only person who would like this - it was discussed
here just 9 days ago, thread title "A release for python 2.7?", an
On 7/18/2010 7:52 AM, Pauli Virtanen wrote:
> Sun, 18 Jul 2010 21:13:43 +0800, Ralf Gommers wrote:
> [clip]
>> Builds fine on OS X 10.6 with both 2.7 and 3.1, and all tests pass. With
>> one exception: in-place build for 3.1 is broken. Does anyone know is
>> this is a distutils or numpy issue? Th
Hello.
I'd appreciate if the NumPy team could provide an MSI installer for Python
2.7.
Thanks,
Ram Rachum.
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Sun, 18 Jul 2010 23:59:24 +0800, Ralf Gommers wrote:
> Scipy Trac seems to work very well now, I get notification emails for
> comments on tickets etc. For numpy Trac, nothing right now. Can this be
> fixed?
Works for me.
Did you check if your email address is correct there? (-> Preferences)
--
Scipy Trac seems to work very well now, I get notification emails for
comments on tickets etc. For numpy Trac, nothing right now. Can this be
fixed?
Thanks,
Ralf
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/l
[shameless plug]
For those of you tired of waiting for 2to3 after "rm -rf build":
http://github.com/pv/lib2to3cache
and
cd numpy/
USE_2TO3CACHE=1 python3 setup.py build
--
Pauli Virtanen
___
NumPy-Discussion mailing list
Num
Sun, 18 Jul 2010 21:13:43 +0800, Ralf Gommers wrote:
[clip]
> Builds fine on OS X 10.6 with both 2.7 and 3.1, and all tests pass. With
> one exception: in-place build for 3.1 is broken. Does anyone know is
> this is a distutils or numpy issue? The problem is that on import
> numpy.__config__ can no
On Sun, Jul 18, 2010 at 2:51 AM, Charles R Harris wrote:
>
>
> On Sat, Jul 17, 2010 at 12:32 PM, Pauli Virtanen wrote:
>
>> Dear all,
>>
>> Based on patches contributed by Christoph Gohlke, I've created a branch
>> for 1.5.x:
>>
>>http://svn.scipy.org/svn/numpy/branches/1.5.x
>>
>> It sh
Hello,
I finally found the time to update numpy in Debian. But, there is a problem...
As you probably know, we support several architectures and we need to
have any package available on each of them. After the upload I noticed
numpy has problem building on alpha [1] (ieee754.c compilation error,
p
21 matches
Mail list logo
