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
Better error messages for bad arrow plots #10925
Comments
This comment has been minimized.
This comment has been minimized.
Branch: u/philwilt/ticket/10925 |
Commit: |
comment:5
This seems really complicated. Would it be easier to just do
I get what this code is doing but I'm afraid it's going to be hard to maintain. I don't know how much of an efficiency gain your solution might be, though, or maybe there are too many cases anyway no matter how you do it. What do you think? By the way, it needs doctests of the "bad" cases (there should be examples of traceback doctesting in nearby code, I think, for sure elsewhere in the plot modules). Thanks for working on this, it's close! |
Work Issues: doctest bad cases |
Changed branch from u/philwilt/ticket/10925 to u/kkiviat/ticket/10925 |
Author: Phillip Wilt |
Changed work issues from doctest bad cases to doctest bad cases, does not apply |
comment:11
Removing the "beginner" tag from old tickets. Some could be returned to beginner-friendly status by adding a comment about what needs to be done. Some others might be easy for an experienced developer to finish. |
The error messages for bad arrow setups are somewhat amusing.
and
I leave the traces in for those who want to fix this; tentatively saying beginner. Ideally, we should plot one-dimensional arrows as well (such as how we plot one-dimensional vectors), or should this remain impossible?
CC: @jasongrout @sagetrac-ryan
Component: graphics
Work Issues: doctest bad cases, does not apply
Author: Phillip Wilt
Branch/Commit: u/kkiviat/ticket/10925 @
4bc5203
Issue created by migration from https://trac.sagemath.org/ticket/10925
The text was updated successfully, but these errors were encountered: