--- a/env/lib/python3.7/site-packages/configparser-5.0.0.dist-info/METADATA	Thu May 14 16:47:39 2020 -0400
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,266 +0,0 @@
-Metadata-Version: 2.1
-Name: configparser
-Version: 5.0.0
-Summary: Updated configparser from Python 3.8 for Python 2.6+.
-Home-page: https://github.com/jaraco/configparser/
-Author: Łukasz Langa
-Author-email: lukasz@langa.pl
-Maintainer: Jason R. Coombs
-Maintainer-email: jaraco@jaraco.com
-License: UNKNOWN
-Keywords: configparser ini parsing conf cfg configuration file
-Platform: any
-Classifier: Development Status :: 5 - Production/Stable
-Classifier: Intended Audience :: Developers
-Classifier: License :: OSI Approved :: MIT License
-Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3 :: Only
-Requires-Python: >=3.6
-Provides-Extra: docs
-Requires-Dist: sphinx ; extra == 'docs'
-Requires-Dist: jaraco.packaging (>=3.2) ; extra == 'docs'
-Requires-Dist: rst.linker (>=1.9) ; extra == 'docs'
-Provides-Extra: testing
-Requires-Dist: pytest (!=3.7.3,>=3.5) ; extra == 'testing'
-Requires-Dist: pytest-checkdocs (>=1.2.3) ; extra == 'testing'
-Requires-Dist: pytest-flake8 ; extra == 'testing'
-Requires-Dist: pytest-black-multipy ; extra == 'testing'
-Requires-Dist: pytest-cov ; extra == 'testing'
-
-.. image:: https://img.shields.io/pypi/v/configparser.svg
-   :target: `PyPI link`_
-
-.. image:: https://img.shields.io/pypi/pyversions/configparser.svg
-   :target: `PyPI link`_
-
-.. _PyPI link: https://pypi.org/project/configparser
-
-.. image:: https://dev.azure.com/jaraco/configparser/_apis/build/status/jaraco.configparser?branchName=master
-   :target: https://dev.azure.com/jaraco/configparser/_build/latest?definitionId=1&branchName=master
-
-.. image:: https://img.shields.io/travis/jaraco/configparser/master.svg
-   :target: https://travis-ci.org/jaraco/configparser
-
-.. image:: https://img.shields.io/badge/code%20style-black-000000.svg
-   :target: https://github.com/psf/black
-   :alt: Code style: Black
-
-.. .. image:: https://img.shields.io/appveyor/ci/jaraco/configparser/master.svg
-..    :target: https://ci.appveyor.com/project/jaraco/configparser/branch/master
-
-.. image:: https://readthedocs.org/projects/configparser/badge/?version=latest
-   :target: https://configparser.readthedocs.io/en/latest/?badge=latest
-
-.. image:: https://tidelift.com/badges/package/pypi/configparser
-   :target: https://tidelift.com/subscription/pkg/pypi-configparser?utm_source=pypi-configparser&utm_medium=readme
-
-
-The ancient ``ConfigParser`` module available in the standard library 2.x has
-seen a major update in Python 3.2. This is a backport of those changes so that
-they can be used directly in Python 2.6 - 3.5.
-
-To use the ``configparser`` backport instead of the built-in version on both
-Python 2 and Python 3, simply import it explicitly as a backport::
-
-  from backports import configparser
-
-If you'd like to use the backport on Python 2 and the built-in version on
-Python 3, use that invocation instead::
-
-  import configparser
-
-For detailed documentation consult the vanilla version at
-http://docs.python.org/3/library/configparser.html.
-
-Why you'll love ``configparser``
---------------------------------
-
-Whereas almost completely compatible with its older brother, ``configparser``
-sports a bunch of interesting new features:
-
-* full mapping protocol access (`more info
-  <http://docs.python.org/3/library/configparser.html#mapping-protocol-access>`_)::
-
-    >>> parser = ConfigParser()
-    >>> parser.read_string("""
-    [DEFAULT]
-    location = upper left
-    visible = yes
-    editable = no
-    color = blue
-
-    [main]
-    title = Main Menu
-    color = green
-
-    [options]
-    title = Options
-    """)
-    >>> parser['main']['color']
-    'green'
-    >>> parser['main']['editable']
-    'no'
-    >>> section = parser['options']
-    >>> section['title']
-    'Options'
-    >>> section['title'] = 'Options (editable: %(editable)s)'
-    >>> section['title']
-    'Options (editable: no)'
-
-* there's now one default ``ConfigParser`` class, which basically is the old
-  ``SafeConfigParser`` with a bunch of tweaks which make it more predictable for
-  users. Don't need interpolation? Simply use
-  ``ConfigParser(interpolation=None)``, no need to use a distinct
-  ``RawConfigParser`` anymore.
-
-* the parser is highly `customizable upon instantiation
-  <http://docs.python.org/3/library/configparser.html#customizing-parser-behaviour>`__
-  supporting things like changing option delimiters, comment characters, the
-  name of the DEFAULT section, the interpolation syntax, etc.
-
-* you can easily create your own interpolation syntax but there are two powerful
-  implementations built-in (`more info
-  <http://docs.python.org/3/library/configparser.html#interpolation-of-values>`__):
-
-  * the classic ``%(string-like)s`` syntax (called ``BasicInterpolation``)
-
-  * a new ``${buildout:like}`` syntax (called ``ExtendedInterpolation``)
-
-* fallback values may be specified in getters (`more info
-  <http://docs.python.org/3/library/configparser.html#fallback-values>`__)::
-
-    >>> config.get('closet', 'monster',
-    ...            fallback='No such things as monsters')
-    'No such things as monsters'
-
-* ``ConfigParser`` objects can now read data directly `from strings
-  <http://docs.python.org/3/library/configparser.html#configparser.ConfigParser.read_string>`__
-  and `from dictionaries
-  <http://docs.python.org/3/library/configparser.html#configparser.ConfigParser.read_dict>`__.
-  That means importing configuration from JSON or specifying default values for
-  the whole configuration (multiple sections) is now a single line of code. Same
-  goes for copying data from another ``ConfigParser`` instance, thanks to its
-  mapping protocol support.
-
-* many smaller tweaks, updates and fixes
-
-A few words about Unicode
--------------------------
-
-``configparser`` comes from Python 3 and as such it works well with Unicode.
-The library is generally cleaned up in terms of internal data storage and
-reading/writing files.  There are a couple of incompatibilities with the old
-``ConfigParser`` due to that. However, the work required to migrate is well
-worth it as it shows the issues that would likely come up during migration of
-your project to Python 3.
-
-The design assumes that Unicode strings are used whenever possible [1]_.  That
-gives you the certainty that what's stored in a configuration object is text.
-Once your configuration is read, the rest of your application doesn't have to
-deal with encoding issues. All you have is text [2]_. The only two phases when
-you should explicitly state encoding is when you either read from an external
-source (e.g. a file) or write back.
-
-Versioning
-----------
-
-This project uses `semver <https://semver.org/spec/v2.0.0.html>`_ to
-communicate the impact of various releases while periodically syncing
-with the upstream implementation in CPython.
-`The changelog <https://github.com/jaraco/configparser/blob/master/CHANGES.rst>`_
-serves as a reference indicating which versions incorporate
-which upstream functionality.
-
-Prior to the ``4.0.0`` release, `another scheme
-<https://github.com/jaraco/configparser/blob/3.8.1/README.rst#versioning>`_
-was used to associate the CPython and backports releases.
-
-Maintenance
------------
-
-This backport was originally authored by Łukasz Langa, the current vanilla
-``configparser`` maintainer for CPython and is currently maintained by
-Jason R. Coombs:
-
-* `configparser repository <https://github.com/jaraco/configparser>`_
-
-* `configparser issue tracker <https://github.com/jaraco/configparser/issues>`_
-
-Security Contact
-----------------
-
-To report a security vulnerability, please use the
-`Tidelift security contact <https://tidelift.com/security>`_.
-Tidelift will coordinate the fix and disclosure.
-
-Conversion Process
-------------------
-
-This section is technical and should bother you only if you are wondering how
-this backport is produced. If the implementation details of this backport are
-not important for you, feel free to ignore the following content.
-
-``configparser`` is converted using `python-future
-<http://python-future.org>`_. The project takes the following
-branching approach:
-
-* the ``3.x`` branch holds unchanged files synchronized from the upstream
-  CPython repository. The synchronization is currently done by manually copying
-  the required files and stating from which CPython changeset they come from.
-
-* the ``master`` branch holds a version of the ``3.x`` code with some tweaks
-  that make it independent from libraries and constructions unavailable on 2.x.
-  Code on this branch still *must* work on the corresponding Python 3.x but
-  will also work on Python 2.6 and 2.7 (including PyPy).  You can check this
-  running the supplied unit tests with ``tox``.
-
-The process works like this:
-
-1. In the ``3.x`` branch, run ``pip-run -- sync-upstream.py``, which
-   downloads the latest stable release of Python and copies the relevant
-   files from there into their new locations here and then commits those
-   changes with a nice reference to the relevant upstream commit hash.
-
-2. I check for new names in ``__all__`` and update imports in
-   ``configparser.py`` accordingly. I run the tests on Python 3. Commit.
-
-3. I merge the new commit to ``master``. I run ``tox``. Commit.
-
-4. If there are necessary changes, I do them now (on ``master``). Note that
-   the changes should be written in the syntax subset supported by Python
-   2.6.
-
-5. I run ``tox``. If it works, I update the docs and release the new version.
-   Otherwise, I go back to point 3. I might use ``pasteurize`` to suggest me
-   required changes but usually I do them manually to keep resulting code in
-   a nicer form.
-
-
-Footnotes
----------
-
-.. [1] To somewhat ease migration, passing bytestrings is still supported but
-       they are converted to Unicode for internal storage anyway. This means
-       that for the vast majority of strings used in configuration files, it
-       won't matter if you pass them as bytestrings or Unicode. However, if you
-       pass a bytestring that cannot be converted to Unicode using the naive
-       ASCII codec, a ``UnicodeDecodeError`` will be raised. This is purposeful
-       and helps you manage proper encoding for all content you store in
-       memory, read from various sources and write back.
-
-.. [2] Life gets much easier when you understand that you basically manage
-       **text** in your application.  You don't care about bytes but about
-       letters.  In that regard the concept of content encoding is meaningless.
-       The only time when you deal with raw bytes is when you write the data to
-       a file.  Then you have to specify how your text should be encoded.  On
-       the other end, to get meaningful text from a file, the application
-       reading it has to know which encoding was used during its creation.  But
-       once the bytes are read and properly decoded, all you have is text.  This
-       is especially powerful when you start interacting with multiple data
-       sources.  Even if each of them uses a different encoding, inside your
-       application data is held in abstract text form.  You can program your
-       business logic without worrying about which data came from which source.
-       You can freely exchange the data you store between sources.  Only
-       reading/writing files requires encoding your text to bytes.
-
-