>
> I didn't see any explicit nan handling. Are missing values allowed
> e.g. in the constructor?
>
No, this is a valid point. We don't handle this as explicitly as we
should. Are you mostly talking about nan handling in loading from
delimited text files? (Or are you talking about something mo
On Tue, Oct 6, 2009 at 12:31 PM, wrote:
> On Mon, Oct 5, 2009 at 5:22 PM, Elaine Angelino
> wrote:
>> Hi there,
>>
>> We are writing to announce the release of "Tabular", a package of Python
>> modules for working with tabular data.
>>
>> Tabular is a package of Python modules for working with t
On Mon, Oct 5, 2009 at 5:22 PM, Elaine Angelino
wrote:
> Hi there,
>
> We are writing to announce the release of "Tabular", a package of Python
> modules for working with tabular data.
>
> Tabular is a package of Python modules for working with tabular data. Its
> main object is the tabarray class
On 10/05/2009 06:20 PM, Robert Kern wrote:
> On Mon, Oct 5, 2009 at 18:15, Elaine Angelino
> wrote:
>
>
>>> Well, what other recarray functionality are you using?
>>>
>> None, in our code. We also thought that since at least some people like
>> using the attribute reference property
On Mon, Oct 5, 2009 at 7:20 PM, Robert Kern wrote:
> On Mon, Oct 5, 2009 at 18:15, Elaine Angelino
> wrote:
>
>
> Then I would suggest making tabarrays subclass from ndarray.
>
Ok, done.We did it using the from*() function design you suggested. In
the future, if there are more direct from*
On Mon, Oct 5, 2009 at 18:15, Elaine Angelino wrote:
>> Well, what other recarray functionality are you using?
>
> None, in our code. We also thought that since at least some people like
> using the attribute reference property, perhaps users of tabarrays might too
> (though we don't personally
Do the minimum number of .view()s that you can get away with.
>
>
I guess our bottom line is that we're still not 100% clear as to the
recommendation of the NumPy community regarding whether we should use
recarray or ndarray. It seems like recarray has some advantages (e.g. the
nice inference func
On Mon, Oct 5, 2009 at 17:52, Elaine Angelino wrote:
> On Mon, Oct 5, 2009 at 6:36 PM, Robert Kern wrote:
>
>> > the main reason we went with the recarray over the ndarray is because
>> > the
>> > recarray has a couple of useful construction functions (e.g.
>> > np.rec.fromrecords and np.rec.from
On Mon, Oct 5, 2009 at 6:36 PM, Robert Kern wrote:
> >
> > the main reason we went with the recarray over the ndarray is because the
> > recarray has a couple of useful construction functions (e.g.
> > np.rec.fromrecords and np.rec.fromarrays). not only are these functions
> > convenient to us
On Mon, Oct 5, 2009 at 17:16, Elaine Angelino wrote:
> hey pierre -- good question. this is something we debated a while ago (we
> actually sent a couple of emails over the numpy list about this very topic)
> when coming up with our design. at the time, there did not seem to be
> strong opinions
hey pierre -- good question. this is something we debated a while ago (we
actually sent a couple of emails over the numpy list about this very topic)
when coming up with our design. at the time, there did not seem to be
strong opinions either way about using ndarray vs. recarray
the main reason w
Ciao Elaine,
I just quickly browsed through your code. Say, what's the reason
behind using np.recarrays instead of just standard ndarrays (with
flexible dtype). Do you really need the overhead of accessing fields
as attributes ? It looks like you're always accessing fields as items...
Cheers
Hi there,
We are writing to announce the release of "Tabular", a package of Python
modules for working with tabular data.
Tabular is a package of Python modules for working with tabular data. Its
main object is the tabarray class, a data structure for holding and
manipulating tabular data. By put
13 matches
Mail list logo
