Hi Chuck,
On Tue, Jul 15, 2008 at 8:41 PM, Charles R Harris
<[EMAIL PROTECTED]> wrote:
> After the second pass only a few remain. Fernando, if you don't get to these
> I'll do them tomorrow.
>
> fperez
> r5298
> r5301
> r5303
Sorry, I hadn't seen this. If you can do it that would be
After the second pass only a few remain. Fernando, if you don't get to these
I'll do them tomorrow.
fperez
r5298
r5301
r5303
Thanks to everyone for your prompt response.
Chuck
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
htt
Hi all,
A project of mine uses f2py internally to dynamically build extension
modules, and we've recently had problems with it on Windows XP using
Python 2.5.2. I think I've isolated the problem to f2py passing the --
compiler option to distutils. It appears not to be doing so.
If I run "pyt
Thanks Robert,
that is exactely what I was looking for.
Matthias
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
On Tue, Jul 15, 2008 at 21:59, Matthias Hillenbrand
<[EMAIL PROTECTED]> wrote:
> Hello,
>
> I want to calculate the root of a numpy array with negative numbers.
> Here is an example:
>
> x = linspace(-10,10,100)
> h = zeros(100)
>
> h[where(abs(x) < 2)] = sqrt( abs(x) -2 )
> h[where(2 <= abs(x))]
Hello,
I want to calculate the root of a numpy array with negative numbers.
Here is an example:
x = linspace(-10,10,100)
h = zeros(100)
h[where(abs(x) < 2)] = sqrt( abs(x) -2 )
h[where(2 <= abs(x))] = 1j * sqrt( 2 - abs(x) )
Unfortunately I get the following error: Warning: invalid value
On 15 Jul 2008, at 6:33 AM, Bruce Southey wrote:
> Hi,
> Following Travis's suggestion below, I would like to suggest that the
> following definitions be depreciated or removed in this forthcoming
> release:
>
> numpy.Inf
> numpy.Infinity
> numpy.infty
> numpy.PINF
> numpy.NAN
> numpy.NaN
...
W
Russell,
What used to be numpy.core.ma is now numpy.oldnumeric.ma, but this latter isd
no longer supported and will disappear soon as well. Just use numpy.ma
If you really need support to ancient versions of numpy, just check the import
try:
import numpy.core.ma as ma
except ImportError:
i
I have some code that does this:
# an extra array cast is used because "compressed" returns what *looks*
like an array
# but is actually something else (I'm not sure exactly what)
unmaskedArr = numpy.array(
numpy.core.ma.array(
dataArr,
mask = mask & self.stretchExcludeBits,
Christopher Barker wrote:
> Jarrod Millman wrote:
>
>> On Tue, Jul 15, 2008 at 6:33 AM, Bruce Southey <[EMAIL PROTECTED]> wrote:
>>
>>> Following Travis's suggestion below, I would like to suggest that the
>>> following definitions be depreciated or removed in this forthcoming release:
>>>
On Tue, Jul 15, 2008 at 09:59, Charles R Harris
<[EMAIL PROTECTED]> wrote:
>
> On Tue, Jul 15, 2008 at 1:42 AM, Michael Abbott <[EMAIL PROTECTED]>
> wrote:
>>
>> I'm reviewing my tickets (seems a good thing to do with a release
>> imminent), and I'll post up each ticket that merits comment as a sep
Jarrod Millman wrote:
> On Tue, Jul 15, 2008 at 6:33 AM, Bruce Southey <[EMAIL PROTECTED]> wrote:
>> Following Travis's suggestion below, I would like to suggest that the
>> following definitions be depreciated or removed in this forthcoming release:
>>
>> numpy.Inf
>> numpy.Infinity
>> numpy.infty
On Tue, Jul 15, 2008 at 6:33 AM, Bruce Southey <[EMAIL PROTECTED]> wrote:
> Following Travis's suggestion below, I would like to suggest that the
> following definitions be depreciated or removed in this forthcoming release:
>
> numpy.Inf
> numpy.Infinity
> numpy.infty
> numpy.PINF
> numpy.NAN
> nu
On Tue, Jul 15, 2008 at 11:10 AM, Charles Doutriaux <[EMAIL PROTECTED]>
wrote:
> Hi I have a quick question and i hope somebody can answer me (I admit I
> should first really check the numpy doc)
>
> I have been porting old Numeric based C code to numpy/numpy.ma for the
> alst couple weeks.
>
> Ju
Hi I have a quick question and i hope somebody can answer me (I admit I
should first really check the numpy doc)
I have been porting old Numeric based C code to numpy/numpy.ma for the
alst couple weeks.
Just as I thought I was done, this morning I updatethe numpy trunk and I
now get the follow
On Tue, Jul 15, 2008 at 10:26 AM, David Huard <[EMAIL PROTECTED]> wrote:
> The revision number for the backport of 5254 is 5419.
>
Great, thanks.
Chuck
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listi
The revision number for the backport of 5254 is 5419.
David
2008/7/15 Charles R Harris <[EMAIL PROTECTED]>:
> After the first round of backports the following remain.
>
> charris
> r5259
> r5312
> r5322
> r5324
> r5392
> r5394
> r5399
> r5406
> r5407
>
> dhuar
2008/7/15 Francesc Alted <[EMAIL PROTECTED]>:
> Maybe is only that. But by using the term 'frequency' I tend to think
> that you are expecting to have one entry (observation) in your array
> for each time 'tick' since time start. OTOH, the term 'resolution'
> doesn't have this implication, and o
On Tuesday 15 July 2008 07:30:09 Francesc Alted wrote:
> Maybe is only that. But by using the term 'frequency' I tend to think
> that you are expecting to have one entry (observation) in your array
> for each time 'tick' since time start. OTOH, the term 'resolution'
> doesn't have this implicatio
On Tue, 15 Jul 2008, Michael Abbott wrote:
> Only half of my patch for this bug has gone into trunk, and without the
> rest of my patch there remains a leak.
I think I might need to explain a little more about the reason for this
patch, because obviously the bug it fixes was missed the last time
On Tue, Jul 15, 2008 at 1:42 AM, Michael Abbott <[EMAIL PROTECTED]>
wrote:
> I'm reviewing my tickets (seems a good thing to do with a release
> imminent), and I'll post up each ticket that merits comment as a separate
> message.
>
> Ticket #843 has gone into trunk (commit 5361, oliphant) ... but
After the first round of backports the following remain.
charris
r5259
r5312
r5322
r5324
r5392
r5394
r5399
r5406
r5407
dhuard
r5254
fperez
r5298
r5301
r5303
oliphant
r5245
r5255
Chuck
___
Nu
On Mon, Jul 14, 2008 at 12:34 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
> We're not doing anything special, here. When I install using "sudo
> python install.py" on OS X, all of the permissions are 644. I think
> the problem may be in your pipeline.
With a little more testing, what I am finding
Hi,
Following Travis's suggestion below, I would like to suggest that the
following definitions be depreciated or removed in this forthcoming release:
numpy.Inf
numpy.Infinity
numpy.infty
numpy.PINF
numpy.NAN
numpy.NaN
I am not sure about what would be best for numpy.NINF.
Thanks
Bruce
Trav
On Tue, Jul 15, 2008 at 1:47 AM, Pauli Virtanen <[EMAIL PROTECTED]> wrote:
> Mon, 14 Jul 2008 18:05:27 -0600, Charles R Harris wrote:
> > All,
> >
> > The rc release of numpy-1.1.1 is due out next Sunday. I have gone
> > through the commits made to the trunk since the 1.1.x branch to pull out
> >
On Tue, Jul 15, 2008 at 1:24 AM, Stéfan van der Walt <[EMAIL PROTECTED]>
wrote:
> 2008/7/15 Charles R Harris <[EMAIL PROTECTED]>:
> > Stefan, these are mostly documentation related. IIRC, you planned to
> update
> > the documentation in 1.1.1, which probably also needs ptvirtan's commit
> > above.
On Mon, Jul 14, 2008 at 10:16 PM, Alan McIntyre <[EMAIL PROTECTED]>
wrote:
> On Mon, Jul 14, 2008 at 8:21 PM, Pierre GM <[EMAIL PROTECTED]> wrote:
> > I did as much as I could to ensure compatibility with Python 2.3, but I
> can't
> > test it myself (can't install Python 2.3 on my machine). It'd b
On Mon, Jul 14, 2008 at 6:21 PM, Pierre GM <[EMAIL PROTECTED]> wrote:
> > Pierre, I know you have been working diligently to get masked arrays up
> to
> > speed and have made numerous fixes in the 1.1.x branch. All the tests
> pass
> > for me. Is there more that needs to be done?
>
> Charles,
> I
On Tue, Jul 15, 2008 at 2:15 AM, David Cournapeau <[EMAIL PROTECTED]>
wrote:
> On Tue, Jul 15, 2008 at 2:05 AM, Charles R Harris
> <[EMAIL PROTECTED]> wrote:
> > All,
> >
> > The rc release of numpy-1.1.1 is due out next Sunday. I have gone through
> > the commits made to the trunk since the 1.1.x
On Tue, Jul 15, 2008 at 2:12 AM, Robert Kern <[EMAIL PROTECTED]> wrote:
> On Mon, Jul 14, 2008 at 19:05, Charles R Harris
> <[EMAIL PROTECTED]> wrote:
> > rkern
> > r5296
> > r5297
> > r5342
> > r5349
> > r5357
>
> Done.
>
Thanks,
Chuck
___
A Monday 14 July 2008, Pierre GM escrigué:
> Francesc, Chris, may I suggest you to try TimeSeries if you didn't
> already ? That way you could see what kind of features are missing
> and which ones should be improved with the new dtype ?
I'm having a look at your package, and I see that you have i
A Monday 14 July 2008, Pierre GM escrigué:
> On Monday 14 July 2008 14:17:18 Francesc Alted wrote:
> > Well, what we are after is precisely this: a new dtype type. After
> > integrating it in NumPy, I suppose that your DateArray would be
> > similar than a NumPy array with a dtype ``datetime64`` (
A Monday 14 July 2008, Pierre GM escrigué:
> On Monday 14 July 2008 15:12:18 Francesc Alted wrote:
> > I see. However, the more I think about this, the more I see the
> > need to split the date/time functionalities and duties in two
> > parts:
> >
> > * the first one implementing a date/time dtype
On Tue, Jul 15, 2008 at 2:05 AM, Charles R Harris
<[EMAIL PROTECTED]> wrote:
> All,
>
> The rc release of numpy-1.1.1 is due out next Sunday. I have gone through
> the commits made to the trunk since the 1.1.x branch to pull out backport
> candidates. If you find your name here could you make the b
On Mon, Jul 14, 2008 at 19:05, Charles R Harris
<[EMAIL PROTECTED]> wrote:
> rkern
> r5296
> r5297
> r5342
> r5349
> r5357
Done.
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless
enigma that is made terrible by our own mad attempt to interp
Tenuous but easy fix, and conformant to style elsewhere.
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
This one is easy, ought to go in. Fixes a (not particularly likely)
memory leak.
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
Only half of my patch for this bug has gone into trunk, and without the
rest of my patch there remains a leak.
Furthermore, it remains necessary to perform an extra INCREF on typecode
before calling PyArray_FromAny ... as otherwise there is the real
possibility that typecode will have evaporate
Mon, 14 Jul 2008 18:05:27 -0600, Charles R Harris wrote:
> All,
>
> The rc release of numpy-1.1.1 is due out next Sunday. I have gone
> through the commits made to the trunk since the 1.1.x branch to pull out
> backport candidates. If you find your name here could you make the
> backport or say wh
I'm reviewing my tickets (seems a good thing to do with a release
imminent), and I'll post up each ticket that merits comment as a separate
message.
Ticket #843 has gone into trunk (commit 5361, oliphant) ... but your
editor appears to be introducing hard tabs! Hard tab characters are
fortuna
2008/7/15 Charles R Harris <[EMAIL PROTECTED]>:
> Stefan, these are mostly documentation related. IIRC, you planned to update
> the documentation in 1.1.1, which probably also needs ptvirtan's commit
> above. What is the current status of this project?
The plan was to include the documentation as
41 matches
Mail list logo
