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
remove deprecated code in functions/ and symbolic/ #16023
Comments
New commits:
|
Commit: |
Branch: u/rws/ticket/16023 |
Reviewer: Burcin Erocal |
comment:2
Many thanks for cleaning up! It looks like some function bodies are reduced to |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:4
Thanks. I believe you mean |
comment:5
Looks good to me. You can switch to positive review once the patchbot gives it a greenlight. (Does patchbot work with the git workflow now?) |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:7
Replying to @burcin:
Not here. This is still unresolved: Thanks. |
comment:8
The Bessel functions weren't removed that long ago, and note that there is a LOT more to be removed - namely, the whole underscore versions of them, see https://github.com/sagemath/sagetrac-mirror/blob/develop/src/sage/functions/bessel.py?id=9db8c5c598ec9de953a33b14e531bee3c092c199#n1102 - basically to the end of the document. Still, hopefully it wouldn't be a problem. I am pretty sure that all the doctests in the stuff to be removed is replicated elsewhere, but it might be worth checking out just to be sure. Also note that here there is a small bit to be removed. I wouldn't cry if the whole Bessel removal were another ticket. |
Last 10 new commits:
|
Changed branch from u/rws/ticket/16023 to u/rws/ticket/16023-1 |
comment:10
Oops wrong branch. |
Changed branch from u/rws/ticket/16023-1 to u/rws/ticket/16023 |
comment:11
Now the branch doesn't seem to be coming up... |
comment:20
Somewhat surprisingly, given the attention to detail you've clearly given, there is still work to be done here - but easy work, I believe.
should not work at all. So either we should confirm it raises an error, check what "should" happen, or make it break... |
comment:21
Burcin, in case you're reading this - what was your intent with that doctest? Should this not work because an embedding needs to be specified, or should it "just work"? |
Changed reviewer from Burcin Erocal to Burcin Erocal, Karl-Dieter Crisman |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:24
Still needed, I believe.
Given that
suggests that this is the only kind of error we treat, and then we just plop it in RR or CC as we can, I suppose we could remove that entire thing and do
as the entire body of call or even remove it. What do you think? |
comment:25
Replying to @kcrisman:
Right. It shouldn't work without specifying an explicit embedding in the I don't have time to try the patch now. It would be nice to give the user a helpful error message in this case, but I have no idea how much trouble that is. |
comment:26
Thanks, Burcin! Okay, I will look at this today, then. Here are a few notes to myself so I don't forget (they are probably taken care of elsewhere or not needed):
|
comment:27
Yeah, although something similar is tested in symbolic/function.pyx this is testing something very specific to exp, so that test should be kept, probably just in the same place as the other example, or in some generic tests place in the file.
The 2607 stuff actually just removes the deprecated method for local max/min, but there is also the deprecated function it depended on which we might as well remove at the same time, seems weird not to
These don't seem to have been tested, though, which is good for this ticket. The stuff for 6094 I found is unrelated to this ticket and not high priority, and 10859 was already all set.
Here is current status if I just remove the call method entirely like you did the others.
I guess we could keep the method and raise an error about embedding, or keep this one. This is the only doctest failure in either directory, and we would want to rescue the tests from that module. What do you think? I hope it's okay with the multi back and forth on this. |
comment:28
Well then, is this still really needs_work? |
comment:29
Yes, because currently
doesn't just work, it is doctested! But the discussion above confirms it should not be allowed to work. So, as I said above, we can either remove the call method entirely and then doctest that error, or keep it and make sure it raises an error about embedding as appropriate. We should also rescue the correct doctests from that method and put them somewhere as tests. |
comment:31
Ah ok. I should have looked into it better. I think after the buildbot thumbs up this can be set to positive? |
comment:32
Yup, thanks! |
Changed branch from u/rws/ticket/16023 to |
Component: symbolics
Keywords: deprecation
Author: Ralf Stephan
Branch/Commit:
633a411
Reviewer: Burcin Erocal, Karl-Dieter Crisman
Issue created by migration from https://trac.sagemath.org/ticket/16023
The text was updated successfully, but these errors were encountered: