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
fix symbolic/pynac.pyx doctests #18257
Comments
comment:1
I agree that this is worth fixing permanently, but unless there is an obvious fix we shouldn't let this hold up adding more symbolic functions. |
comment:2
Replying to @kcrisman:
This is not really difficult. The central database is a dictionary globally defined in There is a problem if ever a function is deregistered. Can this happen? No mechanism in Pynac exists for this at the moment, so it's not a practical consideration. So the solution is easy: instead of simply adding
|
comment:3
As they say the first thing that goes down the drain is the planning. The above solution does not account for user defined Python functions that do not inherit from |
Commit: |
comment:5
No, that was an off-by-one error. Please review. New commits:
|
comment:6
Trivial - duplicate lines in test
This patch seems reasonable. What was comment:3 about? I sense that it was a red herring, but if it could be useful for test-driving this I would love to try it. I assume that since this isn't actually called in Sage but is really just for doctesting, it shouldn't have any speed implications. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Author: Ralf Stephan |
comment:9
Replying to @kcrisman:
It's taken care of in the doctests. |
comment:10
I'm not sure why but I still get
when I have both this ticket and #15024 together. Did I do something wrong? (Note: this is based off of 6.8.beta1, if it matters.) |
comment:12
Same branch does work with pynac-0.3.9 (in case you left that installed and that was the difference between us). |
comment:13
Your line numbers also don't match #18257. |
comment:14
Okay, I'll trash the branches I made locally and try again - may not be immediately, I'm at a conference. |
Reviewer: Karl-Dieter Crisman |
comment:15
I must have either not merged this one or perhaps in the wrong order or something... Anyway, all systems are go, and as expected #15024 fails without this and works with it. Great! |
comment:16
Hold on. I have a necessary addition because of a commit in Pynac where I removed the registry entries for some defunct functions which makes two of the doctest here fail. This would fit in nicely here. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:18
Could you please have a last quick look? |
comment:19
I don't understand why this fails, though? (I mean it shouldn't currently, nothing failed for me.) Surely it would be better to put that commit with the next Pynac upgrade ticket? Easier for the reviewer to test, then (i.e. first upgrade Pynac, run tests (fail), then add branch, watch tests pass). |
Changed branch from u/rws/fix_symbolic_pynac_pyx_doctests to u/rws/18257 |
Changed branch from u/rws/18257 to |
Several doctests in
symbolic/pynac.pyx
iterate overrange(get_ginac_serial(), get_ginac_serial()+100)
. You guess it (sigh),100
is arbitrary and, right now with some new tickets that introduce new functions, it has become too small, leading to unrelated doctest fails insymbolic/pynac.pyx
. This ticket should make sure that this does not happen again.CC: @kcrisman
Component: symbolics
Author: Ralf Stephan
Branch/Commit:
52ccd47
Reviewer: Karl-Dieter Crisman
Issue created by migration from https://trac.sagemath.org/ticket/18257
The text was updated successfully, but these errors were encountered: