-
-
Notifications
You must be signed in to change notification settings - Fork 508
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 expired deprecations in sage/combinat #19513
Comments
comment:1
-1 to this ticket. There is no reason to just remove all deprecations like that. Those deprecations may be removed, that's true. But does this imply that it's the right thing to do? Not always. I doubt that any one person really understands all the deprecated code in Sage and you obviously should not remove deprecations that you don't understand. Besides that, this ticket is simply too broad. If you want to remove specific deprecations, just remove those. But not all at once. |
comment:2
Fair enough. At least |
This comment has been minimized.
This comment has been minimized.
comment:3
|
comment:4
Replying to @jm58660:
6.5 was released less than a year ago so those can stay a bit longer. |
Branch: public/ticket/19513 |
Changed keywords from none to deprecate |
Commit: |
comment:5
I'll give a full list of relevant tickets soon. I'll also add to the cc list to ensure that everyone is aware that these functions are disappearing. I decided my rule was not to touch anything that was deprecated in sage 6.4 or later. There is enough here for the moment. Last 10 new commits:
|
Author: Mike Zabrocki |
comment:6
I will still have to go through the documentation and ensure that removed code does not appear there (this was just a first pass). I just added a large number of people to the cc list hoping that they will all check that the code that they are responsible for deprecating really should be removed. split_nk.py and choose_nk.py are in ticket #18674 |
This comment has been minimized.
This comment has been minimized.
comment:7
I can vouch for everything except that in designs. Nathann, Vincent, I think those are more in your area. |
comment:8
NOTE: whenever For example, |
comment:9
I can restore it if you (or Nicolas or Florent) think that it should remain, however I was following the instruction:
that was in the file. Note that I did not delete |
This comment has been minimized.
This comment has been minimized.
comment:11
Replying to @tscrim:
No, they were not. From #6637 (emphasis mine):
Those classes should have been deprecated in #16352, but they weren't. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
comment:27
I am not convinced that the code in |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:30
I had forgotten that I had not restored the |
comment:31
Apparently, you removed a global import and it causes trouble
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:34
You removed some deprecation released in sage-6.4 (from 04/14/15)... One year deprecation implies that this should not be merged until 04/14/16 which is in 6 months. This concerns this modification
|
This comment has been minimized.
This comment has been minimized.
comment:35
Sage 6.4 was released 14 november 2014, so it's more than 1 year ago. |
comment:36
|
comment:37
14 april 2015 is the release date of Sage 6.6 |
comment:38
Thanks Jeroen for the corrections! I used the dates from trac milestones that were obviously wrong. I fixed them. And I can set this ticket to positive review! |
Reviewer: Vincent Delecroix |
Changed branch from public/ticket/19513 to |
A grep of the word
deprecation
in the source code ofsage/combinat
indicates that there are many functions which have expired. All warnings which were placed there with the intention of eventually removing them. We will clean up some of this code and remove deprecations which have been in Sage for at least one year (the focus will be on those that have been merged since two years).Code deprecated from:
CC: @sagetrac-fwclarke @AndrewAtLarge @anneschilling @darijgr @VivianePons @hivert @fchapoton @sagetrac-chrisjamesberg @saliola @ghseeli @sagetrac-sage-combinat @zabrocki @nthiery @sagetrac-alubovsky @tscrim @simon-king-jena @bsalisbury1 @videlec @staroste @nathanncohen @brettpim
Component: combinatorics
Keywords: deprecate
Author: Mike Zabrocki
Branch/Commit:
a97a800
Reviewer: Vincent Delecroix
Issue created by migration from https://trac.sagemath.org/ticket/19513
The text was updated successfully, but these errors were encountered: