Bump version in setup.py, run Python Black over it all and update THIRDPARTYLICENSES

Author: initialed85

THIRDPARTYLICENSES

@@ -1,4 +1,4 @@
-Start of 'THIRDPARTYLICENSES' generated by Python third_party_license_generator at 2021-04-23 12:42:37.743440
+Start of 'THIRDPARTYLICENSES' generated by Python third_party_license_generator at 2022-02-18 10:34:53.412274
 
 ----------------------------------------
 
@@ -37,7 +37,7 @@ Requires: n/a
 Author: Kenneth Reitz <me@kennethreitz.com>
 Home page: https://certifiio.readthedocs.io/en/latest/
 
-This packge contains a modified version of ca-bundle.crt:
+This package contains a modified version of ca-bundle.crt:
 
 ca-bundle.crt -- Bundle of CA Root Certificates
 
@@ -828,4 +828,4 @@ SOFTWARE.
 
 ----------------------------------------
 
-End of 'THIRDPARTYLICENSES' generated by Python third_party_license_generator at 2021-04-23 12:42:37.743523
+End of 'THIRDPARTYLICENSES' generated by Python third_party_license_generator at 2022-02-18 10:34:53.412320

setup.py

@@ -14,98 +14,74 @@
 here = path.abspath(path.dirname(__file__))
 
 # Get the long description from the README file
-with open(path.join(here, 'README.md'), encoding='utf-8') as f:
+with open(path.join(here, "README.md"), encoding="utf-8") as f:
     long_description = f.read()
 
 setup(
-    name='third-party-license-file-generator',
-
+    name="third-party-license-file-generator",
     # Versions should comply with PEP440.  For a discussion on single-sourcing
     # the version across setup.py and the project code, see
     # https://packaging.python.org/en/latest/single_source_version.html
-    version='2021.4.23',
-
+    version="2022.2.18",
     description='The Python third_party_license_file_generator is aimed at distilling down the appropriate license for one or many pip "requirements" files into a single file; it supports Python2.7 and Python3.',
     long_description=long_description,
-    long_description_content_type='text/markdown',
-
+    long_description_content_type="text/markdown",
     # The project's main homepage.
-    url='https://github.com/ftpsolutions/python-third-party-license-file-generator',
-
+    url="https://github.com/ftpsolutions/python-third-party-license-file-generator",
     # Author details
-    author='Edward Beech',
-    author_email='edward.beech@ftpsolutions.com.au',
-
+    author="Edward Beech",
+    author_email="edward.beech@ftpsolutions.com.au",
     # Choose your license
-    license='MIT',
-
+    license="MIT",
     # See https://pypi.python.org/pypi?%3Aaction=list_classifiers
     classifiers=[
         # How mature is this project? Common values are
         #   3 - Alpha
         #   4 - Beta
         #   5 - Production/Stable
-        'Development Status :: 3 - Alpha',
-
+        "Development Status :: 3 - Alpha",
         # Indicate who your project is intended for
-        'Intended Audience :: Developers',
-        'Topic :: Software Development :: Libraries',
-
+        "Intended Audience :: Developers",
+        "Topic :: Software Development :: Libraries",
         # Pick your license as you wish (should match "license" above)
-        'License :: OSI Approved :: MIT License',
-
+        "License :: OSI Approved :: MIT License",
         # Specify the Python versions you support here. In particular, ensure
         # that you indicate whether you support Python 2, Python 3 or both.
-        'Programming Language :: Python :: 2.7',
-        'Programming Language :: Python :: 3.6',
+        "Programming Language :: Python :: 2.7",
+        "Programming Language :: Python :: 3.6",
     ],
-
     # What does your project relate to?
-    keywords='sample setuptools development',
-
+    keywords="sample setuptools development",
     # You can just specify the packages manually here if your project is
     # simple. Or you can use find_packages().
-    packages=find_packages(exclude=['contrib', 'docs', 'tests']),
-
+    packages=find_packages(exclude=["contrib", "docs", "tests"]),
     # Alternatively, if you want to distribute just a my_module.py, uncomment
     # this:
     #   py_modules=["my_module"],
-
     # List run-time dependencies here.  These will be installed by pip when
     # your project is installed. For an analysis of "install_requires" vs pip's
     # requirements files see:
     # https://packaging.python.org/en/latest/requirements.html
-    install_requires=[
-        'requests>=2.25',
-        'PyYAML>=5.4'
-    ],
-
+    install_requires=["requests>=2.25", "PyYAML>=5.4"],
     # List additional groups of dependencies here (e.g. development
     # dependencies). You can install these using the following syntax,
     # for example:
     # $ pip install -e .[dev,test]
     extras_require={
-        'dev': ['check-manifest'],
-        'test': ['coverage'],
+        "dev": ["check-manifest"],
+        "test": ["coverage"],
     },
-
     # If there are data files included in your packages that need to be
     # installed, specify them here.  If using Python 2.6 or less, then these
     # have to be included in MANIFEST.in as well.
-    package_data={
-    },
-
+    package_data={},
     # Although 'package_data' is the preferred approach, in some case you may
     # need to place data files outside of your packages. See:
     # http://docs.python.org/3.4/distutils/setupscript.html#installing-additional-files # noqa
     # In this case, 'data_file' will be installed into '<sys.prefix>/my_data'
-    data_files=[
-        ('', ['README.md'])
-    ],
-
+    data_files=[("", ["README.md"])],
     # To provide executable scripts, use entry points in preference to the
     # "scripts" keyword. Entry points provide cross-platform support and allow
     # pip to create the appropriate form of executable for the target platform.
-    entry_points={
-    },
+    entry_points={},
 )