i heard you like https, so i https your http

.editorconfig

@@ -1,4 +1,4 @@
-# http://editorconfig.org
+# https://editorconfig.org
 
 root = true
 

.github/CODE_OF_CONDUCT.md

@@ -71,7 +71,7 @@ will be treated with the strictest confidence) or talking privately with
 the person.
 
 Parts of this code of conduct have been adapted from the
-[astropy](http://www.astropy.org/code_of_conduct.html) and the [Python
+[astropy](https://www.astropy.org/code_of_conduct.html) and the [Python
 Software Fundation](https://www.python.org/psf/codeofconduct/) codes of
 conduct.
 

.github/pull_request_template.md

@@ -7,7 +7,7 @@ We have old closed pull requests that might provide useful code or ideas that di
 
 <!-- We have several automatic features that run when a pull request is open.
 They can appear daunting but do not worry about them!
-We have a brief explanation of them in the documentation, http://docs.sunpy.org/en/latest/dev_guide/pr_review_procedure.html#continuous-integration. -->
+We have a brief explanation of them in the documentation, https://docs.sunpy.org/en/latest/dev_guide/pr_review_procedure.html#continuous-integration. -->
 
 ### Description
 <!-- Provide a general description of what your pull request does. -->

CHANGELOG.rst

@@ -643,7 +643,7 @@ Bug fixes
 -  Add support for ANA data.
 -  Updated sun.constants to use astropy.constants objects which include
    units, source, and error instide. For more info check out
-   http://docs.astropy.org/en/latest/constants/index.html
+   https://docs.astropy.org/en/latest/constants/index.html
 -  Add some beta support for IRIS data products
 -  Add a new MapCubeAnimator class with interactive widgets which is
    returned by mapcube.peek().

CODE_OF_CONDUCT.rst

@@ -47,7 +47,7 @@ Overall, we are good to each other and apply this code of conduct to all communi
 We pledge to help the entire community follow the code of conduct, and to not remain silent when we see violations of the code of conduct.
 We will take action when members of our community violate this code such as contacting [email protected] (all emails sent to this address will be treated with the strictest confidence) or talking privately with the person.
 
-Parts of this code of conduct have been adapted from the `astropy <http://www.astropy.org/code_of_conduct.html>`__ and the `Python Software Fundation <https://www.python.org/psf/codeofconduct/>`__ codes of conduct.
+Parts of this code of conduct have been adapted from the `astropy <https://www.astropy.org/code_of_conduct.html>`__ and the `Python Software Fundation <https://www.python.org/psf/codeofconduct/>`__ codes of conduct.
 
 ----
 

CONTRIBUTING.rst

@@ -124,9 +124,9 @@ Setting up a development environment
 
 The instructions in this following section are based upon three resources:
 
-* `Astropy Dev Workflow <http://docs.astropy.org/en/latest/development/workflow/development_workflow.html>`_
-* `Astropy Dev environment <http://docs.astropy.org/en/latest/development/workflow/get_devel_version.html#get-devel>`_
-* `Astropy Pull Request Example <http://docs.astropy.org/en/latest/development/workflow/git_edit_workflow_examples.html#astropy-fix-example>`_
+* `Astropy Dev Workflow <https://docs.astropy.org/en/latest/development/workflow/development_workflow.html>`_
+* `Astropy Dev environment <https://docs.astropy.org/en/latest/development/workflow/get_devel_version.html#get-devel>`_
+* `Astropy Pull Request Example <https://docs.astropy.org/en/latest/development/workflow/git_edit_workflow_examples.html#astropy-fix-example>`_
 
 **We strongly recommend that you read these links.**
 These links are more in-depth than this guide but you will need to replace ``astropy`` with ``sunpy``.

README.rst

@@ -23,7 +23,7 @@ Our homepage `SunPy`_ has more information about the project.
 For some examples of using SunPy see our `gallery`_, to see the latest changes in SunPy see our `Changelog`_.
 
 .. _SunPy: https://sunpy.org
-.. _gallery: http://docs.sunpy.org/en/stable/generated/gallery/index.html
+.. _gallery: https://docs.sunpy.org/en/stable/generated/gallery/index.html
 .. _Changelog: https://docs.sunpy.org/en/latest/whatsnew/changelog.html
 
 Installation
@@ -40,7 +40,7 @@ To install SunPy once conda is installed run the following two commands:
 For detailed installation instructions, see the `installation guide`_ in the SunPy docs.
 
 .. _conda: https://www.anaconda.com/distribution/
-.. _installation guide: http://docs.sunpy.org/en/latest/guide/installation/index.html
+.. _installation guide: https://docs.sunpy.org/en/latest/guide/installation/index.html
 
 Developing
 ==========
@@ -105,7 +105,7 @@ For more information on contributing to SunPy, please read our `Newcomers guide`
    :target: https://www.codetriage.com/sunpy/sunpy
 
 .. _SunPy mailing list: https://groups.google.com/forum/#!forum/sunpy
-.. _Developers Guide: http://docs.sunpy.org/en/latest/dev_guide/index.html
+.. _Developers Guide: https://docs.sunpy.org/en/latest/dev_guide/index.html
 .. _`#sunpy:openastronomy.org`: https://chat.openastronomy.org/#/room/#sunpy:openastronomy.org
 .. _issues page: https://github.com/sunpy/sunpy/issues
 .. _Newcomers guide: https://docs.sunpy.org/en/latest/dev_guide/newcomers.html

ah_bootstrap.py

@@ -835,7 +835,7 @@ def run_cmd(cmd):
     except ValueError:
         # Due to an OSX oddity locale.getdefaultlocale() can also crash
         # depending on the user's locale/language settings.  See:
-        # http://bugs.python.org/issue18378
+        # https://bugs.python.org/issue18378
         stdio_encoding = 'latin1'
 
     # Unlikely to fail at this point but even then let's be flexible

changelog/2366.feature.rst

@@ -1 +1 @@
-asdf schemas and tags were added for the SunPy coordinate frames and `~sunpy.map.GenericMap` allowing these objects to be saved to and restored from `asdf <http://asdf.readthedocs.io/>`__ files.
+asdf schemas and tags were added for the SunPy coordinate frames and `~sunpy.map.GenericMap` allowing these objects to be saved to and restored from `asdf <https://asdf.readthedocs.io/>`__ files.

docs/code_ref/coordinates.rst

@@ -121,7 +121,7 @@ Both `~astropy.coordinates.SkyCoord` and
 `~astropy.coordinates.SkyCoord.transform_to` method. This can be used to
 transform the frame to any other frame, either implemented in SunPy or in
 Astropy `the astropy documentation
-<http://docs.astropy.org/en/stable/coordinates/transforming.html>`_ for more
+<https://docs.astropy.org/en/stable/coordinates/transforming.html>`_ for more
 details. An example of transforming the center of the solar disk to Carrington
 coordinates is::
 

docs/conf.py

@@ -126,10 +126,10 @@
 
 # Add any custom intersphinx for SunPy
 intersphinx_mapping.pop('h5py', None)
-intersphinx_mapping['sqlalchemy'] = ('http://docs.sqlalchemy.org/en/latest/', None)
-intersphinx_mapping['pandas'] = ('http://pandas.pydata.org/pandas-docs/stable/', None)
-intersphinx_mapping['skimage'] = ('http://scikit-image.org/docs/stable/', None)
-intersphinx_mapping['drms'] = ('http://docs.sunpy.org/projects/drms/en/stable/', None)
+intersphinx_mapping['sqlalchemy'] = ('https://docs.sqlalchemy.org/en/latest/', None)
+intersphinx_mapping['pandas'] = ('https://pandas.pydata.org/pandas-docs/stable/', None)
+intersphinx_mapping['skimage'] = ('https://scikit-image.org/docs/stable/', None)
+intersphinx_mapping['drms'] = ('https://docs.sunpy.org/projects/drms/en/stable/', None)
 intersphinx_mapping['parfive'] = ('https://parfive.readthedocs.io/en/latest/', None)
 
 # List of patterns, relative to source directory, that match files and
@@ -145,16 +145,16 @@
 linkcheck_ignore = [r"https://doi.org/\d+",
                     r"https://riot.im/\d+",
                     r"https://github.com/\d+",
-                    r"http://docs.sunpy.org/\d+"]
+                    r"https://docs.sunpy.org/\d+"]
 linkcheck_anchors = False
 
 # This is added to the end of RST files - a good place to put substitutions to
 # be used globally.
 rst_epilog = """
 .. SunPy
-.. _SunPy: http://sunpy.org
-.. _`SunPy mailing list`: http://groups.google.com/group/sunpy
-.. _`SunPy dev mailing list`: http://groups.google.com/group/sunpy-dev
+.. _SunPy: https://sunpy.org
+.. _`SunPy mailing list`: https://groups.google.com/group/sunpy
+.. _`SunPy dev mailing list`: https://groups.google.com/group/sunpy-dev
 """
 
 # -- Project information ------------------------------------------------------
@@ -265,12 +265,6 @@ def rstjinja(app, docname, source):
                                            (os.path.join('..', 'examples/computer_vision_techniques'))]),
         'gallery_dirs': path.joinpath('generated', 'gallery'),  # path to save gallery generated examples
         'default_thumb_file': path.joinpath('logo', 'sunpy_icon_128x128.png'),
-        'reference_url': {
-            'sunpy': None,
-            'astropy': 'http://docs.astropy.org/en/stable/',
-            'matplotlib': 'https://matplotlib.org/',
-            'numpy': 'http://docs.scipy.org/doc/numpy/',
-        },
         'abort_on_example_error': True,
         'plot_gallery': True
     }
@@ -291,9 +285,10 @@ def rstjinja(app, docname, source):
 
 def setup(app):
     if not has_sphinx_gallery:
-        app.warn('The sphinx_gallery extension is not installed, so the '
-                 'gallery will not be built. You will probably see '
-                 'additional warnings about undefined references due '
-                 'to this.')
+        import warnings
+        warnings.warn('The sphinx_gallery extension is not installed, so the '
+                      'gallery will not be built. You will probably see '
+                      'additional warnings about undefined references due '
+                      'to this.')
     if has_yaml:
         app.connect("source-read", rstjinja)

docs/dev_guide/code_standards.rst

@@ -8,7 +8,7 @@ The purpose of the page is to describe the standards that are expected of all th
 All potential developers should read and abide by the following standards.
 Code which does not follow these standards closely will not be accepted.
 
-We try to closely follow the coding style and conventions proposed by `Astropy <http://docs.astropy.org/en/stable/development/codeguide.html#coding-style-conventions>`_.
+We try to closely follow the coding style and conventions proposed by `Astropy <https://docs.astropy.org/en/stable/development/codeguide.html#coding-style-conventions>`_.
 
 Language Standard
 =================

docs/dev_guide/documentation.rst

@@ -10,7 +10,7 @@ Overview
 All code must be documented and we follow these style conventions described here:
 
 * `numpydoc <https://numpydoc.readthedocs.io/en/latest/format.html#docstring-standard>`_
-* `astropy <http://docs.astropy.org/en/latest/development/docrules.html>`_
+* `astropy <https://docs.astropy.org/en/latest/development/docrules.html>`_
 
 We recommend having a read of these and unless stated overwise, we stick to these standards.
 
@@ -38,7 +38,7 @@ SunPy Specific Rules
 Sphinx
 ======
 
-All of the SunPy documentation (like this page) is built by `Sphinx <http://www.sphinx-doc.org/en/stable/>`_, which is a tool especially well-suited for documenting Python projects.
+All of the SunPy documentation (like this page) is built by `Sphinx <https://www.sphinx-doc.org/en/stable/>`_, which is a tool especially well-suited for documenting Python projects.
 Sphinx works by parsing files written using a `a Mediawiki-like syntax <http://docutils.sourceforge.net/docs/user/rst/quickstart.html>`_ called `reStructuredText <http://docutils.sourceforge.net/rst.html>`_.
 In addition to parsing static files of reStructuredText, Sphinx can also be told to parse code comments.
 In fact, in addition to what you are reading right now, the `Python documentation <https://www.python.org/doc/>`_ was also created using Sphinx.

docs/dev_guide/example_gallery.rst

@@ -4,7 +4,7 @@
 Example Gallery
 ***************
 
-The purpose of the page is to describe the contribution guidelines for the `SunPy Example Gallery <http://docs.sunpy.org/en/stable/generated/gallery/index.html>`_.
+The purpose of the page is to describe the contribution guidelines for the `SunPy Example Gallery <https://docs.sunpy.org/en/stable/generated/gallery/index.html>`_.
 
 All potential contributors to the SunPy Example Gallery should read and abide by the following guidelines.
 

docs/dev_guide/maintainer_workflow.rst

@@ -8,7 +8,7 @@ This page is for maintainers who can merge our own or other peoples' changes int
 
 Seeing as how you're a maintainer, you should be completely on top of the basic git workflow in :ref:`newcomers` and Astropy's `git workflow`_.
 
-.. _git workflow: http://docs.astropy.org/en/stable/development/workflow/development_workflow.html#development-workflow
+.. _git workflow: https://docs.astropy.org/en/stable/development/workflow/development_workflow.html#development-workflow
 
 Integrating changes via the web interface (recommended)
 =======================================================
@@ -167,7 +167,7 @@ These guidelines are adapted from `guidelines`_ followed by astropy:
 
 * Issues that require fixing in master, but that also are confirmed to apply to supported stable version lines should be marked with a "Affects Release" label and the corresponding supported stable version label "v0.4.x".
 
-.. _guidelines: :http://docs.astropy.org/en/stable/development/workflow/maintainer_workflow.html#using-milestones-and-labels
+.. _guidelines: :https://docs.astropy.org/en/stable/development/workflow/maintainer_workflow.html#using-milestones-and-labels
 
 Using Projects
 ==============

docs/dev_guide/tests.rst

@@ -5,7 +5,7 @@ Testing Guidelines
 ******************
 
 This section describes the testing framework and format standards for tests in SunPy.
-Here we have heavily adapted the `Astropy version <http://docs.astropy.org/en/latest/development/testguide.html>`_, and **it is worth reading that link.**
+Here we have heavily adapted the `Astropy version <https://docs.astropy.org/en/latest/development/testguide.html>`_, and **it is worth reading that link.**
 
 Testing Framework
 =================
@@ -309,7 +309,7 @@ Writing Doctests
 ----------------
 
 Code examples in the documentation will also be run as tests and this helps to validate that the documentation is accurate and up to date.
-SunPy uses the same system as Astropy, so for information on writing doctests see the astropy `documentation <http://docs.astropy.org/en/latest/development/testguide.html#writing-doctests>`_.
+SunPy uses the same system as Astropy, so for information on writing doctests see the astropy `documentation <https://docs.astropy.org/en/latest/development/testguide.html#writing-doctests>`_.
 
 You do not have to do anything extra in order to run any documentation tests.
 Within our ``setup.cfg`` file we have set default options for ``pytest``, such that you only need to run::

docs/dev_guide/units_quantities.rst

@@ -7,14 +7,14 @@ Use of quantities and units
 ***************************
 
 Much code perform calculations using physical quantities.
-SunPy uses astropy's `quantities and units <http://docs.astropy.org/en/stable/units/index.html>`_ implementation to store, express and convert physical quantities.
+SunPy uses astropy's `quantities and units <https://docs.astropy.org/en/stable/units/index.html>`_ implementation to store, express and convert physical quantities.
 New classes and functions should adhere to SunPy's `quantity and unit usage guidelines
 <https://github.com/sunpy/sunpy-SEP/blob/master/SEP-0003.md>`_.
 
 This document sets out SunPy's reasons and requirements for the usage of quantities and units.
 Briefly, SunPy's `policy <https://github.com/sunpy/sunpy-SEP/blob/master/SEP-0003.md>`_ is that *all user-facing function/object arguments which accept physical quantities as input **MUST** accept astropy quantities, and **ONLY** astropy quantities*.
 
-Developers should consult the `Astropy Quantities and Units page <http://docs.astropy.org/en/stable/units/index.html>`_ for the latest updates on using quantities and units.  The `astropy tutorial on quantities and units <http://www.astropy.org/astropy-tutorials/Quantities.html>`_ also provides useful examples on their
+Developers should consult the `Astropy Quantities and Units page <https://docs.astropy.org/en/stable/units/index.html>`_ for the latest updates on using quantities and units.  The `astropy tutorial on quantities and units <https://www.astropy.org/astropy-tutorials/Quantities.html>`_ also provides useful examples on their
 capabilities.
 
 Astropy provides the decorator `~astropy.units.quantity_input` that checks the units of the input arguments to a function against the expected units of the argument.

docs/guide/acquiring_data/database.rst

@@ -13,7 +13,7 @@ via the :mod:`sunpy.net` package) onto a local or remote database. The
 database may be a single file located on a local hard drive (if a SQLite
 database is used) or a local or remote database server (see the SQLAlchemy
 documentation for a `list of supported databases
-<http://docs.sqlalchemy.org/en/latest/dialects/index.html>`_)
+<https://docs.sqlalchemy.org/en/latest/dialects/index.html>`_)
 This makes it possible to fetch required data from the local database
 instead of downloading it again from a remote server.
 

docs/guide/acquiring_data/helioviewer.rst

@@ -2,7 +2,7 @@
 Querying Helioviewer.org with SunPy
 -----------------------------------
 
-SunPy can be used to make several basic requests using the The `Helioviewer.org API <https://api.helioviewer.org/docs/v2/>`_ including generating a PNG screenshot and downloading a `JPEG 2000 <http://wiki.helioviewer.org/wiki/JPEG_2000>`_ image.
+SunPy can be used to make several basic requests using the The `Helioviewer.org API <https://api.helioviewer.org/docs/v2/>`_ including generating a PNG screenshot and downloading a `JPEG 2000 <https://wiki.helioviewer.org/wiki/JPEG_2000>`_ image.
 
 As you can get JPEG 2000 images, you will need two other pieces of software in order to open them in Python.
 The first is OpenJPEG which is an open source library for reading and writing JPEG2000 files.

docs/guide/acquiring_data/jsoc.rst

@@ -7,7 +7,7 @@ as well as certain other missions and instruments. These data are available from
 which can be directly accessed by the online `JSOC interface <http://jsoc.stanford.edu/ajax/lookdata.html>`_.
 
 SunPy's JSOC Client provides an easier interface to query for JSOC data and make export requests.
-It uses `drms module <http://docs.sunpy.org/projects/drms>`_ as its backend, and exposes a similar API as
+It uses `drms module <https://docs.sunpy.org/projects/drms>`_ as its backend, and exposes a similar API as
 the VSO Client.
 
 There are two ways of downloading JSOC data. One way is using Sunpy's unified search interface,

docs/guide/bugs.rst

@@ -8,7 +8,7 @@ lists first: it is possible that someone else has already run into
 your problem.
 
 If not, please provide the following information in your e-mail to the
-`mailing list <http://groups.google.com/forum/#!forum/sunpy>`_:
+`mailing list <https://groups.google.com/forum/#!forum/sunpy>`_:
 
   * your operating system; (Linux/UNIX users: post the output of ``uname -a``)
 

docs/guide/data_types/maps.rst

@@ -305,7 +305,7 @@ data from minimum to maximum is displayed as best as possible for most cases.
 This means that it is never necessary to touch the data such as applying a function
 such sqrt or log to the data to make your plot look good.
 There are many normalizations available from matplotlib such as `~matplotlib.colors.Lognorm`. Other
-`more exotic normalizations <http://docs.astropy.org/en/stable/visualization/index.html>`_ are also
+`more exotic normalizations <https://docs.astropy.org/en/stable/visualization/index.html>`_ are also
 made available from Astropy.  Just like the colormap the default normalization
 can be changed through the plot_settings dictionary or directly for the individual
 plot by passing a keyword argument. The following example shows the difference between