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
py3 make doctest of matrix2 future-proof #21630
Comments
Commit: |
Branch: u/chapoton/21630 |
New commits:
|
Reviewer: Jori Mäntysalo |
comment:3
I would vote for this ticket. But maybe I still ask Travis opinion: This ticket changes (Tests passed etc, so otherwise this is a positive review.) |
comment:4
I can understand why this was done, but I think it is good to have the shortcut and used in tests. In particular, it forces us to make updates to the constructor or change the doctests and drop the behavior after a discussion at switch time. I don't have a strong opinion either way for this, but just my 2 cents. |
comment:5
Is there still left enought of those test with only one dimension given after this patch? |
comment:6
There remains a lot of them, for example in src/sage/matrix/matrix0.pyx I think we should only keep one such doctest. EDIT:
|
comment:7
Replying to @fchapoton:
OK then.
Yes, maybe. Then it should be on test block and clearly marked what it is for.
Perl-style regexps... scary. |
Changed branch from u/chapoton/21630 to |
because range will be an iterator in python3
CC: @tscrim
Component: python3
Author: Frédéric Chapoton
Branch/Commit:
55f7277
Reviewer: Jori Mäntysalo
Issue created by migration from https://trac.sagemath.org/ticket/21630
The text was updated successfully, but these errors were encountered: