Please do not respond to digest messages. If you want to respond to
messages, subscribe to receive messages individually. Respond to the
just messages you are interested in and keep the Subject lines intact.
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless
eni
> Absolutely. Let's please standardize on:
> import numpy as np
> import scipy as sp
I hope we do NOT standardize on these abbreviations. While a few may
have discussed it at a sprint, it hasn't seen broad discussion and
there are reasons to prefer the other practice (numpy as N, scipy as
S, pyl
Hi Chris
On 09/04/2008, Christopher Barker <[EMAIL PROTECTED]> wrote:
> I have yet to advocate that the Matlab users in my group (The Scientists
> that happen to need a bit of programming, but have no interest in it)
> start using Python, but, frankly, "import *", and minor syntax like that
>
> And I'll say the thing I'm dying to say since this started: If anybody
> other than Travis had suggested we put financial functions in numpy
> the response would have been: make it a scikit, let the functions
> mature and evolve, get some feedback from users and then we'll see
> where they f
On Mittwoch 09 April 2008, Charles R Harris wrote:
> import numpy.linalg as la ?
Yes! :)
Andreas
signature.asc
Description: This is a digitally signed message part.
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org
On Wed, Apr 9, 2008 at 4:57 PM, Jarrod Millman <[EMAIL PROTECTED]> wrote:
> On Wed, Apr 9, 2008 at 11:27 AM, Christopher Barker
> <[EMAIL PROTECTED]> wrote:
> > except that the beginner, nor anyone else, should ever use "import *"
> > anyway!
>
> +1
>
> > "Namespaces are one honking great idea
On Wed, Apr 9, 2008 at 3:57 PM, Jarrod Millman <[EMAIL PROTECTED]> wrote:
> Absolutely. Let's please standardize on:
> import numpy as np
> import scipy as sp
>
> See:
> http://projects.scipy.org/scipy/numpy/wiki/CodingStyleGuidelines
> http://svn.scipy.org/svn/numpy/trunk/numpy/doc/example
On Wed, Apr 9, 2008 at 11:27 AM, Christopher Barker
<[EMAIL PROTECTED]> wrote:
> except that the beginner, nor anyone else, should ever use "import *"
> anyway!
+1
> "Namespaces are one honking great idea -- let's do more of those!"
>
> That's "more", not "fewer"
Agreed.
> I really don't g
Gael Varoquaux wrote:
>> the beginner, nor anyone else, should ever use "import *"
>
> Right! Sure. Tell this to a medical doctor who just wants to learn as
> little things as possible about a computer in order to process his MRI
> data and finish his PhD to never have to worry anymore with stupi
On Wed, Apr 9, 2008 at 4:11 AM, Jarrod Millman <[EMAIL PROTECTED]> wrote:
> Hello Robert Kern (or some else who wants to take this).
>
> This one has a patch:
> http://projects.scipy.org/scipy/numpy/ticket/581
>
> Can you verify that it is safe/correct and commit it?
Fixed, along with a couple
On Wed, Apr 09, 2008 at 04:18:41PM -0400, David Huard wrote:
>And that's what Matlab is especially good at ! ; )
Exactly. I would like to have the same ease of use for beginners than
Matlab. The reason being that _I_ would be able develop my own module using the
powerful feature of Python, but
2008/4/9, Gael Varoquaux <[EMAIL PROTECTED]>:
>
> [snip]
>
> Some people do not want their scripts to scale or to last more than a day.
And that's what Matlab is especially good at ! ; )
And I'll say the thing I'm dying to say since this started: If anybody other
than Travis had suggested we put
On Wed, Apr 09, 2008 at 11:27:04AM -0700, Christopher Barker wrote:
> Gael Varoquaux wrote:
> > For the beginner, "from numpy.all import *" is more confusing than "from
> > numpy import *" (which is already confusing).
> except that the beginner, nor anyone else, should ever use "import *"
> anyw
Sorry to be late on this thread, but I was out of town, and I do feel
strongly about this issue.
Gael Varoquaux wrote:
> For the beginner, "from numpy.all import *" is more confusing than "from
> numpy import *" (which is already confusing).
except that the beginner, nor anyone else, should ever
Hi Chuck, all,
On Mittwoch 09 April 2008, Charles R Harris wrote:
> It would affect polyfit, where the powers correspond to the numpy
> polynomial coefficients. That can be fixed, and as far as I can determine
> that is the only numpy function that uses vander, but it might break some
> software o
On Wed, 9 Apr 2008, Charles R Harris wrote:
> It would affect polyfit, where the powers correspond to
> the numpy polynomial coefficients. That can be fixed, and
> as far as I can determine that is the only numpy function
> that uses vander, but it might break some software out
> there in the w
On Wed, 9 Apr 2008, Rich Shepard wrote:
> ... and I'm wondering if there's a way within NumPy to multiply these
> values by 100 and limit the precision to 4 significant digits
Got it all worked out. All resolved.
Rich
___
Numpy-discussion mailing li
On Wed, Apr 9, 2008 at 11:07 AM, Stéfan van der Walt <[EMAIL PROTECTED]>
wrote:
> On 09/04/2008, Andreas Klöckner <[EMAIL PROTECTED]> wrote:
> > On Mittwoch 26 März 2008, Charles R Harris wrote:
> > > The docstring is incorrect. The Vandermonde matrix produced is
> compatible
> > > with numpy po
On Wed, Apr 9, 2008 at 7:01 AM, David Huard <[EMAIL PROTECTED]> wrote:
> Hello Jarrod and co.,
>
> here is my personal version of the histogram saga.
>
> The current version of histogram puts in the rightmost bin all values
> larger than range, but does not put in the leftmost bin all values small
On 09/04/2008, Andreas Klöckner <[EMAIL PROTECTED]> wrote:
> On Mittwoch 26 März 2008, Charles R Harris wrote:
> > The docstring is incorrect. The Vandermonde matrix produced is compatible
> > with numpy polynomials that also go from high to low powers. I would have
> > done it the other way rou
I'm using linalg.eig() and it works exactly as intended. The values of
the principal eigenvector are presented as real numbers (e.g.,
0.159317312615085), and I'm wondering if there's a way within NumPy to
multiply these values by 100 and limit the precision to 4 significant digits
(e.g., 15.93).
Sorry, I can answer my own question (page 22 of numpy book) booleans are
supposed to be "?" my mistake.
C.
Charles Doutriaux wrote:
> Hi I'm tracked down a bug in our code back to the numpy.ma
>
> s2=numpy.array([[10,60],[65,45]])
> s3=numpy.ma.masked_greater(s2,50.)
> s3.mask.dtype.char
> retur
Hi I'm tracked down a bug in our code back to the numpy.ma
s2=numpy.array([[10,60],[65,45]])
s3=numpy.ma.masked_greater(s2,50.)
s3.mask.dtype.char
returns: '?'
In the Numeric -> numpy.ma (page 35) the "?" is not listed. Is it an
omission in numpy.ma ? Or is it a valid char type ?
s3.dtype does s
On Mittwoch 26 März 2008, Charles R Harris wrote:
> The docstring is incorrect. The Vandermonde matrix produced is compatible
> with numpy polynomials that also go from high to low powers. I would have
> done it the other way round, so index matched power, but that isn't how it
> is.
Patch attache
Hi,
I should have asked first (I hope that you don't mind), but I created a
ticket Ticket #728 (http://scipy.org/scipy/numpy/ticket/728 ) for
numpy.r_ because this incorrectly casts based on the array types.
The bug is that -inf and inf are numpy floats but dbin is an array of
ints. Unfortunate
Hello Jarrod and co.,
here is my personal version of the histogram saga.
The current version of histogram puts in the rightmost bin all values larger
than range, but does not put in the leftmost bin all values smaller than
bin, eg.
In [6]: histogram([1,2,3,4,5,6], bins=3, range=[2,5])
Out[6]: (a
Jarrod Millman wrote:
> Hello,
>
> I just turned this one into a blocker for now. There has been a very
> long and good discussion about this ticket:
> http://projects.scipy.org/scipy/numpy/ticket/605
>
> Could someone (David?, Bruce?) briefly summarize the problem and the
> current proposed solut
Unfortunately, I couldn't get this patch to work, and my time has run
out. Maybe someone with more knowledge the precedences/order of
functions during linking can take a look. I don't know how to tell
the system BLAS to call our custom xerbla, instead of the one
provided.
The patch addresses an
On 09/04/2008, Pearu Peterson <[EMAIL PROTECTED]> wrote:
> On Wed, April 9, 2008 2:13 pm, Jarrod Millman wrote:
> > Hey Pearu,
> >
> > Could you take a quick look at this:
> > http://projects.scipy.org/scipy/numpy/ticket/587
>
>
> I have fixed it in r4996.
>
> However, when trying to change th
On Wed, April 9, 2008 3:25 pm, Jarrod Millman wrote:
> On Wed, Apr 9, 2008 at 4:59 AM, Pearu Peterson <[EMAIL PROTECTED]> wrote:
>> I have fixed it in r4996.
>
> Thanks,
>
>> However, when trying to change the ticked status, I get forbidden
>> error:
>>
>> TICKET_APPEND privileges are required t
Thus far, none have been added.
On 09/04/2008, Jarrod Millman <[EMAIL PROTECTED]> wrote:
> Have sufficient tests been added to close this:
> http://projects.scipy.org/scipy/numpy/ticket/719
>
> Travis -- Are you planning to add more?
___
Numpy-discussi
I'm busy working on this one. Can't get the patch working as
advertised, yet, so I'm wondering if lapack_lite is preferring some
other xerbla over the one provided.
On 09/04/2008, Jarrod Millman <[EMAIL PROTECTED]> wrote:
> This has a patch:
> http://projects.scipy.org/scipy/numpy/ticket/673
>
>
On Wed, Apr 9, 2008 at 4:04 AM, Jarrod Millman <[EMAIL PROTECTED]> wrote:
> The NumPy 1.0.5 release is fast approaching! There are currently 109
> closed tickets and just 19 open ones:
> http://projects.scipy.org/scipy/numpy/milestone/1.0.5
We are now at: 111 closed tickets and 17 open! Keep
On Wed, Apr 9, 2008 at 4:59 AM, Pearu Peterson <[EMAIL PROTECTED]> wrote:
> I have fixed it in r4996.
Thanks,
> However, when trying to change the ticked status, I get forbidden error:
>
> TICKET_APPEND privileges are required to perform this operation
>
> Could track admins add required priv
This code can probably be incorporated into NumPy in the 1.1
timeframe. I don't think anyone is going to miss it before then.
On Wed, Apr 9, 2008 at 2:04 PM, Jarrod Millman <[EMAIL PROTECTED]> wrote:
> This ticket has a patch:
> http://projects.scipy.org/scipy/numpy/ticket/655
>
> --
> Jarrod M
This ticket has a patch:
http://projects.scipy.org/scipy/numpy/ticket/655
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
___
Numpy-discussion mailing list
Nump
On Wed, April 9, 2008 2:13 pm, Jarrod Millman wrote:
> Hey Pearu,
>
> Could you take a quick look at this:
> http://projects.scipy.org/scipy/numpy/ticket/587
I have fixed it in r4996.
However, when trying to change the ticked status, I get forbidden error:
TICKET_APPEND privileges are required t
Have sufficient tests been added to close this:
http://projects.scipy.org/scipy/numpy/ticket/719
Travis -- Are you planning to add more?
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
__
http://projects.scipy.org/scipy/numpy/ticket/693
Could someone add a test for this changeset:
http://projects.scipy.org/scipy/numpy/changeset/4826
Thanks,
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
This has a patch:
http://projects.scipy.org/scipy/numpy/ticket/673
Could someone review, comment or commit?
Thanks,
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
__
This has a patch:
http://projects.scipy.org/scipy/numpy/ticket/663
Could someone review and commit it?
Thanks,
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
___
Hello,
I just turned this one into a blocker for now. There has been a very
long and good discussion about this ticket:
http://projects.scipy.org/scipy/numpy/ticket/605
Could someone (David?, Bruce?) briefly summarize the problem and the
current proposed solution for us again? Let's agree on th
Hey Pearu,
Could you take a quick look at this:
http://projects.scipy.org/scipy/numpy/ticket/587
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
___
Numpy-disc
Hello Robert Kern (or some else who wants to take this).
This one has a patch:
http://projects.scipy.org/scipy/numpy/ticket/581
Can you verify that it is safe/correct and commit it?
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.401
This could possibly be a regression:
http://scipy.org/scipy/numpy/ticket/539
Can someone verify that these now work?
--
Jarrod Millman
Computational Infrastructure for Research Labs
10 Giannini Hall, UC Berkeley
phone: 510.643.4014
http://cirl.berkeley.edu/
__
Hello,
The NumPy 1.0.5 release is fast approaching! There are currently 109
closed tickets and just 19 open ones:
http://projects.scipy.org/scipy/numpy/milestone/1.0.5
The amount of code cleanup, fixes, documentation, and new tests added
over the last month is just phenomenal. With just a few d
A Wednesday 09 April 2008, Stéfan van der Walt escrigué:
> On 09/04/2008, Francesc Altet <[EMAIL PROTECTED]> wrote:
> > Well, I agree that Greg Ewing (the Pyrex creator) has possibly not
> > been very speedy in adding the suggested patches (Greg has his own
> > thoughts on what should be added to
On Wed, Apr 9, 2008 at 1:22 AM, Francesc Altet <[EMAIL PROTECTED]> wrote:
> Well, I agree that Greg Ewing (the Pyrex creator) has possibly not been
> very speedy in adding the suggested patches (Greg has his own thoughts
> on what should be added to Pyrex and what not), which ultimately
> broug
On 09/04/2008, Francesc Altet <[EMAIL PROTECTED]> wrote:
> Well, I agree that Greg Ewing (the Pyrex creator) has possibly not been
> very speedy in adding the suggested patches (Greg has his own thoughts
> on what should be added to Pyrex and what not), which ultimately
> brought to the need of
Am Dienstag, 08. April 2008 17:22:33 schrieb Ken Basye:
> I've had this happen
> often enough that I found the first thing I did when an output
> difference arose was to print the FP in hex to see if the
> difference was "real" or just a formatting artifact.
Nice idea - is that code available some
A Wednesday 09 April 2008, Fernando Perez escrigué:
> On Wed, Apr 9, 2008 at 12:25 AM, Francesc Altet <[EMAIL PROTECTED]>
wrote:
> > I don't expect you having problems in that regard either.
> > However, I've been having problems compiling perfectly valid Pyrex
> > code with the Cython compiler.
On Wed, Apr 9, 2008 at 12:49 AM, Robert Kern <[EMAIL PROTECTED]> wrote:
> On Wed, Apr 9, 2008 at 2:47 AM, Fernando Perez <[EMAIL PROTECTED]> wrote:
> > I'll be happy to leave it as a new trac ticket with an attachment for
> > it if it will make the testing/review process easier in the long run.
On Wed, Apr 9, 2008 at 2:47 AM, Fernando Perez <[EMAIL PROTECTED]> wrote:
> I'll be happy to leave it as a new trac ticket with an attachment for
> it if it will make the testing/review process easier in the long run.
Please do. I don't want to change mtrand over until after 1.0.5 is released.
On Wed, Apr 9, 2008 at 12:25 AM, Francesc Altet <[EMAIL PROTECTED]> wrote:
> I don't expect you having problems in that regard either. However, I've
> been having problems compiling perfectly valid Pyrex code with the
> Cython compiler. I just haven't had time to locate where the problem
> i
A Wednesday 09 April 2008, Francesc Altet escrigué:
> A Wednesday 09 April 2008, Andrew Straw escrigué:
> > This is off-topic and should be directed to the pyrex/cython list,
> > but since we're on the subject:
> >
> > I suppose the following is true, but let me ask, since I have not
> > used Cytho
A Wednesday 09 April 2008, Andrew Straw escrigué:
> This is off-topic and should be directed to the pyrex/cython list,
> but since we're on the subject:
>
> I suppose the following is true, but let me ask, since I have not
> used Cython. Please correct me if I'm wrong.
>
> I have a bunch of pyrex c
56 matches
Mail list logo
