#13131: Make a top-level table/Table function
----------------------------------+-----------------------------------------
Reporter: kcrisman | Owner: was
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-5.9
Component: user interface | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers: Jason Grout, Karl-Dieter
Crisman
Authors: John Palmieri | Merged in:
Dependencies: | Stopgaps:
----------------------------------+-----------------------------------------
Comment (by slabbe):
Replying to [comment:28 jhpalmieri]:
> This is just documentation; I haven't changed the code. If we want to
change the behavior of `html` (maybe just adding a `str` method or
something like that), let's do it on another ticket and keep this one
focused on tables.
I agree. I just can't close my mouth sometimes!
> I can add this, but what should happen if you do `table(array,
column=columns)`? Raise an error? Or try to combine the two sets of data
somehow? I think I prefer to raise an error.
or maybe the interface could be :
{{{
sage: table(data=rows)
...
sage: table(data=columns, orientation='columns')
...
}}}
where orientation would be an optional argument taking `'rows'` as default
value? This way there can't be inconsistent inputs.
> The easiest thing to do with the code as it stands is
`table(columns).transpose()`.
ok
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13131#comment:29>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
