Hi all,
You probably remember that I said that after numpy 1.7.0 was out I wanted
to step down as release manager for NumPy and focus more on SciPy. That was
4.5 months ago, and now that 1.7.0 keeps being postponed I'm actually
planning to not wait for it. I have found that it's not possible for
Hi,
may I suggest an addition to the release process...
'Tests against popular libraries that rely on numpy at the RC stage.
Test at least these libraries pass their numpy related tests:
matplotlib, scipy, pygame, (insert others here?). The release manage
should ask the mailing list for people
On Sat, Feb 6, 2010 at 6:44 PM, René Dudfield ren...@gmail.com wrote:
Hi,
may I suggest an addition to the release process...
'Tests against popular libraries that rely on numpy at the RC stage.
Test at least these libraries pass their numpy related tests:
matplotlib, scipy, pygame,
2008/4/25 Alan G Isaac [EMAIL PROTECTED]:
2008/4/25 Alan G Isaac :
So, if X is 2 by 2, then X[0] will be a row vector.
But if X is 1 by 2, then X[0] will be a scalar?
Ouch!
Bye bye generic code.
On Fri, 25 Apr 2008, Stefan van der Walt apparently wrote:
Yup. That's the
I think the use of the term 'vector' in this
thread is becoming a bit confusing.
An M by N matrix is a vector. (I.e., it is
an element of a vector space.)
Many people use the terms row vector and column
vector to refer to special matrices. What is
special is *not* that they are vectors (since
On Fri, 25 Apr 2008, Stéfan van der Walt apparently wrote:
In current SVN:
In [6]: x[0]
Out[6]: matrix([[0, 1, 2]])
I must have misunderstood:
I thought the agreement was to
provisionally return a 1d array for x[0],
while we hashed through the other proposals.
Cheers,
Alan
2008/4/25 Alan G Isaac [EMAIL PROTECTED]:
I must have misunderstood:
I thought the agreement was to
provisionally return a 1d array for x[0],
while we hashed through the other proposals.
The agreement was:
a) That x[0][0] should be equal to x[0,0] and
b) That x[0,:] should be equal to
On 25/04/2008, Stéfan van der Walt [EMAIL PROTECTED] wrote:
2008/4/25 Alan G Isaac [EMAIL PROTECTED]:
I must have misunderstood:
I thought the agreement was to
provisionally return a 1d array for x[0],
while we hashed through the other proposals.
The agreement was:
a) That
On Fri, Apr 25, 2008 at 10:04 AM, Alan G Isaac [EMAIL PROTECTED] wrote:
I think the use of the term 'vector' in this
thread is becoming a bit confusing.
An M by N matrix is a vector. (I.e., it is
an element of a vector space.)
Sure, but the important thing is the multiplication. If it
Anne Archibald wrote:
Yes, well, it really looks unlikely we will be able to agree on what
the correct solution is before 1.1, so I would like to have something
non-broken for that release.
+1 on that!
___
Numpy-discussion mailing list
I was hoping to get NumPy 1.1 tagged today, but it seems very unlikely
at this point. Unfortunately, I haven't followed the matrix
discussion as closely as I would like, so I can't tell if there is
anything so uncontroversial that it would make sense to change for the
1.1.0 release. If there is
2008/4/25 Stéfan van der Walt [EMAIL PROTECTED]:
I'm starting to see Chris Barker's point; allowing x[0] is causing
more problems than it is worth. On the other hand, how would you
index into a vector (as in
http://en.wikipedia.org/wiki/Vector_(spatial)) without it?
To answer my own
2008/4/24 Jarrod Millman [EMAIL PROTECTED]:
On Thu, Apr 24, 2008 at 1:22 PM, David Huard wrote:
Assuming we want the next version to : ignore values outside of range
and
accept and return the bin edges instead of the left edges, here could be
the
new signature for 1.1:
h, edges =
2008/4/25 David Huard [EMAIL PROTECTED]:
2008/4/24 Jarrod Millman [EMAIL PROTECTED]:
On Thu, Apr 24, 2008 at 1:22 PM, David Huard wrote:
Assuming we want the next version to : ignore values outside of range
and
accept and return the bin edges instead of the left edges, here could
Thanks Chuck,
I didn't know there were other tests for histogram outside of
test_function_base.
The error is now raised only if bins are passed explicitly and normed=True.
David
2008/4/25 Charles R Harris [EMAIL PROTECTED]:
On Fri, Apr 25, 2008 at 12:55 PM, Jarrod Millman [EMAIL PROTECTED]
that demonstrates an
alternative.
Nadav.
-הודעה מקורית-
מאת: [EMAIL PROTECTED] בשם St?fan van der Walt
נשלח: ה 24-אפריל-08 13:13
אל: Discussion of Numerical Python
נושא: Re: [Numpy-discussion] numpy release
2008/4/24 Nadav Horesh [EMAIL PROTECTED]:
+1
+1 to what? I'm glad that Tim chimed
Wed, 23 Apr 2008 16:20:41 -0400, David Huard wrote:
2008/4/23, Stéfan van der Walt [EMAIL PROTECTED]:
Of those tickets, the following are serious:
http://projects.scipy.org/scipy/numpy/ticket/605 (a patch is
available?, David Huard)
Fixing of histogram.
I haven't found a way to fix
I think a long term strategy needs to be adopted for histogram.
Right now there is a great confusion in what the bins keyword
does. Right now it is defined as the lower edge of each bin, meaning
that the last bin is open ended and [inf,bin0 does not exist. While
this may not be the right thing to
The problem I see with C is that it will break compatibility with the other
histogram functions, which also use bins.
So here is suggestion E:
The most common use case ( I think) is the following:
h, b = histogram(r, number_of_bins, normed=True/False) for which the
function behaves correctly.
On Wed, 23 Apr 2008, Timothy Hochberg apparently wrote:
I think the way to go is to probably add some meta
information
I have added this as Proposal 4 at
URL:http://www.scipy.org/MatrixIndexing
Forgive anything said the misrepresents your intent.
Cheers,
Alan
2008/4/25 Alan G Isaac [EMAIL PROTECTED]:
So, if X is 2 by 2, then X[0] will be a row vector.
But if X is 1 by 2, then X[0] will be a scalar?
Ouch!
Bye bye generic code.
Yup. That's the current state of things.
Stéfan
___
Numpy-discussion
On Thu, Apr 24, 2008 at 11:16 AM, Timothy Hochberg
[EMAIL PROTECTED] wrote:
[CHOP]
The proposals thus far don't address two of the major issues I have with the
matrix class:
The thing that seems missing to me is support for LAPACK's banded and
packed (triangular) storage formats. I don't
On Fri, Apr 25, 2008 at 10:23 AM, Christopher Barker
[EMAIL PROTECTED] wrote:
Alan G Isaac wrote:
On Thu, 24 Apr 2008, Christopher Barker apparently wrote:
I suppose a Vector can be either a (n,1) or a (1,n)
matrix that allows single indexing.
This bothers me.
So, if X is 2
2008/4/23 Ondrej Certik [EMAIL PROTECTED]:
What is the plan with the release? There are some minor problems in
the Debian package, some of which are fixed by the new release.
I didn't fix those in Debian as I thought the new release is coming
out. But if it's going to take let's say month
On Wed, Apr 23, 2008 at 6:21 AM, Stéfan van der Walt [EMAIL PROTECTED] wrote:
The question is: what blocks the release of 1.1? The following
tickets deserve attention:
http://projects.scipy.org/scipy/numpy/ticket/750
http://projects.scipy.org/scipy/numpy/ticket/605
Hi Jarrod
Of those tickets, the following are serious:
http://projects.scipy.org/scipy/numpy/ticket/605 (a patch is
available?, David Huard)
Fixing of histogram.
http://projects.scipy.org/scipy/numpy/ticket/551 (old regression,
Chuck and Travis)
Unpickled arrays don't work as expected,
On 23/04/2008, Alan Isaac [EMAIL PROTECTED] wrote:
On Wed, 23 Apr 2008, Sebastian Haase wrote:
What used to be referred to a the 1.1 version, that can
break more stuff, to allow for a cleaner design, will now
be 1.2
So ... fixing x[0][0] for matrices should wait
until 1.2. Is that
On Wed, Apr 23, 2008 at 11:32 AM, Anne Archibald
[EMAIL PROTECTED] wrote:
So ... fixing x[0][0] for matrices should wait
until 1.2. Is that correct?
It seems to me that everyone agrees that the current situation is
broken, but there is considerable disagreement on what the correct fix
2008/4/23, Stéfan van der Walt [EMAIL PROTECTED]:
Hi Jarrod
Of those tickets, the following are serious:
http://projects.scipy.org/scipy/numpy/ticket/605 (a patch is
available?, David Huard)
Fixing of histogram.
I haven't found a way to fix histogram reliably without breaking the
On Wed, 23 Apr 2008, Stéfan van der Walt wrote:
Done in r5072.
Much appreciated.
I have updated URL:http://www.scipy.org/MatrixIndexing
to reflect this change (and its provisional status).
Alan
___
Numpy-discussion mailing list
Alan Isaac wrote:
I have updated URL:http://www.scipy.org/MatrixIndexing
to reflect this change (and its provisional status).
Thanks for writing this up -- it really clarifies what's being proposed.
A few comments on that write up:
For matrix x, should x[0].A[0] == x.A[0][0]? That is,
2008/4/23 Christopher Barker [EMAIL PROTECTED]:
Aside from the fact that someone needs to write the code -- why don't
people like the row/column vector idea? It just feels so natural to me:
I wrote most of the code last week (see the previous thread on the
mailing list for a patch). It
[CHOP]
The proposals thus far don't address two of the major issues I have with the
matrix class:
1. The matrices and arrays should become more alike if possible and
should share more of the same code base. From what I've seen, the people who
write the code (for numpy) don't actually
Hi Jarrod,
any news with the 1.0.5? If you have same prerelease, I'd like to test
it. Debian has just moved from python2.4 to python2.5 yesterday, so
I'd like to test numpy in advance, I am sure there will be some issues
to fix.
Ondrej
___
34 matches
Mail list logo
