Add https

matplotlib · NelleV · Dec 31, 2016 · Dec 27, 2016 · Dec 27, 2016 · Dec 27, 2016
commit 6ec29e6a6b2a84eeb0c8e4546fc7ac66bbcb231a
diff --git a/doc/devel/MEP/MEP12.rst b/doc/devel/MEP/MEP12.rst
@@ -141,8 +141,8 @@ page instead of the gallery examples.
 references to that example.  For example, the API documentation for
 `axes.py` and `pyplot.py` may use these examples to generate
 plots. Use your favorite search tool (e.g., grep, ack, `grin
-<http://pypi.python.org/pypi/grin>`_, `pss
-<http://pypi.python.org/pypi/pss>`_) to search the matplotlib
+<https://pypi.python.org/pypi/grin>`_, `pss
+<https://pypi.python.org/pypi/pss>`_) to search the matplotlib
 package. See `2dc9a46
 <https://github.com/tonysyu/matplotlib/commit/2dc9a4651e5e566afc0866c603aa8d06aaf32b71>`_
 and `aa6b410
@@ -192,10 +192,10 @@ the entry point to these examples, and sections could really help users
 navigate the gallery. Thus, tags are complementary to this reorganization.
 
 
-.. _PEP8: http://www.python.org/dev/peps/pep-0008/
+.. _PEP8: https://www.python.org/dev/peps/pep-0008/
 
-.. [1] http://github.com/matplotlib/matplotlib/pull/714
-.. [2] http://github.com/matplotlib/matplotlib/issues/524
+.. [1] https://github.com/matplotlib/matplotlib/pull/714
+.. [2] https://github.com/matplotlib/matplotlib/issues/524
 .. [3] http://matplotlib.1069221.n5.nabble.com/Matplotlib-gallery-td762.html#a33379091
 .. [4] http://www.loria.fr/~rougier/teaching/matplotlib/
 .. [5] http://www.loria.fr/~rougier/coding/gallery/
diff --git a/doc/devel/contributing.rst b/doc/devel/contributing.rst
@@ -70,10 +70,10 @@ You can then run the tests to check your work environment is set up properly::
 .. _pep8: https://pep8.readthedocs.io/en/latest/
 
 .. note::
-    
+
   **Additional dependencies for testing**: nose_ (version 1.0 or later), `mock
   <https://docs.python.org/dev/library/unittest.mock.html>`_ (if python < 3.3), `Ghostscript
-  <http://www.ghostscript.com/>`_, `Inkscape <http://inkscape.org>`_
+  <https://www.ghostscript.com/>`_, `Inkscape <https://inkscape.org>`_
 
 .. note:: To make sure the tests run locally:
 

diff --git a/doc/devel/documenting_mpl.rst b/doc/devel/documenting_mpl.rst
@@ -333,7 +333,7 @@ purposes, like hosting google docs or youtube videos.  You can embed a
 matplotlib animation in the docs by first saving the animation as a
 movie using :meth:`matplotlib.animation.Animation.save`, and then
 uploading to `matplotlib's youtube
-channel <http://www.youtube.com/user/matplotlib>`_ and inserting the
+channel <https://www.youtube.com/user/matplotlib>`_ and inserting the
 embedding string youtube provides like::
 
   .. raw:: html

diff --git a/doc/devel/gitwash/development_workflow.rst b/doc/devel/gitwash/development_workflow.rst
@@ -125,7 +125,7 @@ sure your pull request is ready for merging.
 
 
 #. Go to your repo URL |emdash| e.g.,
-   ``http://github.com/your-user-name/matplotlib``.
+   ``https://github.com/your-user-name/matplotlib``.
 
 #. Select your feature branch from the drop down menu:
 
@@ -162,7 +162,7 @@ all your commits to the updated upstream commit. For a much more detailed
 explanation (with pictures!) see `this nice write up
 <https://git-scm.com/book/en/Git-Branching-Rebasing>`_.  The NumPy team has also
 `documented how to do this
-<http://docs.scipy.org/doc/numpy/dev/gitwash/development_workflow.html#rebasing-on-master>`_.
+<https://docs.scipy.org/doc/numpy/dev/gitwash/development_workflow.html#rebasing-on-master>`_.
 In general, re-writing history, particularly published history, is considered
 bad practice, but in this case it is very useful.
 

diff --git a/doc/devel/gitwash/forking_hell.rst b/doc/devel/gitwash/forking_hell.rst
@@ -5,7 +5,7 @@ Making your own copy (fork) of matplotlib
 ==========================================
 
 You need to do this only once.  The instructions here are very similar
-to the instructions at http://help.github.com/forking/ |emdash| please see
+to the instructions at https://help.github.com/forking/ |emdash| please see
 that page for more detail.  We're repeating some of it here just to give the
 specifics for the matplotlib_ project, and to suggest some default names.
 

diff --git a/doc/devel/gitwash/git_links.inc b/doc/devel/gitwash/git_links.inc
@@ -9,19 +9,19 @@
    nipy, NIPY, Nipy, etc...
 
 .. git stuff
-.. _git: http://git-scm.com/
-.. _github: http://github.com
-.. _github help: http://help.github.com
+.. _git: https://git-scm.com/
+.. _github: https://github.com
+.. _github help: https://help.github.com
 .. _msysgit: http://code.google.com/p/msysgit/downloads/list
 .. _git-osx-installer: http://code.google.com/p/git-osx-installer/downloads/list
 .. _subversion: http://subversion.tigris.org/
-.. _git cheat sheet: http://github.com/guides/git-cheat-sheet
+.. _git cheat sheet: https://github.com/guides/git-cheat-sheet
 .. _pro git book: http://progit.org/
-.. _git svn crash course: http://git-scm.com/course/svn.html
+.. _git svn crash course: https://git-scm.com/course/svn.html
 .. _learn.github: http://learn.github.com/
-.. _network graph visualizer: http://github.com/blog/39-say-hello-to-the-network-graph-visualizer
-.. _git user manual: http://schacon.github.com/git/user-manual.html
-.. _git tutorial: http://schacon.github.com/git/gittutorial.html
+.. _network graph visualizer: https://github.com/blog/39-say-hello-to-the-network-graph-visualizer
+.. _git user manual: https://schacon.github.com/git/user-manual.html
+.. _git tutorial: https://schacon.github.com/git/gittutorial.html
 .. _git community book: https://git-scm.com/book/en/v2
 .. _git ready: http://www.gitready.com/
 .. _git casts: http://www.gitcasts.com/

diff --git a/doc/devel/gitwash/known_projects.inc b/doc/devel/gitwash/known_projects.inc
@@ -2,40 +2,40 @@
 
 .. PROJECTNAME placeholders
 .. _PROJECTNAME: http://neuroimaging.scipy.org
-.. _`PROJECTNAME github`: http://github.com/nipy
+.. _`PROJECTNAME github`: https://github.com/nipy
 .. _`PROJECTNAME mailing list`: http://projects.scipy.org/mailman/listinfo/nipy-devel
 
 .. numpy
 .. _numpy: hhttp://numpy.scipy.org
-.. _`numpy github`: http://github.com/numpy/numpy
+.. _`numpy github`: https://github.com/numpy/numpy
 .. _`numpy mailing list`: http://mail.scipy.org/mailman/listinfo/numpy-discussion
 
 .. scipy
 .. _scipy: http://www.scipy.org
-.. _`scipy github`: http://github.com/scipy/scipy
+.. _`scipy github`: https://github.com/scipy/scipy
 .. _`scipy mailing list`: http://mail.scipy.org/mailman/listinfo/scipy-dev
 
 .. nipy
 .. _nipy: http://nipy.org/nipy
-.. _`nipy github`: http://github.com/nipy/nipy
+.. _`nipy github`: https://github.com/nipy/nipy
 .. _`nipy mailing list`: http://mail.scipy.org/mailman/listinfo/nipy-devel
 
 .. ipython
 .. _ipython: http://ipython.org
-.. _`ipython github`: http://github.com/ipython/ipython
+.. _`ipython github`: https://github.com/ipython/ipython
 .. _`ipython mailing list`: http://mail.scipy.org/mailman/listinfo/IPython-dev
 
 .. dipy
 .. _dipy: http://nipy.org/dipy
-.. _`dipy github`: http://github.com/Garyfallidis/dipy
+.. _`dipy github`: https://github.com/Garyfallidis/dipy
 .. _`dipy mailing list`: http://mail.scipy.org/mailman/listinfo/nipy-devel
 
 .. nibabel
 .. _nibabel: http://nipy.org/nibabel
-.. _`nibabel github`: http://github.com/nipy/nibabel
+.. _`nibabel github`: https://github.com/nipy/nibabel
 .. _`nibabel mailing list`: http://mail.scipy.org/mailman/listinfo/nipy-devel
 
 .. marsbar
 .. _marsbar: http://marsbar.sourceforge.net
-.. _`marsbar github`: http://github.com/matthew-brett/marsbar
+.. _`marsbar github`: https://github.com/matthew-brett/marsbar
 .. _`MarsBaR mailing list`: https://lists.sourceforge.net/lists/listinfo/marsbar-users
diff --git a/doc/devel/gitwash/this_project.inc b/doc/devel/gitwash/this_project.inc
@@ -1,5 +1,5 @@
 .. matplotlib
 .. _matplotlib: http://matplotlib.org
-.. _`matplotlib github`: http://github.com/matplotlib/matplotlib
+.. _`matplotlib github`: https://github.com/matplotlib/matplotlib
 
 .. _`matplotlib mailing list`: https://mail.python.org/mailman/listinfo/matplotlib-devel
diff --git a/doc/devel/license.rst b/doc/devel/license.rst
@@ -6,7 +6,7 @@ Licenses
 Matplotlib only uses BSD compatible code.  If you bring in code from
 another project make sure it has a PSF, BSD, MIT or compatible license
 (see the Open Source Initiative `licenses page
-<http://opensource.org/licenses>`_ for details on individual
+<https://opensource.org/licenses>`_ for details on individual
 licenses).  If it doesn't, you may consider contacting the author and
 asking them to relicense it.  GPL and LGPL code are not acceptable in
 the main code base, though we are considering an alternative way of
@@ -57,7 +57,7 @@ compatible).  Also, we wanted to attract as many users and developers
 as possible, and many software companies will not use GPL code in
 software they plan to distribute, even those that are highly committed
 to open source development, such as `enthought
-<http://enthought.com>`_, out of legitimate concern that use of the
+<https://www.enthought.com>`_, out of legitimate concern that use of the
 GPL will "infect" their code base by its viral nature. In effect, they
 want to retain the right to release some proprietary code. Companies
 and institutions who use matplotlib often make significant

diff --git a/doc/devel/release_guide.rst b/doc/devel/release_guide.rst
@@ -100,7 +100,7 @@ releases, since doing so will hide any available stable releases.
 
 You may need to set up your `.pypirc` file as described in the
 `distutils register command documentation
-<http://docs.python.org/2/distutils/packageindex.html>`_.
+<https://docs.python.org/2/distutils/packageindex.html>`_.
 
 Then updating the record on PyPI is as simple as::
 

diff --git a/doc/devel/testing.rst b/doc/devel/testing.rst
@@ -20,9 +20,9 @@ The following software is required to run the tests:
   - nose_, version 1.0 or later
   - `mock <https://docs.python.org/dev/library/unittest.mock.html>`_, when running python
     versions < 3.3
-  - `Ghostscript <http://www.ghostscript.com/>`_ (to render PDF
+  - `Ghostscript <https://www.ghostscript.com/>`_ (to render PDF
     files)
-  - `Inkscape <http://inkscape.org>`_ (to render SVG files)
+  - `Inkscape <https://inkscape.org>`_ (to render SVG files)
 
 Optionally you can install:
 
@@ -236,7 +236,7 @@ this module to the list of default tests, append its name to
 Using Travis CI
 ---------------
 
-`Travis CI <http://travis-ci.org/>`_ is a hosted CI system "in the
+`Travis CI <https://travis-ci.org/>`_ is a hosted CI system "in the
 cloud".
 
 Travis is configured to receive notifications of new commits to GitHub
@@ -259,7 +259,7 @@ generally isn't necessary, since any pull request submitted against
 the main matplotlib repository will be tested.
 
 Once this is configured, you can see the Travis CI results at
-http://travis-ci.org/your_GitHub_user_name/matplotlib -- here's `an
+https://travis-ci.org/your_GitHub_user_name/matplotlib -- here's `an
 example <https://travis-ci.org/msabramo/matplotlib>`_.
 
 

diff --git a/doc/faq/howto_faq.rst b/doc/faq/howto_faq.rst
@@ -585,7 +585,7 @@ compiling matplotlib for windows?  Write a FAQ or a section for the
 Write a tutorial on the signal analysis plotting functions like
 :func:`~matplotlib.pyplot.xcorr`, :func:`~matplotlib.pyplot.psd` and
 :func:`~matplotlib.pyplot.specgram`.  Do you use matplotlib with
-`django <http://www.djangoproject.com/>`_ or other popular web
+`django <https://www.djangoproject.com/>`_ or other popular web
 application servers?  Write a FAQ or tutorial and we'll find a place
 for it in the :ref:`users-guide-index`.  Bundle matplotlib in a
 `py2exe <http://www.py2exe.org/>`_ app?  ... I think you get the idea.

diff --git a/doc/faq/installing_faq.rst b/doc/faq/installing_faq.rst
@@ -186,7 +186,7 @@ Canopy web pages for more information.
 Other options for a fresh Python install are the standard installer from
 `python.org <https://www.python.org/downloads/mac-osx/>`_, or installing
 Python using a general OSX package management system such as `homebrew
-<http://brew.sh>`_ or `macports <http://www.macports.org>`_.  Power users on
+<http://brew.sh>`_ or `macports <https://www.macports.org>`_.  Power users on
 OSX will likely want one of homebrew or macports on their system to install
 open source software packages, but it is perfectly possible to use these
 systems with another source for your Python binary, such as Anaconda, Canopy
@@ -197,7 +197,7 @@ or Python.org Python.
 Installing OSX binary wheels
 ----------------------------
 
-If you are using recent Python from http://www.python.org, Macports or
+If you are using recent Python from https://www.python.org, Macports or
 Homebrew, then you can use the standard pip installer to install matplotlib
 binaries in the form of wheels.
 

diff --git a/doc/faq/osx_framework.rst b/doc/faq/osx_framework.rst
@@ -104,7 +104,7 @@ build within the virtual environment you can do ``frameworkpython -m IPython``
 ^^^^^^^^^^^^^^^^^^^^^
 
 An alternative work around borrowed from the `WX wiki
-<http://wiki.wxpython.org/wxPythonVirtualenvOnMac>`_, is to use the non
+<https://wiki.wxpython.org/wxPythonVirtualenvOnMac>`_, is to use the non
 virtualenv python along with the PYTHONHOME environment variable.  This can be
 implemented in a script as below. To use this modify ``PYVER`` and
 ``PATHTOPYTHON`` and put the script in the virtualenv bin directory i.e.

diff --git a/doc/faq/troubleshooting_faq.rst b/doc/faq/troubleshooting_faq.rst
@@ -167,7 +167,7 @@ simple test script in debug mode::
 
 and post :file:`build.out` and :file:`run.out` to the
 `matplotlib-devel
-<http://mail.python.org/mailman/listinfo/matplotlib-devel>`_
+<https://mail.python.org/mailman/listinfo/matplotlib-devel>`_
 mailing list (please do not post git problems to the `users list
 <https://mail.python.org/mailman/listinfo/matplotlib-users>`_).
 

diff --git a/doc/faq/usage_faq.rst b/doc/faq/usage_faq.rst
@@ -376,8 +376,8 @@ For example, with GTK, you can also select GDK rendering (backend
 ``GTK`` deprecated in 2.0) or Cairo rendering (backend ``GTKCairo``).
 
 For the rendering engines, one can also distinguish between `vector
-<http://en.wikipedia.org/wiki/Vector_graphics>`_ or `raster
-<http://en.wikipedia.org/wiki/Raster_graphics>`_ renderers.  Vector
+<https://en.wikipedia.org/wiki/Vector_graphics>`_ or `raster
+<https://en.wikipedia.org/wiki/Raster_graphics>`_ renderers.  Vector
 graphics languages issue drawing commands like "draw a line from this
 point to this point" and hence are scale free, and raster backends
 generate a pixel representation of the line whose accuracy depends on a
@@ -441,19 +441,19 @@ macosx         Cocoa rendering in OSX windows
 ============   ================================================================
 
 .. _`Anti-Grain Geometry`: http://antigrain.com/
-.. _Postscript: http://en.wikipedia.org/wiki/PostScript
-.. _`Portable Document Format`: http://en.wikipedia.org/wiki/Portable_Document_Format
-.. _`Scalable Vector Graphics`: http://en.wikipedia.org/wiki/Scalable_Vector_Graphics
-.. _`Cairo graphics`: http://en.wikipedia.org/wiki/Cairo_(graphics)
-.. _`Gimp Drawing Kit`: http://en.wikipedia.org/wiki/GDK
+.. _Postscript: https://en.wikipedia.org/wiki/PostScript
+.. _`Portable Document Format`: https://en.wikipedia.org/wiki/Portable_Document_Format
+.. _`Scalable Vector Graphics`: https://en.wikipedia.org/wiki/Scalable_Vector_Graphics
+.. _`Cairo graphics`: https://en.wikipedia.org/wiki/Cairo_(graphics)
+.. _`Gimp Drawing Kit`: https://en.wikipedia.org/wiki/GDK
 .. _PyGTK: http://www.pygtk.org
 .. _PyGObject: https://live.gnome.org/PyGObject
-.. _pycairo: http://www.cairographics.org/pycairo/
+.. _pycairo: https://www.cairographics.org/pycairo/
 .. _cairocffi: https://pythonhosted.org/cairocffi/
-.. _wxPython: http://www.wxpython.org/
-.. _TkInter: http://wiki.python.org/moin/TkInter
-.. _PyQt4: http://www.riverbankcomputing.co.uk/software/pyqt/intro
-.. _PyQt5: http://www.riverbankcomputing.co.uk/software/pyqt/intro
+.. _wxPython: https://www.wxpython.org/
+.. _TkInter: https://wiki.python.org/moin/TkInter
+.. _PyQt4: https://riverbankcomputing.com/software/pyqt/intro
+.. _PyQt5: https://riverbankcomputing.com/software/pyqt/intro
 
 WX backends
 ===========