[pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

casement/registry.py

@@ -3,6 +3,7 @@
 Each node in the tree is called a key.
 Each key can contain both subkeys and data entries called values.
 """
+
 import six
 from six.moves import winreg
 

setup.cfg

@@ -8,7 +8,7 @@ url = https://github.com/blurstudio/casement
 author = Blur Studio
 author_email = [email protected]
 license = LGPL-3.0
-license_file = LICENSE
+license_files = LICENSE
 classifiers =
     Development Status :: 3 - Alpha
     Environment :: Console
@@ -18,8 +18,8 @@ classifiers =
     Operating System :: Microsoft :: Windows :: Windows 7
     Operating System :: Microsoft :: Windows :: Windows 10
     Programming Language :: Python
-    Programming Language :: Python :: 2
     Programming Language :: Python :: 3
+    Programming Language :: Python :: 3 :: Only
     Programming Language :: Python :: Implementation :: CPython
     Programming Language :: Python :: Implementation :: PyPy
 platform = any
@@ -33,7 +33,7 @@ install_requires =
     pywin32
     six
     winshell>=0.6
-python_requires = >=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*, !=3.4.*, !=3.5.*
+python_requires = >=3.6, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*, !=3.4.*, !=3.5.*
 include_package_data = True
 setup_requires =
     setuptools

tests/test_env_var.py

@@ -13,6 +13,7 @@
 
 Note: See test_registry.py to see how testing registry keys/entries are handled.
 """
+
 from __future__ import absolute_import
 
 import os

tests/test_registry.py

@@ -13,6 +13,7 @@
 
 Note: See test_env_var.py to see how testing Environment variables are handled.
 """
+
 # TODO: Look into using a custom testing registry hive to handle all testing
 # without the need for the host to actually have these registry keys. We should
 # only enable testing of registry modifications once this is resolved.