Another automatic change

src/bin/sage

@@ -77,7 +77,7 @@ resolvelinks() {
 }
 
 # Resolve the links in $0 so that local/bin/sage can be executed from
-# a symlink (Trac #30888).
+# a symlink (Issue #30888).
 SELF=$(resolvelinks "${0}")
 
 # Display the current version of Sage
@@ -173,7 +173,7 @@ if [ -z "$SAGE_VENV" -a -x "${SELF}-venv-config" ]; then
     export SAGE_VENV=$("${SELF}-venv-config" SAGE_VENV)
 fi
 if [ -f "${SELF}-env-config" ]; then
-    # As of Trac #22731, sage-env-config is optional.
+    # As of Issue #22731, sage-env-config is optional.
     . "${SELF}-env-config" >&2
 fi
 
@@ -570,7 +570,7 @@ fi
 if [ "$1" = '-c' ]; then
     shift
     sage_setup
-    unset TERM  # See Trac #12263
+    unset TERM  # See Issue #12263
     exec sage-eval "$@"
 fi
 
@@ -1016,7 +1016,7 @@ fi
 if [ "$1" = "-docbuild" -o "$1" = "--docbuild" ]; then
     shift
 
-    # Trac #30002: ensure an English locale so that it is possible to
+    # Issue #30002: ensure an English locale so that it is possible to
     # scrape out warnings by pattern matching.
     export LANG=C
     export LANGUAGE=C
@@ -1027,7 +1027,7 @@ if [ "$1" = "-docbuild" -o "$1" = "--docbuild" ]; then
         export OMP_NUM_THREADS=1
     fi
 
-    # Trac #33650: Make sure that user configuration of Jupyter does not
+    # Issue #33650: Make sure that user configuration of Jupyter does not
     # shadow our sagemath kernel when jupyter-sphinx is invoked
     export JUPYTER_CONFIG_DIR=/doesnotexist
     export JUPYTER_CONFIG_PATH=/doesnotexist
@@ -1141,7 +1141,7 @@ if [ $# -ge 1 ]; then
         exit 1
     fi
     sage_setup
-    unset TERM  # See Trac #12263
+    unset TERM  # See Issue #12263
     # sage-run rejects all command line options as the first argument.
     exec sage-run "$@"
 fi

src/bin/sage-coverage

@@ -37,7 +37,7 @@ def coverage_all(directory):
 
     print(''.join(s))
 
-    # Trac #5859: Don't crash if there isn't anything to test.
+    # Issue #5859: Don't crash if there isn't anything to test.
     score = 100.0
     if total != 0:
         score = (float(scr) / total)

src/bin/sage-cython

@@ -1,7 +1,7 @@
 #!/usr/bin/env sage-python
 
 # This script is a deprecated wrapper around the "cython" program.
-# It is deprecated since Trac #27041 (Sage 8.7) because one should
+# It is deprecated since Issue #27041 (Sage 8.7) because one should
 # simply use "cython" directly. We display deprecation messages whenever
 # "sage-cython" does something different from plain "cython".
 #

src/bin/sage-env

@@ -278,7 +278,7 @@ if [ "$UNAME" = "Darwin" ]; then
     export MACOSX_VERSION=`uname -r | awk -F. '{print $1}'`
     # Work around problems on recent OS X crashing with an error message
     # "... may have been in progress in another thread when fork() was called"
-    # when objective-C functions are called after fork(). See Trac #25921.
+    # when objective-C functions are called after fork(). See Issue #25921.
     # Most likely, these errors are false positives, so we disable them:
     export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES
 fi
@@ -449,7 +449,7 @@ if [ -n "$SAGE_LOCAL" ]; then
     PERL5LIB="$SAGE_LOCAL/lib/perl5:$PERL5LIB" && export PERL5LIB
 fi
 
-# Allow SAGE_BROWSER to override BROWSER (Trac #22449)
+# Allow SAGE_BROWSER to override BROWSER (Issue #22449)
 if [ -n "$SAGE_BROWSER" ]; then
     export BROWSER="$SAGE_BROWSER"
 fi
@@ -558,7 +558,7 @@ case "$SAGE_NUM_THREADS,$SAGE_NUM_THREADS_PARALLEL" in
         # sage-num-threads.py would just recompute them
         ;;
     *)
-        # See Trac Ticket #12016
+        # See Issue Ticket #12016
         # First, figure out the right values for SAGE_NUM_THREADS (default
         # number of threads) and SAGE_NUM_THREADS_PARALLEL (default number of
         # threads when parallel execution is asked explicitly).
@@ -615,7 +615,7 @@ fi
 
 if [ -n "$SAGE_LOCAL" ]; then
     # If we move the Sage tree then ncurses cannot find terminfo, hence, we
-    # tell it where to find it. See Trac Ticket #15091
+    # tell it where to find it. See Issue Ticket #15091
     export TERMINFO="$SAGE_LOCAL/share/terminfo"
 
     # If nodejs is installed, activate the nodeenv containing it.

src/bin/sage-runtests

@@ -8,7 +8,7 @@ import sys
 DOT_SAGE = os.environ.get('DOT_SAGE', os.path.join(os.environ.get('HOME'),
                                                    '.sage'))
 
-# Override to not pick up user configuration, see Trac #20270
+# Override to not pick up user configuration, see Issue #20270
 os.environ['SAGE_STARTUP_FILE'] = os.path.join(DOT_SAGE, 'init-doctests.sage')
 
 
@@ -141,7 +141,7 @@ if __name__ == "__main__":
         sys.exit(2)
 
     # Limit the number of threads to 2 to save system resources.
-    # See Trac #23713, #23892, #30351
+    # See Issue #23713, #23892, #30351
     if sys.platform == 'darwin':
         os.environ["OMP_NUM_THREADS"] = "1"
     else:
@@ -153,7 +153,7 @@ if __name__ == "__main__":
     DC = DocTestController(args, args.filenames)
     err = DC.run()
 
-    # Trac #33521: Do not run pytest if the pytest configuration is not available.
+    # Issue #33521: Do not run pytest if the pytest configuration is not available.
     # This happens when the source tree is not available and SAGE_SRC falls back
     # to SAGE_LIB.
     from sage.env import SAGE_SRC

src/conftest.py

@@ -25,7 +25,7 @@
 from _pytest.pathlib import import_path, ImportMode
 
 # Import sage.all is necessary to:
-# - avoid cyclic import errors, see Trac #33580
+# - avoid cyclic import errors, see Issue #33580
 # - inject it into globals namespace for doctests
 import sage.all
 from sage.doctest.parsing import SageDocTestParser, SageOutputChecker

src/doc/en/developer/advanced_git.rst

@@ -11,8 +11,8 @@ Advanced Git
     **Sage development is scheduled to move to GitHub in February 2023.** The exact
     date will be announced in `<https://groups.google.com/g/sage-devel>`_. After
     the transition, some parts of this guide (especially those related with `the
-    Sage Trac server <https://trac.sagemath.org>`_) will become obsolete and be
-    updated according to the new workflow on GitHub. See our `transition guide from Trac to
+    Sage Issue server <https://trac.sagemath.org>`_) will become obsolete and be
+    updated according to the new workflow on GitHub. See our `transition guide from Issue to
     GitHub
     <https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md>`_
     for the preliminary version of the workflow.

src/doc/en/developer/git_trac.rst

@@ -3,16 +3,16 @@
 .. _chapter-git_trac:
 
 ====================================
-Optional: Using the Git-Trac Command
+Optional: Using the Git-Issue Command
 ====================================
 
 .. WARNING::
 
     **Sage development is scheduled to move to GitHub in February 2023.** The exact
     date will be announced in `<https://groups.google.com/g/sage-devel>`_. After
     the transition, some parts of this guide (especially those related with `the
-    Sage Trac server <https://trac.sagemath.org>`_) will become obsolete and be
-    updated according to the new workflow on GitHub. See our `transition guide from Trac to
+    Sage Issue server <https://trac.sagemath.org>`_) will become obsolete and be
+    updated according to the new workflow on GitHub. See our `transition guide from Issue to
     GitHub
     <https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md>`_
     for the preliminary version of the workflow.
@@ -25,7 +25,7 @@ perform every development task with just git and a web browser.
 
 .. _section-git_trac-install:
 
-Installing the Git-Trac Command
+Installing the Git-Issue Command
 ===============================
 
 ::
@@ -58,7 +58,7 @@ there whenever you need to update the ``git-trac`` command.
 
 .. _section-git_trac-setup:
 
-Git and Trac Configuration
+Git and Issue Configuration
 ==========================
 
 .. NOTE::
@@ -75,7 +75,7 @@ authentication mechanism is needed. To set up ``git trac``, first go
 to the Sage directory and tell ``git trac`` about your trac account::
 
     [user@localhost sage]$ git trac config --user USERNAME --pass 'PASSWORD'
-    Trac xmlrpc URL:
+    Issue xmlrpc URL:
         https://trac.sagemath.org/xmlrpc (anonymous)
         https://trac.sagemath.org/login/xmlrpc (authenticated)
         realm sage.math.washington.edu
@@ -98,8 +98,8 @@ a generated token by passing ``--token=<token>`` instead of ``--pass``::
 
     [user@localhost sage]$ git trac config --user=<username> --token=<token>
 
-This is required if you authenticate to Trac with your GitHub account, as
-you do not have a Trac password.  Logged in users can find their token
+This is required if you authenticate to Issue with your GitHub account, as
+you do not have a Issue password.  Logged in users can find their token
 under :trac:`the token tab in preferences on the trac site <prefs/token>`.
 
 .. NOTE::
@@ -142,7 +142,7 @@ secured with SSH keys, which you must have set up as in
 fetch url and does not require SSH.
 
 
-Trac Tickets and Git Branches
+Issue Tickets and Git Branches
 =============================
 
 Now let's start adding code to Sage!
@@ -191,7 +191,7 @@ local branch to make your edits, you would just run::
 
     [user@localhost sage]$ git trac checkout 12345
     Loading ticket #12345...
-    Checking out Trac #13744 remote branch u/user/last_twin_prime -> local branch t/12345/last_twin_prime...
+    Checking out Issue #13744 remote branch u/user/last_twin_prime -> local branch t/12345/last_twin_prime...
 
 The ``git trac checkout`` command downloads an existing branch (as
 specified in the "Branch:" field on the trac ticket) or creates a new
@@ -250,7 +250,7 @@ someone and want to share your changes "up until now". This is simply
 done by::
 
     [user@localhost sage]$ git trac push
-    Pushing to Trac #12345...
+    Pushing to Issue #12345...
     Guessed remote branch: u/user/last_twin_prime
 
     To git@trac.sagemath.org:sage.git

src/doc/en/developer/index.rst

@@ -9,8 +9,8 @@ Welcome to the Sage Developer's Guide!
     **Sage development is scheduled to move to GitHub in February 2023.** The exact
     date will be announced in `<https://groups.google.com/g/sage-devel>`_. After
     the transition, some parts of this guide (especially those related with `the
-    Sage Trac server <https://trac.sagemath.org>`_) will become obsolete and be
-    updated according to the new workflow on GitHub. See our `transition guide from Trac to
+    Sage Issue server <https://trac.sagemath.org>`_) will become obsolete and be
+    updated according to the new workflow on GitHub. See our `transition guide from Issue to
     GitHub
     <https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md>`_
     for the preliminary version of the workflow.
@@ -35,7 +35,7 @@ Here are brief overviews of each part; for more details, see the extended table
 of contents below.  No matter where you start, good luck and welcome to Sage
 development!
 
-- **Trac server:** all changes go through `the Sage Trac server
+- **Issue server:** all changes go through `the Sage Issue server
   <https://trac.sagemath.org>`_ at some point. It contains bug reports, upgrade
   requests, changes in progress, and those already part of Sage
   today. :ref:`Click here <chapter-sage-trac>` for more information.
@@ -74,7 +74,7 @@ development!
   - :ref:`How to configure it for use with Trac? <section-git-setup-name>`
   - :ref:`Here is <chapter-walkthrough>` an overview of our development flow.
 
-Git and Trac for Sage development
+Git and Issue for Sage development
 =================================
 
 First Steps with Git

src/doc/en/developer/manual_git.rst

@@ -3,16 +3,16 @@
 .. _chapter-manual-git:
 
 ===================================
-Using Git with the Sage Trac Server
+Using Git with the Sage Issue Server
 ===================================
 
 .. WARNING::
 
     **Sage development is scheduled to move to GitHub in February 2023.** The exact
     date will be announced in `<https://groups.google.com/g/sage-devel>`_. After
     the transition, some parts of this guide (especially those related with `the
-    Sage Trac server <https://trac.sagemath.org>`_) will become obsolete and be
-    updated according to the new workflow on GitHub. See our `transition guide from Trac to
+    Sage Issue server <https://trac.sagemath.org>`_) will become obsolete and be
+    updated according to the new workflow on GitHub. See our `transition guide from Issue to
     GitHub
     <https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md>`_
     for the preliminary version of the workflow.
@@ -102,7 +102,7 @@ passphrase empty to be able to login without any human intervention.
 
 .. _section-trac-ssh-key:
 
-Linking your Public Key to your Trac Account
+Linking your Public Key to your Issue Account
 --------------------------------------------
 
 In order to push your code directly to a branch on the git repository
@@ -199,7 +199,7 @@ changes and ``git push`` to upload your local changes using::
 
 Note that write operations (``push``) use the ssh protocol (specified by the ``git@``
 part). For this to work, you need to have a trac account and to set up your ssh public
-key as described in `Trac authentication through ssh
+key as described in `Issue authentication through ssh
 <http://doc.sagemath.org/html/en/developer/trac.html#trac-authentication-through-ssh>`_.
 Authentication is necessary if you want to upload anything to ensure
 that it really is from you.

src/doc/en/developer/packaging.rst

@@ -628,7 +628,7 @@ The comments may include links to Github issues, as in the following example:
 
     $ cat build/pkgs/packaging/install-requires.txt
     packaging >=18.0
-    # Trac #30975: packaging 20.5 is known to work but we have to silence "DeprecationWarning: Creating a LegacyVersion"
+    # Issue #30975: packaging 20.5 is known to work but we have to silence "DeprecationWarning: Creating a LegacyVersion"
 
 The currently encoded version constraints are merely a starting point.
 Developers and downstream packagers are invited to refine the version
@@ -1079,7 +1079,7 @@ For Python packages available from PyPI, there is another shortcut::
     [...............................................................]
 
 The ``upstream_url`` information serves yet another purpose.
-Developers who wish to test a package update from a Trac branch before
+Developers who wish to test a package update from a Issue branch before
 the archive is available on a Sage mirror can do so by configuring
 their Sage tree using ``./configure
 --enable-download-from-upstream-url``.  Then Sage will fall back to

src/doc/en/developer/reviewer_checklist.rst

@@ -11,8 +11,8 @@ The reviewer's check list
     **Sage development is scheduled to move to GitHub in February 2023.** The exact
     date will be announced in `<https://groups.google.com/g/sage-devel>`_. After
     the transition, some parts of this guide (especially those related with `the
-    Sage Trac server <https://trac.sagemath.org>`_) will become obsolete and be
-    updated according to the new workflow on GitHub. See our `transition guide from Trac to
+    Sage Issue server <https://trac.sagemath.org>`_) will become obsolete and be
+    updated according to the new workflow on GitHub. See our `transition guide from Issue to
     GitHub
     <https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md>`_
     for the preliminary version of the workflow.
@@ -133,6 +133,6 @@ For more advice on reviewing, see [WSblog]_.
 
 REFERENCES:
 
-.. [WSblog] William Stein, How to Referee Sage Trac Tickets,
+.. [WSblog] William Stein, How to Referee Sage Issue Tickets,
    http://sagemath.blogspot.com/2010/10/how-to-referee-sage-trac-tickets.html
    (Caveat: mercurial was replaced with git)

src/doc/en/developer/sage_manuals.rst

@@ -107,7 +107,7 @@ by Sage, you can link toward it without specifying its full path:
    :widths: 4 4 4
    :header-rows: 0
 
-   * - Trac server
+   * - Issue server
      - ``:trac:`17596```
      - :trac:`17596`
 

src/doc/en/developer/trac.rst

@@ -3,16 +3,16 @@
 .. _chapter-sage-trac:
 
 ====================
-The Sage Trac Server
+The Sage Issue Server
 ====================
 
 .. WARNING::
 
     **Sage development is scheduled to move to GitHub in February 2023.** The exact
     date will be announced in `<https://groups.google.com/g/sage-devel>`_. After
     the transition, some parts of this guide (especially those related with `the
-    Sage Trac server <https://trac.sagemath.org>`_) will become obsolete and be
-    updated according to the new workflow on GitHub. See our `transition guide from Trac to
+    Sage Issue server <https://trac.sagemath.org>`_) will become obsolete and be
+    updated according to the new workflow on GitHub. See our `transition guide from Issue to
     GitHub
     <https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md>`_
     for the preliminary version of the workflow.
@@ -22,7 +22,7 @@ your own private needs.  However, typically it is beneficial to
 share code and ideas with others; the manner in which the
 `Sage project <https://www.sagemath.org>`_ does this (as well as fixing
 bugs and upgrading components) is in a very collaborative and
-public setting on `the Sage Trac server <https://trac.sagemath.org>`_
+public setting on `the Sage Issue server <https://trac.sagemath.org>`_
 (the Sage bug and enhancement tracker).
 
 The purpose of the Sage trac server is to
@@ -47,7 +47,7 @@ the :trac:`Sage trac timeline <timeline>`.
 .. WARNING::
 
     **Sage development is scheduled to move to GitHub in February 2023.**
-    All functions of our Trac server will be taken over by our main repository,
+    All functions of our Issue server will be taken over by our main repository,
     https://github.com/sagemath/sage.
 
 
@@ -173,7 +173,7 @@ of fields that can be changed. Here is a comprehensive overview (for the
 * **Reported by:** The trac account name of whoever created the
   ticket. Cannot be changed.
 
-* **Owned by:** Trac account name of owner, by default the person in charge of
+* **Owned by:** Issue account name of owner, by default the person in charge of
   the Component (see below). Generally not used in the Sage trac.
 
 * **Type:** One of ``enhancement`` (e.g. a new feature), ``defect`` (e.g. a bug