Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Minor offsetText formatting improvement #4451

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.

Sign up for GitHub

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

Jump to bottom
Open
anntzer opened this issue May 21, 2015 · 3 comments
Open

Minor offsetText formatting improvement #4451

anntzer opened this issue May 21, 2015 · 3 comments
Labels
API: changes keep Items to be ignored by the “Stale” Github Action New feature
Milestone
future releases

Comments

@anntzer
Copy link
Contributor

anntzer commented May 21, 2015 •
edited
Loading

Currently, the axis offset text is always typeset with the format string "%1.10e" followed by some crazy postprocessing in ScalarFormatter._formatSciNotation. I would suggest switching to some "%g"-based format, so that e.g. 1234 doesn't get formatted as "1.234e3" which can hardly be described as "more legible". Probably _formatSciNotation could be simplified a bit too.

Simple example:

python -c 'from pylab import *; plot(*[1234 + arange(10)] * 2); show()'

Edit: the above is now fixed by the switch of axes.formatter.offset_threshold to 4, but the issue remains with

python -c 'from pylab import *; plot(*[12.321 + arange(5) * .001] * 2); show()'

test
where the offset text should be "12.320" (or at least "12.32"), not "1.232e1".
@tacaswell tacaswell added this to the proposed next point release milestone May 21, 2015
@anntzer anntzer mentioned this issue Dec 29, 2015
Closed
@petehuang
Copy link
Contributor

#5785 improved the calculation of the offset text but this particular formatting issue still is up for grabs

@anntzer
Copy link
Contributor Author

anntzer commented Jan 10, 2017

@petehuang I appreciate your efforts are triaging through the list of issues, but messages such as this one only reach the (small) participants list and do not actually help bumping the issue.

@tacaswell tacaswell modified the milestones: 2.1 (next point release), 2.2 (next next feature release) Oct 3, 2017
@github-actions
Copy link

This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!

@github-actions github-actions bot added the status: inactive Marked by the “Stale” Github Action label Mar 13, 2023
@anntzer anntzer added keep Items to be ignored by the “Stale” Github Action and removed status: inactive Marked by the “Stale” Github Action labels Mar 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
API: changes keep Items to be ignored by the “Stale” Github Action New feature
Projects
None yet
Milestone
future releases
Development

No branches or pull requests
3 participants
@tacaswell @petehuang @anntzer