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 UI for Python 3 Sage doctesting #27150
Comments
This comment has been minimized.
This comment has been minimized.
comment:2
It's just a UI issue. Everything is behaving as it should be... |
This comment has been minimized.
This comment has been minimized.
comment:3
I don't agree: python2 doctesting is also broken. The py2 tag is not in the optional list and hence ignored. |
comment:4
Are you really sure? |
comment:5
It depends what you mean by "normal". More precisely:
Both look quite artificial to me. Conclusion: doctests are not broken - behavior is very confusing. |
comment:6
Everything is working as designed but the design might be confusing. That's why I said that it's an UI issue. |
comment:7
@jdemeyer: Do you know whether |
comment:8
Ticket retargeted after milestone closed (if you don't believe this ticket is appropriate for the Sage 8.8 release please retarget manually) |
comment:9
As the Sage-8.8 release milestone is pending, we should delete the sage-8.8 milestone for tickets that are not actively being worked on or that still require significant work to move forward. If you feel that this ticket should be included in the next Sage release at the soonest please set its milestone to the next release milestone (sage-8.9). |
comment:11
Outdated, should close |
comment:13
ok |
running
sage -t
in a Python 2 or Python 3 installation of Sage results in a seemingly wrong set of--optional
flagsIn a Python 2 installation the
py2
should be there (and thepython2
appearing because of a is quite weird). While on Python 3 it should bepy3
.See also this sage-devel thread.
CC: @fchapoton
Component: doctest framework
Issue created by migration from https://trac.sagemath.org/ticket/27150
The text was updated successfully, but these errors were encountered: