-
-
Notifications
You must be signed in to change notification settings - Fork 490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improve documentation of pretty_print #29136
Comments
Branch: u/gh-mwageringel/29136 |
Author: Markus Wageringel |
Commit: |
comment:2
lgtm, but what do you think about a shorter name for the context manager? |
comment:3
it's not so bad, but I would still go for |
comment:4
Thanks for the suggestions. I have renamed it to I have also fixed the doctest failure in the Mathematica interface that was found by the patchbot (diff). New commits:
|
This comment has been minimized.
This comment has been minimized.
Changed branch from u/gh-mwageringel/29136 to u/gh-mwageringel/29136v2 |
comment:5
Could someone review this please? |
comment:6
Batch modifying tickets that will likely not be ready for 9.1, based on a review of the ticket title, branch/review status, and last modification date. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:9
Setting new milestone based on a cursory review of ticket status, priority, and last modification date. |
comment:10
As of Sage 9.3.rc2, |
comment:11
Actually text preference of the display manager does not affect terminal ipython backend.
|
comment:12
Replying to @kwankyu:
Well, they do if set to Is there an interest in the other changes on the current branch or should we close this ticket? Mainly, the branch adds a context manager for changing the display preferences and improves the documentation of |
comment:13
Replying to @mwageringel:
Right. I missed that.
I don't know. Possibly. At least you need to revise the ticket description, and explain what this ticket achieves in the changed situation. |
comment:18
Replying to @kwankyu:
For interactive use, I would just use the magic |
comment:19
For doctesting rich output textual representations, functions like For the documentation of In conclusion, I don't see any real necessity or benefit of One other comment: --- a/src/sage/repl/rich_output/pretty_print.py
+++ b/src/sage/repl/rich_output/pretty_print.py
@@ -4,7 +4,7 @@ The ``pretty_print`` command
Works similar to the ``print`` function, except that it always tries
to use a rich output for an object, as specified via the text display
-preference. If such a rich output is not available, it is falling back on the
+preference. If such a rich output is not available, it falls back on the
plain text.
EXAMPLES:: |
comment:20
Yes, I agree. Replying to @kwankyu:
I have implemented this by hiding the actual change of the preferences in a New commits:
|
Changed branch from u/gh-mwageringel/29136v3 to u/gh-mwageringel/29136v4 |
This comment has been minimized.
This comment has been minimized.
Reviewer: Kwankyu Lee |
comment:21
Okay. It seems that this is the best we can do right now. In the future, I hope we could remove the |
comment:22
Merge fails. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:24
Trivial merge, so I am setting this back to positive. |
Changed branch from u/gh-mwageringel/29136v4 to |
This ticket improves the documentation of
pretty_print
, which was previously missing from the documentation.CC: @nbruin @mantepse
Component: refactoring
Author: Markus Wageringel
Branch/Commit:
264bd7c
Reviewer: Kwankyu Lee
Issue created by migration from https://trac.sagemath.org/ticket/29136
The text was updated successfully, but these errors were encountered: