Pierre GM wrote:
Ryan,
OK, I'll look into that. I won't have time to address it before this
next week, however. Option #2 looks like the best.
No hurries, I just want to make sure I raise any issues I see while the design
is
still up for change.
In other news, I was considering renaming
Pierre GM wrote:
All,
Here's the latest version of genloadtxt, with some recent corrections.
With just a couple of tweaking, we end up with some decent speed: it's
still slower than np.loadtxt, but only 15% so according to the test at
the end of the package.
I have one more use issue that
Ryan,
OK, I'll look into that. I won't have time to address it before this
next week, however. Option #2 looks like the best.
In other news, I was considering renaming genloadtxt to genfromtxt,
and using ndfromtxt, mafromtxt, recfromtxt, recfromcsv for the
function names. That way, loadtxt
Pierre GM wrote:
in the same place in NumPy; and all the SciPy IO code to be in the
same place in SciPy.
+1
So, no problem w/ importing numpy.ma and numpy.records in numpy.lib.io ?
As long as numpy.ma and numpy.records are, and will remain, part of the
standard numpy distribution, this is
On Fri, Dec 5, 2008 at 3:59 PM, Pierre GM [EMAIL PROTECTED] wrote:
All,
Here's the latest version of genloadtxt, with some recent corrections. With
just a couple of tweaking, we end up with some decent speed: it's still
slower than np.loadtxt, but only 15% so according to the test at the end
Jarrod Millman wrote:
From the user's perspective, I would like all the NumPy IO code to be
in the same place in NumPy; and all the SciPy IO code to be in the
same place in SciPy.
+1
So I
wonder if it would make sense to incorporate AstroAsciiData?
Doesn't it overlap a lot with
On Dec 9, 2008, at 12:59 PM, Christopher Barker wrote:
Jarrod Millman wrote:
From the user's perspective, I would like all the NumPy IO code to
be
in the same place in NumPy; and all the SciPy IO code to be in the
same place in SciPy.
+1
So, no problem w/ importing numpy.ma and
On Tue, Dec 09, 2008 at 01:34:29AM -0800, Jarrod Millman wrote:
It was decided last year that numpy io should provide simple, generic,
core io functionality. While scipy io would provide more domain- or
application-specific io code (e.g., Matlab IO, WAV IO, etc.) My
vision for scipy io,
Pierre GM wrote:
All,
Here's the latest version of genloadtxt, with some recent corrections.
With just a couple of tweaking, we end up with some decent speed: it's
still slower than np.loadtxt, but only 15% so according to the test at
the end of the package.
And so, now what ? Should I
On Fri, Dec 05, 2008 at 06:59:25PM -0500, Pierre GM wrote:
Here's the latest version of genloadtxt, with some recent corrections. With
just a couple of tweaking, we end up with some decent speed: it's still
slower than np.loadtxt, but only 15% so according to the test at the end of
the
All,
Here's the latest version of genloadtxt, with some recent corrections.
With just a couple of tweaking, we end up with some decent speed: it's
still slower than np.loadtxt, but only 15% so according to the test at
the end of the package.
And so, now what ? Should I put the module in
11 matches
Mail list logo
