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
automatic papersize selection by ps backend is almost certainly broken #7551
Comments
Currently the code looks like: matplotlib/lib/matplotlib/backends/backend_ps.py Lines 80 to 85 in 9caa261
so slightly different sorting. I guess that sorted(papersize.items(), key=lambda v: v[1]) will be better as it gives:
|
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! |
Based on the discussions in #22796 this is very hard to fix in a back compatible way. (But easy to fix as such.) There were some discussions if we actually require ps, as most people probably use eps anyway. One solution is to introduce a pending deprecation for ps and see the reactions? |
My preference would be to completely deprecate and then drop papersize, and make ps output at the size of the figure, like all other backends. We could (if there's really demand for it) additionally support |
Talked about this on the call, the consensus was to remove the "auto" feature. |
No minimal example, but the relevant chunk (
backend_ps.py
) isNote that the sorting is by name, which means that the size is the first one among "a9, a8, ..., a2, a10, a1, b9, b8, ..., b2, b10, b1" (in that order) that is larger than the requested size -- which makes no sense.
The text was updated successfully, but these errors were encountered: