Remove or update bitbucket links (GH-101963)

Since Mercurial removal from bitbucket.org, some links are broken.
They are replaced by github.com or webarchive.org links if available. Otherwise, they are removed.

Co-authored-by: Shantanu <12621235+hauntsaninja@users.noreply.github.com>

diff --git a/Doc/distributing/index.rst b/Doc/distributing/index.rst
index 2ae2726d4e4b92ae967192a60d3e79e42845588a..21389adedf9c154e9b0f9920a86cceb68dbf9cf7 100644 (file)
--- a/Doc/distributing/index.rst
+++ b/Doc/distributing/index.rst
@@ -39,8 +39,7 @@ Key terms
   developers and documentation authors responsible for the maintenance and
   evolution of the standard packaging tools and the associated metadata and
   file format standards. They maintain a variety of tools, documentation
-  and issue trackers on both `GitHub <https://github.com/pypa>`__ and
-  `Bitbucket <https://bitbucket.org/pypa/>`__.
+  and issue trackers on `GitHub <https://github.com/pypa>`__.
 * ``distutils`` is the original build and distribution system first added
   to the Python standard library in 1998. While direct use of ``distutils``
   is being phased out, it still laid the foundation for the current packaging

diff --git a/Doc/installing/index.rst b/Doc/installing/index.rst
index e158bf1c4c0c7f59ecb706389c59b54f5263efed..5aec5178d48f3df2c4ec08c28fef18a31977e9cc 100644 (file)
--- a/Doc/installing/index.rst
+++ b/Doc/installing/index.rst
@@ -52,8 +52,7 @@ Key terms
   developers and documentation authors responsible for the maintenance and
   evolution of the standard packaging tools and the associated metadata and
   file format standards. They maintain a variety of tools, documentation,
-  and issue trackers on both `GitHub <https://github.com/pypa>`__ and
-  `Bitbucket <https://bitbucket.org/pypa/>`__.
+  and issue trackers on `GitHub <https://github.com/pypa>`__.
 * ``distutils`` is the original build and distribution system first added to
   the Python standard library in 1998. While direct use of ``distutils`` is
   being phased out, it still laid the foundation for the current packaging

diff --git a/Doc/library/venv.rst b/Doc/library/venv.rst
index 2a41096de006b80c873aeabae3adb9f3ef50e827..8eb0b35eaa12df6850b2810fc04b17557a2040bf 100644 (file)
--- a/Doc/library/venv.rst
+++ b/Doc/library/venv.rst
@@ -478,7 +478,7 @@ subclass which installs setuptools and pip into a created virtual environment::
             :param context: The information for the virtual environment
                             creation request being processed.
             """
-            url = 'https://bitbucket.org/pypa/setuptools/downloads/ez_setup.py'
+            url = "https://bootstrap.pypa.io/ez_setup.py"
             self.install_script(context, 'setuptools', url)
             # clear up the setuptools archive which gets downloaded
             pred = lambda o: o.startswith('setuptools-') and o.endswith('.tar.gz')

diff --git a/Lib/test/test_pathlib.py b/Lib/test/test_pathlib.py
index df9c1f6ba65deb5ea78f0f3ab8b3fbe9950826ba..f8e2f44d27fc1ef269d456b9f8aace5b9e046610 100644 (file)
--- a/Lib/test/test_pathlib.py
+++ b/Lib/test/test_pathlib.py
@@ -1938,7 +1938,7 @@ class _BasePathTest(object):
 
     @os_helper.skip_unless_symlink
     def test_resolve_dot(self):
-        # See https://bitbucket.org/pitrou/pathlib/issue/9/pathresolve-fails-on-complex-symlinks
+        # See http://web.archive.org/web/20200623062557/https://bitbucket.org/pitrou/pathlib/issues/9/
         p = self.cls(BASE)
         self.dirlink('.', join('0'))
         self.dirlink(os.path.join('0', '0'), join('1'))

diff --git a/PC/launcher.c b/PC/launcher.c
index da566a180168c5d80104e68b3595f140c4ba989f..0776e57249c427b5ec073a7a50ade2c8c8eeffce 100644 (file)
--- a/PC/launcher.c
+++ b/PC/launcher.c
@@ -770,8 +770,7 @@ run_child(wchar_t * cmdline)
     window, or fetching a message).  As this launcher doesn't do this
     directly, that cursor remains even after the child process does these
     things.  We avoid that by doing a simple post+get message.
-    See http://bugs.python.org/issue17290 and
-    https://bitbucket.org/vinay.sajip/pylauncher/issue/20/busy-cursor-for-a-long-time-when-running
+    See http://bugs.python.org/issue17290
     */
     MSG msg;
 

diff --git a/PC/launcher2.c b/PC/launcher2.c
index beeb2ae46b83f049a55bd5d1857f7466a31e9203..932665387f196661f73226bf006dcb71a9f70f77 100644 (file)
--- a/PC/launcher2.c
+++ b/PC/launcher2.c
@@ -2473,8 +2473,7 @@ launchEnvironment(const SearchInfo *search, const EnvironmentInfo *launch, wchar
     window, or fetching a message).  As this launcher doesn't do this
     directly, that cursor remains even after the child process does these
     things.  We avoid that by doing a simple post+get message.
-    See http://bugs.python.org/issue17290 and
-    https://bitbucket.org/vinay.sajip/pylauncher/issue/20/busy-cursor-for-a-long-time-when-running
+    See http://bugs.python.org/issue17290
     */
     MSG msg;