-
-
Notifications
You must be signed in to change notification settings - Fork 528
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
Change handling of 'sage --APP' #29930
Comments
comment:1
Should we also deprecate these commands? Right now:
If we deprecate, is the alternative
? I think the quotes are necessary. Is this too unwieldy, or are we happy to essentially discourage people from using these commands at all? |
Branch: u/jhpalmieri/deprecate-sage-APP |
comment:3
Here's a branch to start the conversation. Last 10 new commits:
|
Commit: |
comment:4
|
comment:6
needs rebase |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:8
Here's a new version. Not a strict rebase: the earlier version deprecated commands like |
comment:10
See #30563 regarding |
comment:11
Setting new milestone based on a cursory review of ticket status, priority, and last modification date. |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:16
Rebased. Still don't know if this a good approach or worth spending much time on. |
Rather than handling
sage --gp
,sage --singular
, etc. as separateif
blocks in thesage
script, treat them more uniformly.Component: scripts
Branch/Commit: u/jhpalmieri/deprecate-sage-APP @
0ad0e4f
Issue created by migration from https://trac.sagemath.org/ticket/29930
The text was updated successfully, but these errors were encountered: