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
Graphics Array needs suboptions to show #11160
Comments
comment:1
Hmm, but that doesn't work... but it must be a similar issue, anyway. |
comment:2
Adding the suboptions we usually send to save to the normal !Graphics class matplotlib removes the error, but does the following - see attached graphic. I don't have time to do any more with this now, though. |
Note the second graph has two legends for the same function! |
comment:3
Attachment: tmp_0.png Replying to @kcrisman:
I should add that my code was slightly simpler:
|
comment:5
This is a bug which might be related:
It seems that this part of the problem might be completely solved by adding the suboptions usually added when show()'ing a graphics object. |
This comment has been minimized.
This comment has been minimized.
comment:8
The issue described here is fixed in #27865. |
comment:9
Since #27865 has been merged in Sage 8.9.beta0, we could close this ticket as duplicate. |
comment:11
All the examples listed here work fine in the newest develop, at least. |
comment:12
Replying to @johanrosenkilde:
Then maybe you could set this ticket to positive review, given its status is "sage-duplicate/invalid/wontfix" (the positive review is necessary to close it). |
comment:13
Any doctests necessary or are they all included in #27865 as I suspect? |
comment:14
Replying to @kcrisman:
Yes the doctests relevant to this ticket are included in #27865; in Sage 8.9.beta6, you can find them in lines 3481 - 3499 of
as well as in lines 555-613 of
|
comment:15
I only asked because maybe that is why someone hasn't hit positive review. So I guess jsrn should :-) or actually you could as well, I think. |
This is reported at this sage-support thread.
I think the fix should be the same as at #10244, but for the GraphicsArray class.
Related tickets:
CC: @jasongrout @johanrosenkilde @sagetrac-jhonrubia6 @fchapoton
Component: graphics
Issue created by migration from https://trac.sagemath.org/ticket/11160
The text was updated successfully, but these errors were encountered: