On Mon, Aug 4, 2008 at 20:41, Andrew Dalke <[EMAIL PROTECTED]> wrote:
> On Aug 5, 2008, at 2:00 AM, Robert Kern wrote:
>> You have old stuff in your checkout/installation. Make sure you have
>> deleted all of the *.pycs and directories which have been deleted in
>> SVN.
>
> Now that I've fixed that
On Aug 5, 2008, at 2:00 AM, Robert Kern wrote:
> You have old stuff in your checkout/installation. Make sure you have
> deleted all of the *.pycs and directories which have been deleted in
> SVN.
Now that I've fixed that, I can tell that I made a
mistake related to the self-test code. I can't fig
On Aug 5, 2008, at 2:00 AM, Robert Kern wrote:
> You have old stuff in your checkout/installation. Make sure you have
> deleted all of the *.pycs and directories which have been deleted in
> SVN.
I removed all .pyc files, wiped my installation directory, and it
works now as I expect it to work.
On Mon, Aug 4, 2008 at 18:15, Andrew Dalke <[EMAIL PROTECTED]> wrote:
> I'm working on the patches for reducing the import overhead. I want
> to make sure I don't break anything. I'm trying to figure out how to
> run all of the tests. I expected, based on the following
>
> Alan McIntyre wrote:
>
I'm working on the patches for reducing the import overhead. I want
to make sure I don't break anything. I'm trying to figure out how to
run all of the tests. I expected, based on the following
Alan McIntyre wrote:
> They actually do two different things; numpy.test() runs test for all
> of
On Mon, Aug 4, 2008 at 18:01, Christopher Barker <[EMAIL PROTECTED]> wrote:
> OK,
>
> So I'm an idiot. After reading this, I thought "I haven't rebooted for a
> while". It turns out it's been 35 days. I think I've been having slow
> startup for a longer than that, but none the less, I re-booted (wh
OK,
So I'm an idiot. After reading this, I thought "I haven't rebooted for a
while". It turns out it's been 35 days. I think I've been having slow
startup for a longer than that, but none the less, I re-booted (which
took a long time), and presto:
$ time python -c "import numpy"
real0m0.6
On Monday 04 August 2008 6:27:12 pm you wrote:
> On Monday 04 August 2008 17:53:54 you wrote:
> In my example, it is not
>
> > just that concat is stripping the units, it is returning a different
> > type.
>
> By that, you mean that the result is not a NDQuantity ? Ah.
>
> As you mentioned Travis'
svd uses 1 for its defaults:
svd(a, full_matrices=1, compute_uv=1)
Anyone interested in changing 1 to True? It shouldn't break any code, right?
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy
Hi Pierre,
On Monday 04 August 2008 04:29:57 pm Pierre GM wrote:
> On Monday 04 August 2008 14:16:33 Darren Dale wrote:
> > Hi Jarrod,
> >
> > I was wondering if someone knowledgeable would please look into the
> > behavior of concatenate() with subclasses of ndarray.
>
> Darren,
> I ran into simi
PS: is there any public C library available which would perform the same
operation?
like
void* swap(int numberDimensions,int sizeDimensions,int dataSize,int
conversionType,void* data);
where conversionType is the flag fortran to c or vice versa.
As it works for numpy, there should be some pub
Yeah, this function does the job.
Thank you very much!
-Original Message-
From: [EMAIL PROTECTED] on behalf of Stéfan van der Walt
Sent: Mon 8/4/2008 1:41 AM
To: Discussion of Numerical Python
Subject: Re: [Numpy-discussion] arrays : c aligmen to fortran and back
Hi Thomas
2008/8/4 Th
SciPy Documentation Marathon 2008 Status Report
We are now nearing the end of the summer. We have a ton of great
docstrings, a nice PDF and HTML reference guide, a new package with
pages on general topics like slicing, and a glossary.
We had hoped to have all the numpy docstrings in firs
On Monday 04 August 2008 14:16:33 Darren Dale wrote:
> Hi Jarrod,
>
> I was wondering if someone knowledgeable would please look into the
> behavior of concatenate() with subclasses of ndarray.
Darren,
I ran into similar problems when I started working on numpy.ma and
scikits.timeseries, and I r
On Mon, Aug 4, 2008 at 14:24, Christopher Barker <[EMAIL PROTECTED]> wrote:
> Robert Kern wrote:
>> It isn't. The problem is on Chris's file system.
>
> Thanks for all your help, Robert. Interestingly, I haven't noticed any
> problems anywhere else, but who knows?
>
> I guess this is what Linux Tor
On Monday 04 August 2008 13:45:51 Jarrod Millman wrote:
> Here are the remaining tasks that I am aware of that need to be done
> before tagging 1.2.0b1 on the 8th.
> The call signature for median needs to change from
> def median(a, axis=0, out=None, overwrite_input=False):
> to
> def median(a
Robert Kern wrote:
> It isn't. The problem is on Chris's file system.
Thanks for all your help, Robert. Interestingly, I haven't noticed any
problems anywhere else, but who knows?
I guess this is what Linux Torvalds meant when he said that OS-X's file
system was "brain dead"
> Whatever is wron
On Mon, Aug 4, 2008 at 13:40, Charles R Harris
<[EMAIL PROTECTED]> wrote:
>
> On Mon, Aug 4, 2008 at 1:07 PM, Pierre GM <[EMAIL PROTECTED]> wrote:
>>
>> Charles, Jarrod,
>> That isn't be a pb. I just ran into a pb with 1.2 that I know would show
>> up in
>> 1.1.x, so I just commited the changes to
On Mon, Aug 4, 2008 at 1:45 PM, Jarrod Millman <[EMAIL PROTECTED]> wrote:
> Here are the remaining tasks that I am aware of that need to be done
> before tagging 1.2.0b1 on the 8th.
>
> Median
> ==
> The call signature for median needs to change from
> def median(a, axis=0, out=None, overwrit
On Mon, Aug 4, 2008 at 1:07 PM, Pierre GM <[EMAIL PROTECTED]> wrote:
> Charles, Jarrod,
> That isn't be a pb. I just ran into a pb with 1.2 that I know would show up
> in
> 1.1.x, so I just commited the changes to the 2 versions. I was just
> wondering
> for how long I would have to backport this
On Mon, Aug 4, 2008 at 12:31 PM, Jarrod Millman <[EMAIL PROTECTED]>wrote:
> On Mon, Aug 4, 2008 at 10:17 AM, Charles R Harris
> <[EMAIL PROTECTED]> wrote:
> > I don't know what the schedule is, but if you have a bug fix it is
> probably
> > a good idea to back port it to 1.1.x so that any future
Hi Jarrod,
I was wondering if someone knowledgeable would please look into the behavior
of concatenate() with subclasses of ndarray. I posted at scipy-dev some work
on a subclass that handles units, and when two of these are concatenated, a
regular ndarray is returned rather than another instan
Charles, Jarrod,
That isn't be a pb. I just ran into a pb with 1.2 that I know would show up in
1.1.x, so I just commited the changes to the 2 versions. I was just wondering
for how long I would have to backport this kind of fixes.
> I agree with the caveat that your focus should be mostly on 1.
Here are the remaining tasks that I am aware of that need to be done
before tagging 1.2.0b1 on the 8th.
Median
==
The call signature for median needs to change from
def median(a, axis=0, out=None, overwrite_input=False):
to
def median(a, axis=None, out=None, overwrite_input=False):
in both
On Mon, Aug 4, 2008 at 10:17 AM, Charles R Harris
<[EMAIL PROTECTED]> wrote:
> I don't know what the schedule is, but if you have a bug fix it is probably
> a good idea to back port it to 1.1.x so that any future release will be
> easier. Also, if you do do the backport, put an informative comment
On Mon, Aug 4, 2008 at 10:10 AM, Jarrod Millman <[EMAIL PROTECTED]> wrote:
> Here is the current 1.2.0 schedule:
>
> - 8/08/08 tag the 1.2.0rc1 release and prepare packages
> - 8/15/08 tag the 1.2.0rc2 release and prepare packages
> - 8/23/08 tag the 1.2.0 release and prepare package
HI Pierre,
On Mon, Aug 4, 2008 at 11:49 AM, Pierre GM <[EMAIL PROTECTED]> wrote:
> All,
> * What will be the next release: 1.1.x (w/ support of Python 2.3) or 1.2.0
> (w/o support to Python 2.3) ?
> I need to correct an elusive bug in numpy.ma.MaskedArray and wondered
> whether
> I needed to back
On Mon, Aug 4, 2008 at 9:49 AM, Pierre GM <[EMAIL PROTECTED]> wrote:
> * What will be the next release: 1.1.x (w/ support of Python 2.3) or 1.2.0
> (w/o support to Python 2.3) ?
There are currently no plans for 1.1.2. Not that it won't happen;
it's just that there hasn't been any plans for the re
David, I second your approach. Furthermore, look how SWIG handles
this, it is very similar to your proposal. The difference is that SWIG
uses SWIGUNUSED for some autogenerated functions. Furthermore, it
seems the SWIG developers protected the generated code taking into
account GCC versions ;-) and
All,
* What will be the next release: 1.1.x (w/ support of Python 2.3) or 1.2.0
(w/o support to Python 2.3) ?
I need to correct an elusive bug in numpy.ma.MaskedArray and wondered whether
I needed to backport it or not (1.1.x would likely be affected as well).
Thanks a lot in advance,
P.
On Monday 04 August 2008 10:58:00 Nicolas Chopin wrote:
> Hi list,
> I want to do this:
>
> y = concatenate(x[0],x)
>
> where x is a 1d array.
> However, the only way I managed to make this work is:
>
> y = concatenate( array((x[0],),ndmin=1), x)
>
> which is kind of cryptic. (If I remove ndmin, nu
On Mon, Aug 4, 2008 at 3:58 PM, Nicolas Chopin
<[EMAIL PROTECTED]> wrote:
> Hi list,
> I want to do this:
>
> y = concatenate(x[0],x)
>
> where x is a 1d array.
> However, the only way I managed to make this work is:
>
> y = concatenate( array((x[0],),ndmin=1), x)
>
> which is kind of cryptic. (If
On Mon, Aug 4, 2008 at 09:58, Nicolas Chopin <[EMAIL PROTECTED]> wrote:
> Hi list,
> I want to do this:
>
> y = concatenate(x[0],x)
>
> where x is a 1d array.
> However, the only way I managed to make this work is:
>
> y = concatenate( array((x[0],),ndmin=1), x)
>
> which is kind of cryptic. (If I
Hi list,
I want to do this:
y = concatenate(x[0],x)
where x is a 1d array.
However, the only way I managed to make this work is:
y = concatenate( array((x[0],),ndmin=1), x)
which is kind of cryptic. (If I remove ndmin, numpy still complains.)
1. Is there a better way?
2. Would it be possib
Bruce Southey wrote:
> Hi,
> I installed the 'official binaries' on a Intel Celeron M 530 that
> supports SSE2 and SSE3 running MS Vista. All tests passed and with
> regards to the ticket: numpy.inner(F,F) resulted in 'array([[ Inf]])'
>
Ok, it looks like this is entirely due to my own stupid
Bruce Southey wrote:
> Hi,
> I installed the 'official binaries' on a Intel Celeron M 530 that
> supports SSE2 and SSE3 running MS Vista. All tests passed and with
> regards to the ticket: numpy.inner(F,F) resulted in 'array([[ Inf]])'
>
I thought that problem had be gone for good, but you're
Hi,
I installed the 'official binaries' on a Intel Celeron M 530 that
supports SSE2 and SSE3 running MS Vista. All tests passed and with
regards to the ticket: numpy.inner(F,F) resulted in 'array([[ Inf]])'
Regards
Bruce
On Sat, Aug 2, 2008 at 7:36 PM, Jarrod Millman <[EMAIL PROTECTED]> wrote:
Hi Thomas
2008/8/4 Thomas Hrabe <[EMAIL PROTECTED]>:
> I need to convert a 3d array from c alingment to fortran and was wandering
> for the simplest code available.
> Its all about python and an interfaced C++ program, which, however,
> processes fortran aligned arrays.
>
> Is there a simple code
David Cournapeau wrote:
> On Mon, 2008-08-04 at 01:50 +0200, Stéfan van der Walt wrote:
>> Just to be clear: I meant that I agree with you that we should see
>> NumPy related warnings that aren't smothered in bogus messages. Is
>> there no way to do this without compiler-specific hacks?
>
> Yes,
39 matches
Mail list logo
