On Thu, Feb 11, 2010 at 18:23, Charles R Harris
charlesr.har...@gmail.com wrote:
What about python version? Do we want to bump that up from 2.4?
Only if it were *really* necessary for the Python 3 port. Otherwise, I
would resist the urge.
I don't think it's necessary for that.
--
Pauli
On Fri, Feb 12, 2010 at 9:01 AM, Pauli Virtanen p...@iki.fi wrote:
On Thu, Feb 11, 2010 at 18:23, Charles R Harris
charlesr.har...@gmail.com wrote:
What about python version? Do we want to bump that up from 2.4?
Only if it were *really* necessary for the Python 3 port. Otherwise, I
would
Hi,
I was just looking for numpy.ma.compressed, but forgot its name. I suggest to
add a pointer/see also to numpy.ma.filled at least:
http://docs.scipy.org/numpy/docs/numpy.ma.core.filled/
Unfortunately, I forgot the PW of my account (hans_meine), otherwise I'd have
given it a shot.
Ciao,
On Friday 12 February 2010 13:43:56 Hans Meine wrote:
I was just looking for numpy.ma.compressed, but forgot its name.
Another strange thing is the docstring of numpy.ma.compress, which appears in
ipython like this:
Type: instance
Base Class: numpy.ma.core._frommethod
[...]
On Fri, Feb 12, 2010 at 12:16 AM, David Cournapeau
da...@silveregg.co.jp wrote:
Charles R Harris wrote:
I don't see any struct definitions there, it looks clean.
Any struct defined outside numpy/core/include is fine to change at will
as far as ABI is concerned anyway, so no need to check
On Mon, Feb 8, 2010 at 7:25 PM, Robert Kern robert.k...@gmail.com wrote:
Here's the problem that I don't think many people appreciate: logical
arguments suck just as much as personal experience in answering these
questions. You can make perfectly structured arguments until you are
blue in the
I am trying to read a large amount of data that is output in scientific
notation using D instead of E. After searching around I found a thread that
implied numpy already has the capability to do this:
http://stackoverflow.com/questions/1959210/python-scientific-notation-using-d-instead-of-e
On Fri, Feb 12, 2010 at 10:46 AM, Robert C. ricit...@mac.com wrote:
I am trying to read a large amount of data that is output in scientific
notation using D instead of E. After searching around I found a thread that
implied numpy already has the capability to do this:
On Fri, Feb 12, 2010 at 11:03 AM, josef.p...@gmail.com wrote:
On Fri, Feb 12, 2010 at 10:46 AM, Robert C. ricit...@mac.com wrote:
I am trying to read a large amount of data that is output in scientific
notation using D instead of E. After searching around I found a thread that
implied numpy
josef.p...@gmail.com wrote:
On Fri, Feb 12, 2010 at 11:03 AM, josef.p...@gmail.com wrote:
On Fri, Feb 12, 2010 at 10:46 AM, Robert C. ricit...@mac.com wrote:
I am trying to read a large amount of data that is output in scientific
notation using D instead of E. After searching around
On Fri, Feb 12, 2010 at 10:05, josef.p...@gmail.com wrote:
On Fri, Feb 12, 2010 at 11:03 AM, josef.p...@gmail.com wrote:
np.float('1.5698D+03')
1569.8
np.float('1.23D+04')
12300.0
it's still working with numpy 1.4.0
maybe this is a python feature with python builtin float:
Thank you for the replies. It must be because I am using python on OSX. Is
there no work around for it then?
Robert Kern-2 wrote:
On Fri, Feb 12, 2010 at 10:05, josef.p...@gmail.com wrote:
On Fri, Feb 12, 2010 at 11:03 AM, josef.p...@gmail.com wrote:
np.float('1.5698D+03')
1569.8
Robert Kern wrote:
numpy.float is indeed Python's builtin float type (for obscure
historical reasons that I won't go into). However, in Python 2.5, at
least, the parsing of the string is offloaded to the standard C
function strtod().
well, sort of -- it's pre-processed first, to add some
On Fri, Feb 12, 2010 at 11:27, Christopher Barker chris.bar...@noaa.gov wrote:
Robert Kern wrote:
numpy.float is indeed Python's builtin float type (for obscure
historical reasons that I won't go into). However, in Python 2.5, at
least, the parsing of the string is offloaded to the standard C
2010/2/12 Hans Meine me...@informatik.uni-hamburg.de
On Friday 12 February 2010 13:43:56 Hans Meine wrote:
I was just looking for numpy.ma.compressed, but forgot its name.
Fixed this one in the Wiki.
Another strange thing is the docstring of numpy.ma.compress, which appears
in
ipython
On Fri, Feb 12, 2010 at 12:19, David Goldsmith d.l.goldsm...@gmail.com wrote:
PS: please, if you don't mind, in the future post docstring complaints at
scipy-dev (numpy-discussion has many more subscribers, many of whom probably
don't immediately care about any particular docstring problem,
Hi,
I don't know if y'all are subscribed to the ATLAS mailing list, but,
it would be good if we could find a way of supporting Clint as
strongly as we can.
Best,
Matthew
-- Forwarded message --
From: Clint Whaley wha...@cs.utsa.edu
Date: Fri, Feb 12, 2010 at 9:15 AM
Subject:
Hi,
On Fri, Feb 12, 2010 at 7:02 AM, Fernando Perez fperez@gmail.com wrote:
On Mon, Feb 8, 2010 at 7:25 PM, Robert Kern robert.k...@gmail.com wrote:
Here's the problem that I don't think many people appreciate: logical
arguments suck just as much as personal experience in answering these
On Fri, Feb 12, 2010 at 10:57 AM, Robert Kern robert.k...@gmail.com wrote:
On Fri, Feb 12, 2010 at 12:19, David Goldsmith d.l.goldsm...@gmail.com
wrote:
PS: please, if you don't mind, in the future post docstring complaints
at
scipy-dev (numpy-discussion has many more subscribers, many of
On Fri, Feb 12, 2010 at 14:26, David Goldsmith d.l.goldsm...@gmail.com wrote:
On Fri, Feb 12, 2010 at 10:57 AM, Robert Kern robert.k...@gmail.com wrote:
On Fri, Feb 12, 2010 at 12:19, David Goldsmith d.l.goldsm...@gmail.com
wrote:
PS: please, if you don't mind, in the future post docstring
On Fri, Feb 12, 2010 at 3:29 PM, Robert Kern robert.k...@gmail.com wrote:
On Fri, Feb 12, 2010 at 14:26, David Goldsmith d.l.goldsm...@gmail.com
wrote:
On Fri, Feb 12, 2010 at 10:57 AM, Robert Kern robert.k...@gmail.com wrote:
On Fri, Feb 12, 2010 at 12:19, David Goldsmith
On Fri, Feb 12, 2010 at 14:42, josef.p...@gmail.com wrote:
On Fri, Feb 12, 2010 at 3:29 PM, Robert Kern robert.k...@gmail.com wrote:
On Fri, Feb 12, 2010 at 14:26, David Goldsmith d.l.goldsm...@gmail.com
wrote:
On Fri, Feb 12, 2010 at 10:57 AM, Robert Kern robert.k...@gmail.com wrote:
On
On Fri, Feb 12, 2010 at 3:47 PM, Robert Kern robert.k...@gmail.com wrote:
On Fri, Feb 12, 2010 at 14:42, josef.p...@gmail.com wrote:
On Fri, Feb 12, 2010 at 3:29 PM, Robert Kern robert.k...@gmail.com wrote:
On Fri, Feb 12, 2010 at 14:26, David Goldsmith d.l.goldsm...@gmail.com
wrote:
On
On Fri, Feb 12, 2010 at 14:58, josef.p...@gmail.com wrote:
On Fri, Feb 12, 2010 at 3:47 PM, Robert Kern robert.k...@gmail.com wrote:
On Fri, Feb 12, 2010 at 14:42, josef.p...@gmail.com wrote:
On Fri, Feb 12, 2010 at 3:29 PM, Robert Kern robert.k...@gmail.com wrote:
On Fri, Feb 12, 2010 at
OK, OK, Ok, it's not worth getting into a flame war over. We ask people who
are going to be working on the docstrings to subscribe to scipy-dev; this is
not the same thing as being an innocent bystander asking a question or
making a comment - I retract the request.
Now, does anyone have anything
Robert Kern wrote:
Eh, what? numpy.float is Python's float. No numpy features at all.
my mistake -- I guess I assumed that numpy.float was an alias for
numpy.float64.
anyway, the (all?) the numpy dtypes have their own implementation of
conversion from strings (which are a bit buggy,
On Feb 12, 2010, at 4:24 PM, David Goldsmith wrote:
OK, OK, Ok, it's not worth getting into a flame war over. We ask people who
are going to be working on the docstrings to subscribe to scipy-dev; this is
not the same thing as being an innocent bystander asking a question or
making a
On Fri, Feb 12, 2010 at 2:30 PM, Pierre GM pgmdevl...@gmail.com wrote:
On Feb 12, 2010, at 4:24 PM, David Goldsmith wrote:
OK, OK, Ok, it's not worth getting into a flame war over. We ask people
who are going to be working on the docstrings to subscribe to scipy-dev;
this is not the same
On Feb 12, 2010, at 8:14 PM, David Goldsmith wrote
Is the present issue an instance where Scott's second statement is invalid,
an instance where its validity is resulting in a poor docstring for the
function, or an instance in which Scott's recommendation was not followed?
The methods'
On Fri, Feb 12, 2010 at 7:09 PM, Pierre GM pgmdevl...@gmail.com wrote:
On Feb 12, 2010, at 8:14 PM, David Goldsmith wrote
Is the present issue an instance where Scott's second statement is
invalid, an instance where its validity is resulting in a poor docstring for
the function, or an
30 matches
Mail list logo
