-
-
Notifications
You must be signed in to change notification settings - Fork 482
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 support for Parent.__init__(gens=...) #21385
Comments
Branch: u/jdemeyer/ticket/21385 |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Commit: |
This comment has been minimized.
This comment has been minimized.
comment:4
The changes look good to me, but shouldn't the feature in question first be deprecated, in case something outside Sage uses it? (To be clear, I personally think the deprecation policy is both too vague and much too strict for the level of quality and maturity of large parts of Sage. But Sage does have such a policy...) |
comment:5
Replying to @mezzarobba:
I don't see the point of deprecation here because the So I am not removing any functionality, I am basically just removing dead code. In any case, this ticket depends on #21382 which should be reviewed first. |
comment:6
Replying to @jdemeyer:
Fine then. (I hadn't paid attention to the fact that
Yes, I posted the comment here since it applied to the second commit, but I was actually waiting for your answer to set the first ticket to positive review |
Reviewer: Marc Mezzarobba |
Changed branch from u/jdemeyer/ticket/21385 to |
Parent.__init__()
takes agens
keyword argument, but it turns out that nothing in Sage actually uses this argument. So we simply remove it. Then we can also remove the_populate_generators_
method which is never actually called.(see also the task ticket: #21380)
Depends on #21382
CC: @videlec @tscrim
Component: categories
Author: Jeroen Demeyer
Branch/Commit:
517808d
Reviewer: Marc Mezzarobba
Issue created by migration from https://trac.sagemath.org/ticket/21385
The text was updated successfully, but these errors were encountered: