Hi,
> I receive the NumPy and SciPy digests because the amount of traffic
> on the lists is so high and my time to keep up with them is so limited
> (there is probably a way to filter emails in Thunderbird that would
> work, but I still have to figure that out).
Why not just create a filter that
James,
Thank you for that very helpful set of suggestions. I think the main
thing is to keep the subject heading so that we can parse which
conversation the response is targeted to.
Also, not including the entire digest in the response is useful as well.
We don't want to push occasional po
Hi Robert et al.,
> 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.
Just a suggestion, which I hope doesn't annoy anyone :-).
I rece
On Thu, Apr 10, 2008 at 2:31 AM, Sebastian Haase <[EMAIL PROTECTED]> wrote:
> I hope I won't we excluded from further discussions if I would prefer
> to stick with my "single capital" approach for my "every day modules".
> I already have a default, "import numpy as N" (and some others of my
> o
Am Donnerstag, 10. April 2008 11:05:35 schrieb Matthew Brett:
> type thing. Upper case also draws the eye to the capital letter, so
>
> print N.sin(a)
>
> pulls the eye to the N, so you have to disengage and remind yourself
> that it's the sin(a) that is important, whereas:
>
> print np.sin(a)
>
>
On Thu, Apr 10, 2008 at 11:05 AM, Matthew Brett <[EMAIL PROTECTED]> wrote:
> Hi Joe,
>
> I do see your point - and agree that typing and cruft make code harder
> to write and read, to some extent. But I think the point is - and I'm
> increasingly finding this - that a judicious use of namespace
Hi Joe,
I do see your point - and agree that typing and cruft make code harder
to write and read, to some extent. But I think the point is - and I'm
increasingly finding this - that a judicious use of namespaces and
'from' statements makes the code much easier to read, as in
import numpy as np
f
On Thu, Apr 10, 2008 at 02:21:05AM -0400, Joe Harrington wrote:
> I'll go so far as to suggest that if scipy must
> have multiple packages within it, we could have them each be their own
> top-level package, and drop the "scipy." (or "S.", or "sp.") prefix
> entirely.
Sound like C-type namespace
On Wed, Apr 9, 2008 at 11:21 PM, Joe Harrington <[EMAIL PROTECTED]> wrote:
> > 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
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
11 matches
Mail list logo
