[Python-checkins] devguide: make links to hg.python.org https
benjamin.peterson
python-checkins at python.org
Sun Sep 14 18:57:40 CEST 2014
http://hg.python.org/devguide/rev/dd01b6c1978f
changeset: 713:dd01b6c1978f
user: Benjamin Peterson <benjamin at python.org>
date: Sun Sep 14 12:57:24 2014 -0400
summary:
make links to hg.python.org https
files:
buildbots.rst | 4 +-
committing.rst | 8 ++--
communication.rst | 2 +-
coredev.rst | 6 +-
coverity.rst | 2 +-
docquality.rst | 4 +-
faq.rst | 6 +-
index.rst | 8 ++--
runtests.rst | 4 +-
setup.rst | 2 +-
triaging.rst | 58 +++++++++++++++++-----------------
11 files changed, 52 insertions(+), 52 deletions(-)
diff --git a/buildbots.rst b/buildbots.rst
--- a/buildbots.rst
+++ b/buildbots.rst
@@ -189,8 +189,8 @@
When creating ("forcing") a build on a custom builder, you have to provide
at least two parameters:
-* The repository path, relative to http://hg.python.org. For example,
- ``sandbox/myfixes`` if ``http://hg.python.org/sandbox/myfixes`` is the
+* The repository path, relative to https://hg.python.org. For example,
+ ``sandbox/myfixes`` if ``https://hg.python.org/sandbox/myfixes`` is the
full path to the repository.
* The Mercurial id of the changeset you want to build. To make things less
diff --git a/committing.rst b/committing.rst
--- a/committing.rst
+++ b/committing.rst
@@ -487,10 +487,10 @@
If you want to work on a feature long-term (perhaps you're implementing a
PEP), you will probably want to publish your work in a dedicated repository.
The following instructions will help you do so on `hg.python.org
-<http://hg.python.org>`_'s infrastructure without requiring a lot of upload
+<https://hg.python.org>`_'s infrastructure without requiring a lot of upload
bandwidth.
-Go to the main repository's Web page (http://hg.python.org/cpython/); there
+Go to the main repository's Web page (https://hg.python.org/cpython/); there
you find a button labelled "server-side clone", which you can click on to
display a Web form. Enter the relative path of the repository you want to
create on the server, for example ``features/mywork``; and press the button.
@@ -539,13 +539,13 @@
When you push them, they will land in the public repository at
``ssh://hg@hg.python.org/features/mywork`` (or
-``http://hg.python.org/features/mywork`` for the read-only URL). Other
+``https://hg.python.org/features/mywork`` for the read-only URL). Other
people can clone the public repository and work on the code too.
When you want to synchronize with CPython's upstream changes, you can pull
from the main repository, either from its remote URL::
- $ hg pull http://hg.python.org/cpython
+ $ hg pull https://hg.python.org/cpython
or from a local clone that you may have on your disk (which is of course
faster)::
diff --git a/communication.rst b/communication.rst
--- a/communication.rst
+++ b/communication.rst
@@ -31,7 +31,7 @@
it will get redirected here.
Python-checkins_ sends out an email for every commit to Python's various
-repositories from http://hg.python.org. All core developers
+repositories from https://hg.python.org. All core developers
subscribe to this list and are known to reply to these emails to make comments
about various issues they catch in the commit. Replies get redirected to
python-dev.
diff --git a/coredev.rst b/coredev.rst
--- a/coredev.rst
+++ b/coredev.rst
@@ -25,7 +25,7 @@
able to commit them without supervision.
A complete list of core developer usernames can be found at
-http://hg.python.org/committers.txt. :ref:`developers` lists when and why
+https://hg.python.org/committers.txt. :ref:`developers` lists when and why
someone received commit privileges.
@@ -69,9 +69,9 @@
This should match your username on the issue tracker.
You can verify your commit access by looking at
-http://hg.python.org/committers.txt which lists all core developers by
+https://hg.python.org/committers.txt which lists all core developers by
username. If you want to practice, there is a `test repository
-<http://hg.python.org/test/>`_ where you can freely commit and push any
+<https://hg.python.org/test/>`_ where you can freely commit and push any
changes you like::
hg clone ssh://hg@hg.python.org/test/ hgtest
diff --git a/coverity.rst b/coverity.rst
--- a/coverity.rst
+++ b/coverity.rst
@@ -150,4 +150,4 @@
.. _Coverity Connect: http://scan5.coverity.com:8080/
-.. _coverity_model.c: http://hg.python.org/cpython/file/tip/Misc/coverity_model.c
+.. _coverity_model.c: https://hg.python.org/cpython/file/tip/Misc/coverity_model.c
diff --git a/docquality.rst b/docquality.rst
--- a/docquality.rst
+++ b/docquality.rst
@@ -76,12 +76,12 @@
are normally published within a day, on a schedule that may be different from
the main documentation.
-.. _separate repository: http://hg.python.org/devguide
+.. _separate repository: https://hg.python.org/devguide
.. _Python bug tracker: http://bugs.python.org
To clone the Developer's Guide::
- $ hg clone http://hg.python.org/devguide
+ $ hg clone https://hg.python.org/devguide
Core developers should use::
diff --git a/faq.rst b/faq.rst
--- a/faq.rst
+++ b/faq.rst
@@ -113,7 +113,7 @@
On the `issue tracker`_, most core developers will have the Python logo
appear next to their name.
-.. _full list of developers: http://hg.python.org/committers.txt
+.. _full list of developers: https://hg.python.org/committers.txt
What standards of behaviour are expected in these communication channels?
@@ -177,8 +177,8 @@
while the maintenance branch names (``2.7``, ``3.3``, etc) are mapped
directly.
-.. _git mirror: http://github.com/akheron/cpython
-.. _CPython repository: http://hg.python.org/cpython
+.. _git mirror: https://github.com/akheron/cpython
+.. _CPython repository: https://hg.python.org/cpython
Please only use this approach if you're already an experienced Git user and
don't require assistance with the specifics of version control commands. All
diff --git a/index.rst b/index.rst
--- a/index.rst
+++ b/index.rst
@@ -16,7 +16,7 @@
1. :ref:`Get the source code <checkout>`::
- hg clone http://hg.python.org/cpython
+ hg clone https://hg.python.org/cpython
2. :ref:`Build Python <compiling>`. On all platforms, install build
dependencies (such as compilers), then on :ref:`UNIX <unix-compiling>`::
@@ -147,8 +147,8 @@
* `Firefox search engine plug-in`_
* `Buildbot status`_
* Source code
- * `Browse online <http://hg.python.org/cpython/file/default/>`_
- * `Snapshot of py3k <http://hg.python.org/cpython/archive/default.tar.bz2>`_
+ * `Browse online <https://hg.python.org/cpython/file/default/>`_
+ * `Snapshot of py3k <https://hg.python.org/cpython/archive/default.tar.bz2>`_
* `Daily OS X installer <http://buildbot.python.org/daily-dmg/>`_
* PEPs_ (Python Enhancement Proposals)
* :doc:`faq`
@@ -214,7 +214,7 @@
.. _Buildbot status: http://python.org/dev/buildbot/
.. _Firefox search engine plug-in: http://www.python.org/dev/searchplugin/
-.. _Misc directory: http://hg.python.org/cpython/file/default/Misc
+.. _Misc directory: https://hg.python.org/cpython/file/default/Misc
.. _PEPs: http://www.python.org/dev/peps/
.. _python.org maintenance: http://python.org/dev/pydotorg/
.. _Python: http://www.python.org/
diff --git a/runtests.rst b/runtests.rst
--- a/runtests.rst
+++ b/runtests.rst
@@ -130,7 +130,7 @@
----------
Benchmarking is useful to test that a change does not degrade performance.
-`The Grand Unified Python Benchmark Suite <http://hg.python.org/benchmarks/>`_
+`The Grand Unified Python Benchmark Suite <https://hg.python.org/benchmarks/>`_
has a collection of benchmarks for all Python implementations. Documentation
about running the benchmarks is in the `README.txt
-<http://hg.python.org/benchmarks/file/tip/README.txt>`_ of the benchmarks repo.
+<https://hg.python.org/benchmarks/file/tip/README.txt>`_ of the benchmarks repo.
diff --git a/setup.rst b/setup.rst
--- a/setup.rst
+++ b/setup.rst
@@ -222,7 +222,7 @@
Windows
'''''''
-The `readme <http://hg.python.org/cpython/file/default/PCbuild/readme.txt>`_
+The `readme <https://hg.python.org/cpython/file/default/PCbuild/readme.txt>`_
included in the solution has more details, especially on what additional
software is required to build which parts of Python.
diff --git a/triaging.rst b/triaging.rst
--- a/triaging.rst
+++ b/triaging.rst
@@ -282,7 +282,7 @@
The issue tracker automatically translates the legacy svn revision
``<number>`` to its corresponding Mercurial changeset identifier.
* ``Dir/file.ext`` and ``Dir/file.ext:NNN`` generate links to files in the
- `Python source code repositories <http://hg.python.org/cpython/file/>`_,
+ `Python source code repositories <https://hg.python.org/cpython/file/>`_,
possibly linking to the line number specified after the ``:``.
* ``PEP <number>`` and ``PEP<number>`` link to the
:abbr:`PEP (Python Enhancement Proposal)` ``<number>``.
@@ -291,33 +291,33 @@
the Devguide, this page, and this section respectively.
-.. _CPython: http://hg.python.org/cpython/file/default/
-.. _Doc: http://hg.python.org/cpython/file/default/Doc/
-.. _Grammar: http://hg.python.org/cpython/file/default/Grammar/
-.. _Lib: http://hg.python.org/cpython/file/default/Lib/
-.. _Lib/lib2to3: http://hg.python.org/cpython/file/default/Lib/lib2to3/
-.. _Lib/ctypes: http://hg.python.org/cpython/file/default/Lib/ctypes/
-.. _Lib/distutils: http://hg.python.org/cpython/file/default/Lib/distutils/
-.. _Lib/doctest.py: http://hg.python.org/cpython/file/default/Lib/doctest.py
-.. _Lib/idlelib: http://hg.python.org/cpython/file/default/Lib/idlelib/
-.. _Lib/io.py: http://hg.python.org/cpython/file/default/Lib/io.py
-.. _Lib/re.py: http://hg.python.org/cpython/file/default/Lib/re.py
-.. _Lib/test: http://hg.python.org/cpython/file/default/Lib/test/
-.. _Lib/test/regrtest.py: http://hg.python.org/cpython/file/default/Lib/test/regrtest.py
-.. _Lib/test/support: http://hg.python.org/cpython/file/default/Lib/test/support/
-.. _Lib/tkinter: http://hg.python.org/cpython/file/default/Lib/tkinter/
-.. _Lib/unittest: http://hg.python.org/cpython/file/default/Lib/unittest/
-.. _Lib/xml: http://hg.python.org/cpython/file/default/Lib/xml/
-.. _Modules: http://hg.python.org/cpython/file/default/Modules/
-.. _Modules/_io: http://hg.python.org/cpython/file/default/Modules/_io/
-.. _Modules/_sre.c: http://hg.python.org/cpython/file/default/Modules/_sre.c
-.. _Objects: http://hg.python.org/cpython/file/default/Objects/
-.. _Objects/unicodeobject.c: http://hg.python.org/cpython/file/default/Objects/unicodeobject.c
-.. _Parser: http://hg.python.org/cpython/file/default/Parser/
-.. _Python: http://hg.python.org/cpython/file/default/Python/
-.. _Tools: http://hg.python.org/cpython/file/default/Tools/
-.. _Tools/demo: http://hg.python.org/cpython/file/default/Tools/demo/
-.. _benchmarks: http://hg.python.org/benchmarks/
-.. _Developer's guide: http://hg.python.org/devguide/
+.. _CPython: https://hg.python.org/cpython/file/default/
+.. _Doc: https://hg.python.org/cpython/file/default/Doc/
+.. _Grammar: https://hg.python.org/cpython/file/default/Grammar/
+.. _Lib: https://hg.python.org/cpython/file/default/Lib/
+.. _Lib/lib2to3: https://hg.python.org/cpython/file/default/Lib/lib2to3/
+.. _Lib/ctypes: https://hg.python.org/cpython/file/default/Lib/ctypes/
+.. _Lib/distutils: https://hg.python.org/cpython/file/default/Lib/distutils/
+.. _Lib/doctest.py: https://hg.python.org/cpython/file/default/Lib/doctest.py
+.. _Lib/idlelib: https://hg.python.org/cpython/file/default/Lib/idlelib/
+.. _Lib/io.py: https://hg.python.org/cpython/file/default/Lib/io.py
+.. _Lib/re.py: https://hg.python.org/cpython/file/default/Lib/re.py
+.. _Lib/test: https://hg.python.org/cpython/file/default/Lib/test/
+.. _Lib/test/regrtest.py: https://hg.python.org/cpython/file/default/Lib/test/regrtest.py
+.. _Lib/test/support: https://hg.python.org/cpython/file/default/Lib/test/support/
+.. _Lib/tkinter: https://hg.python.org/cpython/file/default/Lib/tkinter/
+.. _Lib/unittest: https://hg.python.org/cpython/file/default/Lib/unittest/
+.. _Lib/xml: https://hg.python.org/cpython/file/default/Lib/xml/
+.. _Modules: https://hg.python.org/cpython/file/default/Modules/
+.. _Modules/_io: https://hg.python.org/cpython/file/default/Modules/_io/
+.. _Modules/_sre.c: https://hg.python.org/cpython/file/default/Modules/_sre.c
+.. _Objects: https://hg.python.org/cpython/file/default/Objects/
+.. _Objects/unicodeobject.c: https://hg.python.org/cpython/file/default/Objects/unicodeobject.c
+.. _Parser: https://hg.python.org/cpython/file/default/Parser/
+.. _Python: https://hg.python.org/cpython/file/default/Python/
+.. _Tools: https://hg.python.org/cpython/file/default/Tools/
+.. _Tools/demo: https://hg.python.org/cpython/file/default/Tools/demo/
+.. _benchmarks: https://hg.python.org/benchmarks/
+.. _Developer's guide: https://hg.python.org/devguide/
.. _GSoC: http://code.google.com/soc/
.. _issue tracker: http://bugs.python.org
--
Repository URL: http://hg.python.org/devguide
More information about the Python-checkins
mailing list