Well, I think we should figure out what the various printing methods
should do. As far as I can tell we have:
- plain str/repr (the same for technical reasons)
- sstr and srepr
- pprint
Now, as I see it, pprint is really what we use interactively. Depending
on the environment it might be ascii, unicode or latex, but in any case
this is the one that is supposed to look good. The main use of sstr is
in doctests. When is plain str ever used?
As far as I can see, pprint should just look good, and "str" should
produce something that, when passed to sympify, recreates the
expression. What about sstr? From my taxonomy above, sstr is also
output-oriented, and as such there does not seem to be a need for this
to recreate the original expression upon sympify. Which of course would
mean that the current quasi-2d printing is fine, so I must be
misunderstanding things...
Tom
On 10.06.2012 15:57, Chris Smith wrote:
Ah, so there was work on this. As a heads up, why didn't this get committed?
@goodok had some comments and ideas about how he thought this should
move. But it looks like he is busy with other things at the moment. I
think all the discussion is intact at the pull request. If you can
give it the final touches in line with what he was saying, I would be
happy to review it. In any case, please check over the notes and work
there.
/c
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To post to this group, send email to sympy@googlegroups.com.
To unsubscribe from this group, send email to
sympy+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sympy?hl=en.
