Hi Jarrod,
any news with the 1.0.5? If you have same prerelease, I'd like to test
it. Debian has just moved from python2.4 to python2.5 yesterday, so
I'd like to test numpy in advance, I am sure there will be some issues
to fix.
Ondrej
___
Tested fine on my old Classic Athlon 500 (no SSE) under Win98. It
correctly reported installing the non-SSE version when I clicked on the
details button on the last page of the install wizard. Whereas
previously numpy.test() would bring up an illegal operation dialog box,
now all tests pass.
Everything installed without problem on Intel Pentium M on my notebook
recognized as SSE2 capable.
Installer found Python 2.5. immediately, which I just installed and
all my windows environment settings are still setup for python 2.4
Thanks,
Josef
numpy.test()
Numpy is installed in
This (on little-endian machine) surprised me:
In [23]:np.ones((1,), dtype='i2')
Out[23]:array([1], dtype=int16)
In [24]:np.ones((1,), dtype='i2')
Out[24]:array([256], dtype=int16)
I expected the value to be [1] in either case. Am I wrong? The
docstring gives no hint that this is how the dtype
On Mon, Apr 14, 2008 at 1:59 PM, Eric Firing [EMAIL PROTECTED] wrote:
This (on little-endian machine) surprised me:
In [23]:np.ones((1,), dtype='i2')
Out[23]:array([1], dtype=int16)
In [24]:np.ones((1,), dtype='i2')
Out[24]:array([256], dtype=int16)
I expected the value to be [1] in
Neil Crighton wrote:
The Win32 installer works on my Vista machine. There is one failed
test, but I think that's just because it tries to write somewhere it
doesn't have permission - I installed Python in /Program
Files/Python25/, and you need to be an administrator to write to
Program
After the SciPy sprints some useful discussions took place that helped
us all realize that we have made enough changes to the code base that we
will need to call any release from the trunk 1.1
I don't think that is a big problem. However, there have also been a
lot of substantial bug fixes
On Mon, Apr 14, 2008 at 9:59 PM, Travis E. Oliphant
[EMAIL PROTECTED] wrote:
So, the question is. Do we have enough energy in the community to
release the current trunk as 1.1 as well as release 1.0.5 which does not
contain any of the code/api changes, but just the bug fixes? The answer
On Mon, Apr 14, 2008 at 10:59 PM, Travis E. Oliphant [EMAIL PROTECTED]
wrote:
After the SciPy sprints some useful discussions took place that helped
us all realize that we have made enough changes to the code base that we
will need to call any release from the trunk 1.1
I don't think that is
On Mon, Apr 14, 2008 at 10:38 PM, Charles R Harris
[EMAIL PROTECTED] wrote:
Let's not rush 1.1, then. I think with another week or two we should be able
to settle most of the outstanding bugs and it would be good to do so before
getting caught up in planning 1.2.
+1. I think that we are so
On Mon, 14 Apr 2008, Charles R Harris apparently wrote:
Let's not rush 1.1, then.
Will matrix behavior change in 1.1, as discussed from time
to time? Perhaps it just takes a very small change in __getitem__:
URL:http://www.mail-archive.com/numpy-discussion@scipy.org/msg07363.html
Cheers,
11 matches
Mail list logo
