Add https

Author: dstansby

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/

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:
 

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

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.
 

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.
 

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/

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

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

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

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::