On 06/09/2017 10:28, Ximin Luo wrote:
Jeroen Demeyer:
On 2017-09-06 14:53, Ximin Luo wrote:
I've seen numerous cases where Sage has to change the expected test output
simply because a dependency was upgraded. There has to be a more sustainable
way of achieving this...
Suggestions welcome...
Note that none of your above proposals is relevant to the typical PARI failures. We would need
support in the doctest framework for stuff like "# generates same group" or "# same
element of H^1(...)" or whatever. I don't think this can be fixed in the doctest framework.
OK. Another suggestion would be to wrap many of the test cases in normalising
functions like round() or whatever is appropriate (for PARI it would be group
theory related stuff). For example:
+1 It would be nice to have the testsuite pass on the different PARI
versions.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
