Hello,
We've recently posted the RC2 build of EPD (the Enthought Python
Distribution) with Python 2.5 version 4.0.30002 to the EPD website. You
may download the RC from here:
http://www.enthought.com/products/epdbeta.php
You can check out the release notes here:
https://svn.ent
Roman Bertle wrote:
> * Travis E. Oliphant <[EMAIL PROTECTED]> [081003 22:20]:
>
>> Roman Bertle wrote:
>>
>>> Hello,
>>>
>>> I have found something I call a bug in the numpy choose() method and
>>> wanted to report it in trac.
>>>
>>>
>> Thanks for your report. I'm not sure why
On Fri, Oct 17, 2008 at 1:27 PM, Tony S Yu <[EMAIL PROTECTED]> wrote:
> I ran into this weird behavior with astype(int)
>
> In [57]: a = np.array(1E13)
>
> In [58]: a.astype(int)
>
> Out[58]: array(-2147483648)
>
> I understand why large numbers need to be clipped when converting to
> int (althoug
Hi,
This a usual thing in integers conversions. If you transform an
integer like 0x from 16 bits to 8bits, you get 0x, thus a
negative number. As there are no processor instructions that do
saturations (DSP instructions), the behavior is to be expected.
Matthieu
2008/10/17 Tony S Yu
I ran into this weird behavior with astype(int)
In [57]: a = np.array(1E13)
In [58]: a.astype(int)
Out[58]: array(-2147483648)
I understand why large numbers need to be clipped when converting to
int (although I would have expected some sort of warning), but I'm
puzzled by the negative valu
On Thu, Oct 16, 2008 at 2:28 PM, Rob Hetland <[EMAIL PROTECTED]> wrote:
> I did not know that very useful thing. But now I do. This is solid
> proof that lurking on the mailing lists makes you smarter.
and that our documentation effort still has a long way to go !
FAQ added at
http://matplotli
* Travis E. Oliphant <[EMAIL PROTECTED]> [081003 22:20]:
> Roman Bertle wrote:
> > Hello,
> >
> > I have found something I call a bug in the numpy choose() method and
> > wanted to report it in trac.
> >
> Thanks for your report. I'm not sure why you are having trouble with
> Trac, but I've cr
numpy 1.2 is not buildable with python 2.6. You will have to wait
> for a later version, most probably 1.3,
>
Ok thanks David, guess I will have to wait till I can leverage the new
IEEE 754 support in python 2.6
___
Numpy-discussion mailing list
Numpy-di
Adam Foster wrote:
> Please add numpy 1.2.0 win32 package for python 2.6
Hi,
numpy 1.2 is not buildable with python 2.6. You will have to wait
for a later version, most probably 1.3,
cheers,
David
___
Numpy-discussion mailing list
Numpy-discussion
Please add numpy 1.2.0 win32 package for python 2.6
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
2008/10/16 Rob Hetland <[EMAIL PROTECTED]>:
>
> On Oct 14, 2008, at 12:56 AM, Stéfan van der Walt wrote:
>
>> Here is an implementation in Python, ctypes and in weave:
>>
>> http://mentat.za.net/source/pnpoly.tar.bz2
>>
>> Regards
>> Stéfan
>
> This question gets asked about once a month on the mai
> BTW, I can confirm that the latest official MKL does not work with
> numpy, as it is explained on the Intel forum
> (http://software.intel.com/en-us/forums/intel-math-kernel-library/topic/60460).
> I get the i_free not defined issue.
For those who run into this issue, you have to use MKL 10.0.2
12 matches
Mail list logo