Charles R Harris wrote:
>
> Let's announce the RC somewhere prominent on the scipy page so it gets
> more notice and testing. I didn't see any mention of the beta when I
> looked today.
Yes, you're right, I completely forgot it. On a side-note, I think the
whole release process should be more auto
Hi,
>> I found this a little confusing:
>>
>> In [11]: n = 25
>>
>> In [12]: np.arange(n).shape
>> Out[12]: (0,)
>>
>> Maybe this should raise an error instead.
>>
>> This was a little more obvious, but perhaps again a more explicit
>> error would be helpful?
>>
>> In [13]: np.zeros((n,))
On Sat, Mar 21, 2009 at 11:46 PM, Matthew Brett wrote:
> Hello,
>
> I found this a little confusing:
>
> In [11]: n = 25
>
> In [12]: np.arange(n).shape
> Out[12]: (0,)
>
> Maybe this should raise an error instead.
>
> This was a little more obvious, but perhaps again a more explicit
> err
On Sat, Mar 21, 2009 at 11:09 PM, David Cournapeau <
da...@ar.media.kyoto-u.ac.jp> wrote:
> Hi Pauli,
>
> Pauli Virtanen wrote:
> > Hi all, (esp. David)
> >
> > Is there still time for a merge from the doc wiki for 1.3.x?
> >
> > Stefan already merged several reviewed docstrings a while ago. My cu
Hello,
I found this a little confusing:
In [11]: n = 25
In [12]: np.arange(n).shape
Out[12]: (0,)
Maybe this should raise an error instead.
This was a little more obvious, but perhaps again a more explicit
error would be helpful?
In [13]: np.zeros((n,))
---
Hi Pauli,
Pauli Virtanen wrote:
> Hi all, (esp. David)
>
> Is there still time for a merge from the doc wiki for 1.3.x?
>
> Stefan already merged several reviewed docstrings a while ago. My current
> worry is that there's quite a bit good work still in there that would be
> useful to have in 1.3
Sun, 22 Mar 2009 03:14:50 +0200, Stéfan van der Walt wrote:
> Hi Pauli
>
> 2009/3/22 Pauli Virtanen :
>> Previously, I did the cherry-picking just by reading through the full
>> patch, but now I added a feature to the doc wiki that allows to
>> parallelize this:
>>
>> 1. Go to http://docs.scip
Hi Pauli
2009/3/22 Pauli Virtanen :
> Previously, I did the cherry-picking just by reading through the full
> patch, but now I added a feature to the doc wiki that allows to
> parallelize this:
>
> 1. Go to http://docs.scipy.org/numpy/patch/
> 2. Click on a link in the patch list. This shows
Hi all, (esp. David)
Is there still time for a merge from the doc wiki for 1.3.x?
Stefan already merged several reviewed docstrings a while ago. My current
worry is that there's quite a bit good work still in there that would be
useful to have in 1.3.0, but which, despite being an improvement o
jason.wool...@noaa.gov wrote:
> hi all,
>
> I'm sort of new to Numpy and I haven't had any luck with the docs or examples
> on this so I thought I would ask here. I have this small piece of code that's
> working but I'm wondering if the list really needs to be created or if this
> is an extra s
hi all,
I'm sort of new to Numpy and I haven't had any luck with the docs or examples
on this so I thought I would ask here. I have this small piece of code that's
working but I'm wondering if the list really needs to be created or if this is
an extra step that could be eliminated and speed thi
I would like to 'memoize' the objective, derivative and hessian
functions, each taking a 1d double ndarray argument X, that are passed
as arguments to
scipy.optimize.fmin_ncg.
Each of these 3 functions has calculations in common that are
expensive to compute and are a function of X. It seems fmin_
Sat, 21 Mar 2009 13:24:19 -0400, josef.pktd wrote:
> In following up on a question, I didn't find numpy testing anywhere in
> the sphinx generated docs.
>
> Since especially the asserts are useful also for other applications, it
> would be nice to have it in the help file.
>
> Where in the docs i
In following up on a question, I didn't find numpy testing anywhere in
the sphinx generated docs.
Since especially the asserts are useful also for other applications,
it would be nice to have it in the help file.
Where in the docs is it supposed to go?
Josef
_
On Sat, Mar 21, 2009 at 10:15, wrote:
>
> The testing assert functions are not well documented, I usually just
> use assert_array_almost_equal with decimal precision for float arrays.
> useful is also assert_() which is better than the assert statement
> since it survives optimization flag for py
15 matches
Mail list logo
