Docs: replace http links with https

Author: edschofield

README.rst

@@ -6,9 +6,6 @@ Overview: Easy, clean, reliable Python 2/3 compatibility
 .. image:: https://github.com/PythonCharmers/python-future/actions/workflows/ci.yml/badge.svg?branch=master
     :target: https://github.com/PythonCharmers/python-future/actions/workflows/ci.yml?query=branch%3Amaster
 
-.. image:: https://readthedocs.org/projects/python-future/badge/?version=latest
-    :target: https://python-future.readthedocs.io/en/latest/?badge=latest
-
 ``python-future`` is the missing compatibility layer between Python 2 and
 Python 3. It allows you to use a single, clean Python 3.x-compatible
 codebase to support both Python 2 and Python 3 with minimal overhead.
@@ -325,16 +322,19 @@ Licensing
 
            Pinterest https://opensource.pinterest.com
 
-:Licence: MIT. See ``LICENSE.txt`` or `here <http://python-future.org/credits.html>`_.
+:Licence: MIT. See ``LICENSE.txt`` or `here <https://python-future.org/credits.html>`_.
 
-:Other credits:  See `here <http://python-future.org/credits.html>`_.
+:Other credits:  See `here <https://python-future.org/credits.html>`_.
 
+Docs
+----
+See the docs `here <https://python-future.org>`.
 
 Next steps
 ----------
 
 If you are new to Python-Future, check out the `Quickstart Guide
-<http://python-future.org/quickstart.html>`_.
+<https://python-future.org/quickstart.html>`_.
 
 For an update on changes in the latest version, see the `What's New
-<http://python-future.org/whatsnew.html>`_ page.
+<https://python-future.org/whatsnew.html>`_ page.

docs/_templates/sidebarintro.html

@@ -1,7 +1,7 @@
 <!--<h3>Python-Future</h3>
 <p>-->
   <h4>Easy, clean, reliable Python 2/3 compatibility</h4>
-  <a href="http://python-future.org">Table of Contents</a>
+  <a href="https://python-future.org">Table of Contents</a>
 <!--
 </p>
 <h3>Other Formats</h3>

docs/compatible_idioms.rst

@@ -7,12 +7,12 @@ Cheat Sheet: Writing Python 2-3 compatible code
 -  **Author:** Ed Schofield.
 -  **Licence:** Creative Commons Attribution.
 
-A PDF version is here: http://python-future.org/compatible\_idioms.pdf
+A PDF version is here: https://python-future.org/compatible\_idioms.pdf
 
 This notebook shows you idioms for writing future-proof code that is
 compatible with both versions of Python: 2 and 3. It accompanies Ed
 Schofield's talk at PyCon AU 2014, "Writing 2/3 compatible code". (The
-video is here: http://www.youtube.com/watch?v=KOqk8j11aAI&t=10m14s.)
+video is here: https://www.youtube.com/watch?v=KOqk8j11aAI&t=10m14s.)
 
 Minimum versions:
 
@@ -38,7 +38,7 @@ The following scripts are also ``pip``-installable:
     futurize             # pip install future
     pasteurize           # pip install future
 
-See http://python-future.org and https://pythonhosted.org/six/ for more
+See https://python-future.org and https://pythonhosted.org/six/ for more
 information.
 
 Essential syntax differences
@@ -337,7 +337,7 @@ this idiom to make all string literals in a module unicode strings:
 
     s1 = 'The Zen of Python'
     s2 = 'きたないのよりきれいな方がいい\n'
-See http://python-future.org/unicode\_literals.html for more discussion
+See https://python-future.org/unicode\_literals.html for more discussion
 on which style to use.
 
 Byte-string literals

docs/faq.rst

@@ -8,7 +8,7 @@ Who is this for?
 ongoing Python 2.7 support easily and with little maintenance burden.
 
 2. People who wish to ease and accelerate migration of their Python 2 codebases
-to Python 3.4+, module by module, without giving up Python 2 compatibility.
+to Python 3.3+, module by module, without giving up Python 2 compatibility.
 
 
 Why upgrade to Python 3?
@@ -92,7 +92,7 @@ What inspired this project?
 ---------------------------
 
 In our Python training courses, we at `Python Charmers
-<http://pythoncharmers.com>`_ faced a dilemma: teach people Python 3, which was
+<https://pythoncharmers.com>`_ faced a dilemma: teach people Python 3, which was
 future-proof but not as useful to them today because of weaker 3rd-party
 package support, or teach people Python 2, which was more useful today but
 would require them to change their code and unlearn various habits soon. We

docs/notebooks/Writing Python 2-3 compatible code.ipynb

@@ -15,9 +15,9 @@
     "- **Author:** Ed Schofield.\n",
     "- **Licence:** Creative Commons Attribution.\n",
     "\n",
-    "A PDF version is here: http://python-future.org/compatible_idioms.pdf\n",
+    "A PDF version is here: https://python-future.org/compatible_idioms.pdf\n",
     "\n",
-    "This notebook shows you idioms for writing future-proof code that is compatible with both versions of Python: 2 and 3. It accompanies Ed Schofield's talk at PyCon AU 2014, \"Writing 2/3 compatible code\". (The video is here: <http://www.youtube.com/watch?v=KOqk8j11aAI&t=10m14s>.)\n",
+    "This notebook shows you idioms for writing future-proof code that is compatible with both versions of Python: 2 and 3. It accompanies Ed Schofield's talk at PyCon AU 2014, \"Writing 2/3 compatible code\". (The video is here: <https://www.youtube.com/watch?v=KOqk8j11aAI&t=10m14s>.)\n",
     "\n",
     "Minimum versions:\n",
     "\n",
@@ -48,7 +48,7 @@
     "    futurize             # pip install future\n",
     "    pasteurize           # pip install future\n",
     "\n",
-    "See http://python-future.org and https://pythonhosted.org/six/ for more information."
+    "See https://python-future.org and https://pythonhosted.org/six/ for more information."
    ]
   },
   {
@@ -756,7 +756,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "See http://python-future.org/unicode_literals.html for more discussion on which style to use."
+    "See https://python-future.org/unicode_literals.html for more discussion on which style to use."
    ]
   },
   {
@@ -2812,7 +2812,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "``urllib`` is the hardest module to use from Python 2/3 compatible code. You may like to use Requests (http://python-requests.org) instead."
+    "``urllib`` is the hardest module to use from Python 2/3 compatible code. You may like to use Requests (https://python-requests.org) instead."
    ]
   },
   {

src/future/__init__.py

@@ -52,7 +52,7 @@
 --------------------
 
 An included script called `futurize
-<http://python-future.org/automatic_conversion.html>`_ aids in converting
+<https://python-future.org/automatic_conversion.html>`_ aids in converting
 code (from either Python 2 or Python 3) to code compatible with both
 platforms. It is similar to ``python-modernize`` but goes further in
 providing Python 3 compatibility through the use of the backported types
@@ -62,15 +62,15 @@
 Documentation
 -------------
 
-See: http://python-future.org
+See: https://python-future.org
 
 
 Credits
 -------
 
 :Author:  Ed Schofield, Jordan M. Adler, et al
 :Sponsor: Python Charmers: https://pythoncharmers.com
-:Others:  See docs/credits.rst or http://python-future.org/credits.html
+:Others:  See docs/credits.rst or https://python-future.org/credits.html
 
 
 Licensing

src/future/builtins/__init__.py

@@ -2,7 +2,7 @@
 A module that brings in equivalents of the new and modified Python 3
 builtins into Py2. Has no effect on Py3.
 
-See the docs `here <http://python-future.org/what-else.html>`_
+See the docs `here <https://python-future.org/what-else.html>`_
 (``docs/what-else.rst``) for more information.
 
 """