On Mon, Jul 21, 2008 at 11:33 PM, Pierre GM [EMAIL PROTECTED] wrote:
Pierre, I suggest you go to python.org and install python-2.3.7 instead
of
shooting blind. It's pretty easy if you're running linux, just be sure to
end with make altinstall in case your distro has python installed in
On Tuesday 22 July 2008 02:06:35 Charles R Harris wrote:
But I thought Gentoo was for uber geeks? And testing the cpu cooler.
Turns out that I'm not one. It's educational, though, but the older I get, the
less compiling kernels and tweaking OS corresponds to my idea of fun.
Anyway, the tests
On Tue, Jul 22, 2008 at 12:10 AM, Pierre GM [EMAIL PROTECTED] wrote:
On Tuesday 22 July 2008 02:06:35 Charles R Harris wrote:
But I thought Gentoo was for uber geeks? And testing the cpu cooler.
Turns out that I'm not one. It's educational, though, but the older I get,
the
less compiling
On Tue, Jul 22, 2008 at 12:39 AM, Pierre GM [EMAIL PROTECTED] wrote:
On Tuesday 22 July 2008 02:27:38 Charles R Harris wrote:
Looks like you shouldn't use NumpyTestCase for the 1.2 test, however.
Looks like Alan updated it for me, the tests look OK on 1.2.
Interestingly, I segfault when
On Mon, Jul 21, 2008 at 8:40 PM, Stéfan van der Walt [EMAIL PROTECTED]
wrote:
2008/7/20 Ryan May [EMAIL PROTECTED]:
arr
array([('JOE', 25.301), ('BOB', 27.899)],
dtype=[('stid', '|S4'), ('temp', 'f8')])
The code in SVN still breaks for more complicated dtypes,
On Tuesday 22 July 2008 02:58:25 Charles R Harris wrote:
I'm testing 1.2.0.dev5497 and still see the deprecation warnings, they are
up near the beginning.
I'm afraid you have some outdated files lingering somewhere, there's no
NumpyTestCase in the sources of numpy.ma
I don't get a segfault,
On Tue, Jul 22, 2008 at 1:06 AM, Pierre GM [EMAIL PROTECTED] wrote:
On Tuesday 22 July 2008 02:58:25 Charles R Harris wrote:
I'm testing 1.2.0.dev5497 and still see the deprecation warnings, they
are
up near the beginning.
I'm afraid you have some outdated files lingering somewhere,
On Tuesday 22 July 2008 03:23:40 Charles R Harris wrote:
Looks like it's coming from linalg. Now, which one ?
This is a new thing, I take it. Looks like a good time to wait for morning
Could be on my side only with a botched dependence, but finding which one...
The deprecation warning went
2008/7/22 Charles R Harris [EMAIL PROTECTED]:
This bit is illegal syntax in Python 2.3
X.append(tuple(conv(val) for (conv, val) in zip(converterseq,
vals)))
So this isn't going to work for 1.1.1
That's easy to fix. New patch attached.
Cheers
Stéfan
loadtxt.patch
Description:
On Tue, Jul 22, 2008 at 2:45 AM, Stéfan van der Walt [EMAIL PROTECTED]
wrote:
2008/7/22 Charles R Harris [EMAIL PROTECTED]:
This bit is illegal syntax in Python 2.3
X.append(tuple(conv(val) for (conv, val) in zip(converterseq,
vals)))
So this isn't going to work for 1.1.1
2008/7/22 Charles R Harris [EMAIL PROTECTED]:
That's easy to fix. New patch attached.
Yep, but I wanted you to look it over and find all the problems ;)
Ah, you have your managerial hat on!
Could you post a patch against current mainline svn, which already has your
previous patch applied?
2008/7/22 Stéfan van der Walt [EMAIL PROTECTED]:
Could you post a patch against current mainline svn, which already has your
previous patch applied? I'm also curious why we need tuples, are we using
these values as hashes someplace.
Applied. The reason we need to use tuples is because
On Tue, Jul 22, 2008 at 9:21 AM, Stéfan van der Walt [EMAIL PROTECTED]
wrote:
2008/7/22 Stéfan van der Walt [EMAIL PROTECTED]:
Could you post a patch against current mainline svn, which already has
your
previous patch applied? I'm also curious why we need tuples, are we
using
these
On Tue, Jul 22, 2008 at 11:44 AM, Charles R Harris
[EMAIL PROTECTED] wrote:
OK, the only other change since 1.1.0 is using
np.x in the doctests, which doesn't look like a big problem. I wonder what
the status of that is in 1.1.x? Alan?
All the changes I made for that were in the trunk after
On Tue, Jul 22, 2008 at 9:58 AM, Alan McIntyre [EMAIL PROTECTED]
wrote:
On Tue, Jul 22, 2008 at 11:44 AM, Charles R Harris
[EMAIL PROTECTED] wrote:
OK, the only other change since 1.1.0 is using
np.x in the doctests, which doesn't look like a big problem. I wonder
what
the status of that
On Tuesday 22 July 2008 12:05:22 Charles R Harris wrote:
Failed importing
/usr/local/lib/python2.3/site-packages/numpy/ma/tests/test_mrecords.py:
invalid syntax (mrecords.py, line 245)
Charles,
Can you import numpy.ma.mrecords ? And we're talking about the 1.1.x branch,
right ?
On Tue, Jul 22, 2008 at 10:23 AM, Pierre GM [EMAIL PROTECTED] wrote:
On Tuesday 22 July 2008 12:05:22 Charles R Harris wrote:
Failed importing
/usr/local/lib/python2.3/site-packages/numpy/ma/tests/test_mrecords.py:
invalid syntax (mrecords.py, line 245)
Charles,
Can you import
On Tue, Jul 22, 2008 at 10:48 AM, Charles R Harris
[EMAIL PROTECTED] wrote:
On Tue, Jul 22, 2008 at 10:23 AM, Pierre GM [EMAIL PROTECTED] wrote:
On Tuesday 22 July 2008 12:05:22 Charles R Harris wrote:
Failed importing
On Tuesday 22 July 2008 12:48:20 Charles R Harris wrote:
I fixed it, Pierre. You can't do
(_[1] for _ in ddtype.descr)
to get a tuple.
OK, thx for that. AAMOF, lines 243-245 should be:
self._fill_value = np.array(tuple(fillval),
dtype=[(_[0], _[1])
On Tuesday 22 July 2008 12:56:11 Charles R Harris wrote:
Well, it produces a generator object in python2.5, which zip accepts. I
don't know in which Python version this feature was added.
Likely 2.4, as it works on my machine (else I would have found about it at one
point or another...)
On Tue, Jul 22, 2008 at 12:48 PM, Charles R Harris
[EMAIL PROTECTED] wrote:
Actually, I think this should fail in mainline also. Alan,
does nose show import failures?
I've seen talk of it swallowing some exceptions, but I'm not sure of
the specifics. Are you referring to import
On Tue, Jul 22, 2008 at 10:52 AM, Pierre GM [EMAIL PROTECTED] wrote:
On Tuesday 22 July 2008 12:48:20 Charles R Harris wrote:
I fixed it, Pierre. You can't do
(_[1] for _ in ddtype.descr)
to get a tuple.
OK, thx for that. AAMOF, lines 243-245 should be:
self._fill_value =
On Tue, Jul 22, 2008 at 11:00 AM, Pierre GM [EMAIL PROTECTED] wrote:
On Tuesday 22 July 2008 13:00:08 Alan McIntyre wrote:
I've seen talk of it swallowing some exceptions, but I'm not sure of
the specifics. Are you referring to import numpy.ma.mrecords under
Python 2.3, NumPy trunk?
On Tue, Jul 22, 2008 at 1:00 PM, Pierre GM [EMAIL PROTECTED] wrote:
On Tuesday 22 July 2008 13:00:08 Alan McIntyre wrote:
I've seen talk of it swallowing some exceptions, but I'm not sure of
the specifics. Are you referring to import numpy.ma.mrecords under
Python 2.3, NumPy trunk? Here's
On Tuesday 22 July 2008 13:06:52 Charles R Harris wrote:
I just replaced () by []. The 1.1.x version is now
dt = zip(ddtype.names, [s[1] for s in ddtype.descr])
Which should have the same effect, although not done as slickly.
Bah, that'll do for now. Many many thanks !
On Tue, Jul 22, 2008 at 10:09 AM, Alan McIntyre [EMAIL PROTECTED] wrote:
I've been told NumPy 1.2 doesn't have to support Python 2.3, so I hope
that's right. :)
Yes that's correct. NumPy 1.2 requires at least Python 2.4
--
Jarrod Millman
Computational Infrastructure for Research Labs
10
So, the following oddities remain for Python2.3 :
Failed importing numpy.f2py.lib.extgen: update() takes no keyword arguments
snip
ctypes is not available on this python: skipping the test (import error was:
ctypes is not available.)
No distutils available, skipping test.
The missing ctypes
On Tue, Jul 22, 2008 at 12:41, Charles R Harris
[EMAIL PROTECTED] wrote:
So, the following oddities remain for Python2.3 :
Failed importing numpy.f2py.lib.extgen: update() takes no keyword arguments
snip
ctypes is not available on this python: skipping the test (import error was:
ctypes is
On Tuesday 22 July 2008 13:41:04 Charles R Harris wrote:
The missing ctypes shouldn't be a problem. I don't know what to make of the
f2py import failure or if it matters.
/extgen/py_support.py:284:
parent_container_options.update(prefix='\\n\\n:Parameters:\\n\n ')
On Tue, Jul 22, 2008 at 11:46 AM, Robert Kern [EMAIL PROTECTED] wrote:
On Tue, Jul 22, 2008 at 12:41, Charles R Harris
[EMAIL PROTECTED] wrote:
So, the following oddities remain for Python2.3 :
Failed importing numpy.f2py.lib.extgen: update() takes no keyword
arguments
snip
ctypes
On Tue, Jul 22, 2008 at 12:57, Charles R Harris
[EMAIL PROTECTED] wrote:
On Tue, Jul 22, 2008 at 11:46 AM, Robert Kern [EMAIL PROTECTED] wrote:
On Tue, Jul 22, 2008 at 12:41, Charles R Harris
[EMAIL PROTECTED] wrote:
So, the following oddities remain for Python2.3 :
Failed importing
On Tue, Jul 22, 2008 at 12:03 PM, Robert Kern [EMAIL PROTECTED] wrote:
On Tue, Jul 22, 2008 at 12:57, Charles R Harris
[EMAIL PROTECTED] wrote:
On Tue, Jul 22, 2008 at 11:46 AM, Robert Kern [EMAIL PROTECTED]
wrote:
On Tue, Jul 22, 2008 at 12:41, Charles R Harris
[EMAIL PROTECTED]
On Tue, Jul 22, 2008 at 13:20, Charles R Harris
[EMAIL PROTECTED] wrote:
Although... would it be a problem to just remove the f2py stuff? That would
get rid of one confusing message.
Probably not. See r5347 and r5348 for what I had to do on the trunk.
--
Robert Kern
I have come to believe
On Tue, Jul 22, 2008 at 12:51 PM, Robert Kern [EMAIL PROTECTED] wrote:
On Tue, Jul 22, 2008 at 13:20, Charles R Harris
[EMAIL PROTECTED] wrote:
Although... would it be a problem to just remove the f2py stuff? That
would
get rid of one confusing message.
Probably not. See r5347 and
On Tue, Jul 22, 2008 at 15:07, Charles R Harris
[EMAIL PROTECTED] wrote:
On Tue, Jul 22, 2008 at 12:51 PM, Robert Kern [EMAIL PROTECTED] wrote:
On Tue, Jul 22, 2008 at 13:20, Charles R Harris
[EMAIL PROTECTED] wrote:
Although... would it be a problem to just remove the f2py stuff? That
On Tuesday 22 July 2008 17:10:57 Charles R Harris wrote:
Runs on both Python 2.5.1 and 2.3.7 here. I'll run the buildbots.
Thx a lot, I'll close the ticket.
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
On Tue, Jul 22, 2008 at 3:04 PM, Pierre GM [EMAIL PROTECTED] wrote:
On Tuesday 22 July 2008 17:10:57 Charles R Harris wrote:
Runs on both Python 2.5.1 and 2.3.7 here. I'll run the buildbots.
Thx a lot, I'll close the ticket.
Any more changes in the pipeline?
Chuck
On Tue, Jul 22, 2008 at 4:48 PM, Pierre GM [EMAIL PROTECTED] wrote:
Could anybody working on the 1.1.x branch test r5507 ? I just backported a
bugfix from 1.2, and I'd like to make sure that 1. it doesn't break anything
(I can't see why it should, but), 2. I can close the ticket (#857)
Thx a
On Tuesday 22 July 2008 17:24:27 Alan McIntyre wrote:
1.1.x runs with no errors against 2.3.7, 2.4.5, and 2.5.3 for me on Linux.
Thx Alan ! I didn't expect the fix to crash anything, but better safe than
sorry.
___
Numpy-discussion mailing list
On Tue, Jul 22, 2008 at 3:22 PM, Pierre GM [EMAIL PROTECTED] wrote:
On Tuesday 22 July 2008 17:24:27 Alan McIntyre wrote:
1.1.x runs with no errors against 2.3.7, 2.4.5, and 2.5.3 for me on
Linux.
Thx Alan ! I didn't expect the fix to crash anything, but better safe than
sorry.
_
Ryan, I committed your patch to the trunk and added a test for it from your
failing example.
Jarrod, though I'm also wary to touch the branch so late, the patch is minor
and I don't see how it could break something that was not already broken.
David
2008/7/20 Ryan May [EMAIL PROTECTED]:
On Mon, Jul 21, 2008 at 7:02 PM, David Huard [EMAIL PROTECTED] wrote:
Ryan, I committed your patch to the trunk and added a test for it from your
failing example.
Jarrod, though I'm also wary to touch the branch so late, the patch is
minor and I don't see how it could break something that
I'm in favor of putting it in. Pierre has also made some fixes to masked
arrays. I think that is about the end of it for 1.1.1. However, if anyone
is running Python 2.3 it would be helpful if you could test the release
candidate as the buildbots are all 2.4 or 2.5.
Oh yes. I don't have
2008/7/20 Ryan May [EMAIL PROTECTED]:
arr
array([('JOE', 25.301), ('BOB', 27.899)],
dtype=[('stid', '|S4'), ('temp', 'f8')])
The code in SVN still breaks for more complicated dtypes, such as:
np.dtype([('x', int), ('y', [('t', int), ('s', float)])])
Please find
On Mon, Jul 21, 2008 at 6:59 PM, Charles R Harris
[EMAIL PROTECTED] wrote:
I'm in favor of putting it in. Pierre has also made some fixes to masked
arrays. I think that is about the end of it for 1.1.1. However, if anyone is
running Python 2.3 it would be helpful if you could test the release
On Mon, Jul 21, 2008 at 8:02 PM, Pierre GM [EMAIL PROTECTED] wrote:
I'm in favor of putting it in. Pierre has also made some fixes to masked
arrays. I think that is about the end of it for 1.1.1. However, if
anyone
is running Python 2.3 it would be helpful if you could test the release
On Tuesday 22 July 2008 01:10:30 Charles R Harris wrote:
Hmm... 70 errors. Pretty much all of them of this sort:
NameError: global name 'actual_dtype' is not defined
OK, that's a problem with numpy.ma.testutils. r5496 should fix that
Pierre, I suggest you go to python.org and install
Pierre, I suggest you go to python.org and install python-2.3.7 instead of
shooting blind. It's pretty easy if you're running linux, just be sure to
end with make altinstall in case your distro has python installed in
/usr/local.
I forgot to mention that my reluctance to install another
Hello,
This is a reminder that 1.1.1rc1 will be tagged tonight. Chuck is
planning to spend some time today fixing a few final bugs on the 1.1.x
branch. If anyone else is planning to commit anything to the 1.1.x
branch today, please let me know immediately. Obviously now is not
the time to
Jarrod Millman wrote:
Hello,
This is a reminder that 1.1.1rc1 will be tagged tonight. Chuck is
planning to spend some time today fixing a few final bugs on the 1.1.x
branch. If anyone else is planning to commit anything to the 1.1.x
branch today, please let me know immediately. Obviously now
50 matches
Mail list logo
