-
-
Notifications
You must be signed in to change notification settings - Fork 601
regression in solve #14306
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
Comments
comment:1
I've reported this at Maxima bug 2564. |
Upstream: Reported upstream. No feedback yet. |
Changed upstream from Reported upstream. No feedback yet. to Fixed upstream, but not in a stable release. |
comment:3
see #13973 |
Changed upstream from Fixed upstream, but not in a stable release. to Fixed upstream, in a later stable release. |
comment:8
Wait a minute. This is already almost a doctest in Sage.
and it passes
But assuming we want to add this back: Paul, where should this appear - presumably in src/sage/tests/french_book/calculus_doctest.py ? |
comment:9
in our book we originally had the example in the description (at that time we were using Sage 5.1) but With Paul |
comment:10
Ah, but with #13973 we have
As you see, Maxima fixed it. So are you saying that you don't need this for your book? We can still add this as a doctest elsewhere, of course. |
comment:11
yes we don't need this (with Paul |
Commit: |
Author: Karl-Dieter Crisman |
Last 10 new commits:
|
comment:13
Once again sorry for the looong branch - I'll do this better after the current Maxima upgrade things are done. |
comment:14
The last colon before the example should be a double colon. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:16
Right you are! I've fixed this now. I just want to point out that in Mercurial, I could always "roll back" the previous commit and fix such trivialities. Now it has to clutter up the log/tree/directed acyclic graph/whatever for a one-character fix. New commits:
New commits:
|
comment:17
Replying to @kcrisman:
You still can. You'll just have to "force push" and deal with a grumpy Volker. It's a trade-off: do you want a clean history or a (small) chance for more difficult merge issues later on, in case someone based some work on your now abandoned commit? |
Reviewer: Peter Bruin |
Changed branch from u/kcrisman/14306-maxima_solve_doctest to |
the following example, which we use in our book (in french) about Sage, does not work any more with Sage 5.7:
With Sage 5.1:
With Sage 5.7:
Cf http://sagebook.gforge.inria.fr/
Upstream: Fixed upstream, in a later stable release.
CC: @mezzarobba
Component: calculus
Author: Karl-Dieter Crisman
Branch/Commit:
0585302
Reviewer: Peter Bruin
Issue created by migration from https://trac.sagemath.org/ticket/14306
The text was updated successfully, but these errors were encountered: