-
-
Notifications
You must be signed in to change notification settings - Fork 481
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 all code from src/setup.py, src/fpickle_setup.py to sage_setup #29702
Comments
Dependencies: #29411 |
This comment has been minimized.
This comment has been minimized.
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
Author: Matthias Koeppe |
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits: |
comment:14
(that was pushed to wrong ticket; fixed) |
comment:15
Ready for review |
Branch pushed to git repo; I updated commit sha1. This was a forced push. Last 10 new commits:
|
comment:17
Redone on top of new version of #29411 |
comment:28
please rebase this over 9.2.beta1 |
comment:29
rebased over rebased #29411 Last 10 new commits:
|
comment:30
Argh! I have a million tickets depending on this |
Reviewer: Dima Pasechnik |
comment:31
well, I don't quite know how to deal with it. The rebased branch works for me. Should we revert all these rebases, and just hope that the merges will work? |
comment:32
Yes, please restore to the unrebased ones. I know that the merges work, I am already testing on them |
comment:33
It's also fine with me if you merge in the current develop, but rebasing is too disruptive. |
Branch pushed to git repo; I updated commit sha1 and set ticket back to needs_review. This was a forced push. Last 10 new commits:
|
comment:35
Replying to @mkoeppe:
Did that, needs review |
comment:36
lgtm |
comment:37
Thank you! |
Changed branch from public/move_all_code_from_src_setup_py__src_fpickle_setup_py_to_sage_setup to |
comment:39
Thank you, the setup.py looks sooo much cleaner now. |
Changed commit from |
This is preparation for splitting sagelib into separate distutils packages, but a useful cleanup in any case.
As a follow-up of this ticket, as part of Meta-ticket #29705, the remaining very short
src/setup.py
should probably be moved tobuild/pkgs/sagelib/src/
(alongside a symlinksrc
->SAGE_ROOT/src
)Depends on #29411
CC: @kiwifb @vbraun @isuruf @dimpase @jhpalmieri @fchapoton @orlitzky
Component: refactoring
Keywords: sd109
Author: Matthias Koeppe
Branch:
a56dc35
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/29702
The text was updated successfully, but these errors were encountered: