-
-
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
Move attrcall and friends from sage.misc.misc to new module sage.misc.call #29869
Comments
This comment has been minimized.
This comment has been minimized.
Commit: |
comment:3
The reimport in New commits:
|
Author: Matthias Koeppe |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:7
I think this is clean now, needs review |
comment:8
You need to add the new file to
It is also missing the standard header information:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Reviewer: Travis Scrimshaw |
comment:10
Thanks. If the patchbot comes back green, then this is a positive review. |
comment:11
Well, there are all kinds of colors, but I think this is from code that was already there |
comment:12
There is one real failure:
|
comment:13
OK... I need some help here. Do I need to add |
comment:14
Yes, that is correct. You can add it in the old file to redirect to the new file. The other option (which has happened) is to simply drop the backwards compatibility and tell people to find a version of Sage during the deprecation period to load it then resave as a new pickle. IMO, I would rather do the former here since it is a 1-line fix. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:16
Thanks. I had to add it to the new file though because New commits:
|
comment:17
I think it doesn't matter where it is at. I just want to see one more run of the patchbot before setting a positive review. |
comment:19
Thanks! |
Changed branch from u/mkoeppe/move_attrcall_and_friends_from_sage_misc_misc_to_new_module_sage_misc_call to |
<!-- ^ Please provide a concise and informative title. --> <!-- ^ Don't put issue numbers in the title, do this in the PR description below. --> <!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method to calculate 1 + 2". --> <!-- v Describe your changes below in detail. --> <!-- v Why is this change required? What problem does it solve? --> <!-- v If this PR resolves an open issue, please link to it here. For example, "Fixes sagemath#12345". --> Remove code deprecated in - sagemath#32987 (2022) - sagemath#33213 (2022) - sagemath#29869 (2020) - sagemath#17815 (2020) - sagemath#29892 (2020) ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> - [x] The title is concise and informative. - [ ] The description explains in detail what this PR is about. - [x] I have linked a relevant issue or discussion. - [ ] I have created tests covering the changes. - [ ] I have updated the documentation and checked the documentation preview. ### ⌛ Dependencies <!-- List all open PRs that this PR logically depends on. For example, --> <!-- - sagemath#12345: short description why this is a dependency --> <!-- - sagemath#34567: ... --> URL: sagemath#37868 Reported by: Matthias Köppe Reviewer(s): Michael Orlitzky
This will help with #29865
CC: @tscrim
Component: refactoring
Author: Matthias Koeppe
Branch/Commit:
6024ffd
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/29869
The text was updated successfully, but these errors were encountered: