> A new copy of the reference guide is now available at
>
> http://mentat.za.net/numpy/refguide/
Very nice.
Will this be included in the main numpy distribution upon completion?
Thanks and appreciation for efforts.
Kind regards,
Timmie
___
Numpy-disc
Hi Jarrod,
I'm just catching up on my numpy lists and I caught this; sorry for
the late reply!
> Another issue that we should address is whether it is OK to postpone
> the planned API changes to histogram and median. A couple of people
> have mentioned to me that they would like to delay the API
On Tuesday 22 July 2008 18:25:23 Neil Crighton wrote:
> > A new copy of the reference guide is now available at
> > http://mentat.za.net/numpy/refguide/
>
> It there a reason why there's so much vertical space between all of the
> text sections? I find the docstrings much easier to read in the edi
> A new copy of the reference guide is now available at
> http://mentat.za.net/numpy/refguide/
It there a reason why there's so much vertical space between all of the text
sections? I find the docstrings much easier to read in the editor:
http://sd-2116.dedibox.fr/pydocweb/doc/numpy.core.fromnum
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.
>
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
Numpy
> Any more changes in the pipeline?
I hope not. I wasn't especially thrilled to get a ticket at the very last
minute, but this one was definitely worth fixing ASAP...
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.o
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)
> Th
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 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
http://projects.scipy.org/mailma
On Thu, Jul 17, 2008 at 2:04 PM, Matthieu Brucher <
[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've enclosed a patch for numpy.i (against the trunk). Its goal is to
> add const char*
> instead of char* in some functions (pytype_string and
> typecode_string). The char* use raises some warnings in GCC 4.2.
On Tue, Jul 22, 2008 at 2:48 PM, Pierre GM <[EMAIL PROTECTED]> wrote:
> All
> 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 (#
All
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 lot in advance !
___
Num
On Tue, Jul 22, 2008 at 2:21 PM, Pauli Virtanen <[EMAIL PROTECTED]> wrote:
> Tue, 22 Jul 2008 15:13:09 -0500, Robert Kern wrote:
>
> > On Tue, Jul 22, 2008 at 14:57, Pauli Virtanen <[EMAIL PROTECTED]> wrote:
> >> Tue, 22 Jul 2008 00:34:46 -0600, Charles R Harris wrote:
> >>>
> >>> FAIL: test_umath
On Tue, Jul 22, 2008 at 15:21, Pauli Virtanen <[EMAIL PROTECTED]> wrote:
> Tue, 22 Jul 2008 15:13:09 -0500, Robert Kern wrote:
>
>> On Tue, Jul 22, 2008 at 14:57, Pauli Virtanen <[EMAIL PROTECTED]> wrote:
>>> Tue, 22 Jul 2008 00:34:46 -0600, Charles R Harris wrote:
FAIL: test_umath.TestC9
Tue, 22 Jul 2008 15:13:09 -0500, Robert Kern wrote:
> On Tue, Jul 22, 2008 at 14:57, Pauli Virtanen <[EMAIL PROTECTED]> wrote:
>> Tue, 22 Jul 2008 00:34:46 -0600, Charles R Harris wrote:
>>>
>>> FAIL: test_umath.TestC99.test_clog(, (-0.0, -0.0), (-inf,
>>> -0.0), 'divide')
>>> AssertionError: ('(-
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 th
On Tue, Jul 22, 2008 at 14:57, Pauli Virtanen <[EMAIL PROTECTED]> wrote:
> Tue, 22 Jul 2008 00:34:46 -0600, Charles R Harris wrote:
>>
>> FAIL: test_umath.TestC99.test_clog(, (-0.0, -0.0), (-inf,
>> -0.0), 'divide')
>> AssertionError: ('(-inf, 3.1415926535897931)', '(-inf, 0.0)')
>
> The interestin
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
Tue, 22 Jul 2008 00:34:46 -0600, Charles R Harris wrote:
>
> FAIL: test_umath.TestC99.test_clog(, (-0.0, -0.0), (-inf,
> -0.0), 'divide')
> AssertionError: ('(-inf, 3.1415926535897931)', '(-inf, 0.0)')
The interesting thing is that there is no test like this
in test_umath.py. The closest thing is
I also noticed that the inverse operation, PyArray_Item_INCREF has the
potential to leak memory as it will doubly-increment each object in the
array. The solution there probably isn't quite as clean, since we can't
just mark the pointer. It will have to somehow avoid incref'ing the
objects tw
I've run into a segfault that occurs in the array destructor with arrays
containing object references with both names and titles.
When a field contains both and name and a title, the fields dictionary
contains two entries for that field. This means that the array item
destructor (which iterat
On Tue, Jul 22, 2008 at 11:20 AM, 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.
+1
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone:
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 beli
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
> >>
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 :
>>
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
>
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" ')
./extgen/py_support
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
>
> ctypes is not available on this python: skipping the test (import error was:
> ctypes
So, the following oddities remain for Python2.3 :
Failed importing numpy.f2py.lib.extgen: update() takes no keyword arguments
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 shouldn'
On Tuesday 22 July 2008 13:09:20 Alan McIntyre wrote:
> I've been told NumPy 1.2 doesn't have to support Python 2.3, so I hope
> that's right. :)
I sure do hope so...
> > If it's the 1.1.x branch, then I'm in trouble.
> > Please don't tell me I'm in trouble.
>
> No, I was just trying NumPy trunk
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 G
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 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?
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 tr
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 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 what I get:
Hold on a second, what are we taling about ?
If it's
On Tue, Jul 22, 2008 at 1:00 PM, Alan McIntyre <[EMAIL PROTECTED]> 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?
When I run numpy/numpy/ma/tests/test_mrecords.py from
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 numpy.ma.mr
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 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 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
>> > /usr/local/lib/python2.3/site-packages/numpy/ma/te
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 imp
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 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 st
On Tue, Jul 22, 2008 at 9:44 AM, Charles R Harris <[EMAIL PROTECTED]>
wrote:
>
>
> 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
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 afte
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
>
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 becau
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 ap
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 wo
I am trying to prepare for the trouble-making python3. I installed with
success python2.6b2 and then numpy1.10. scipy failed to compile with
the following error message:
compile options: '-DNO_ATLAS_INFO=1 -DUSE_VENDOR_BLAS=1
-I/usr/local/lib/python2.6/site-packages/numpy/core/include
-I/usr/loca
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
Descripti
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
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 somewhe
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 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', '
> The code in SVN still breaks for more complicated dt
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
58 matches
Mail list logo
