Removed compatibility with Python 3.6

* Removed CI & tests
* Amended documentation

closes #705

.github/workflows/ci.yml

@@ -41,10 +41,8 @@ jobs:
     strategy:
       matrix:
         os: [ubuntu-latest, macos-latest, windows-latest]
-        python-version: [3.6, 3.7, 3.8, 3.9]
+        python-version: [3.7, 3.8, 3.9]
         include:
-          - python-version: 3.6
-            tox-env: py36
           - python-version: 3.7
             tox-env: py37
           - python-version: 3.8

Changelog.md

@@ -2,7 +2,7 @@
 
 ## master (unreleased)
 
-Nothing here yet.
+- Removed compatibility with Python 3.6, also, removed tests & amended documentation (#705).
 
 ## v16.4.0 (2022-09-16)
 

README.md

@@ -74,16 +74,16 @@ For a more complete documentation and advanced usage, go to [the official workal
 
 ## External dependencies
 
-**Workalendar will require you to use Python 3.6+.**
+**Workalendar will require you to use Python 3.7+.**
 
-Workalendar is tested on Python 3.6, 3.7, 3.8, 3.9, and on Linux (Ubuntu), Mac OS and Windows using Github actions.
+Workalendar is tested on Python 3.7, 3.8, 3.9, and on Linux (Ubuntu), Mac OS and Windows using Github actions.
 
 ### Conditional dependencies
 
 As of v15.0.0:
 
-* If you're using \*Nix and Python 3.6, 3.7, 3.8, the package `backports.zoneinfo` is required
-* If you're using Windows and Python 3.6, 3.7, 3.8, the package `tzdata` is *also* a requirement (with the `backports.zoneinfo`).
+* If you're using \*Nix and Python 3.7, 3.8, the package `backports.zoneinfo` is required
+* If you're using Windows and Python 3.7, 3.8, the package `tzdata` is *also* a requirement (with the `backports.zoneinfo`).
 * If you're using Python 3.9+, the stdlib `zoneinfo` package will be used.
 
 ## Tests

docs/contributing.md

@@ -68,7 +68,7 @@ pip install -e ./
 When you provide a patch for workalendar, whether it would be a new calendar or a fix to an existing one, or else, you will have to make sure that your contribution follows these basic requirements:
 
 * Your code should pass the `flake8` test ; that is to say that it follows the [PEP8](https://www.python.org/dev/peps/pep-0008/) guidelines. You can check using the `tox -e flake8` command. If you can't, our CI jobs will do it, and you'll be able to know where are your mistakes, if any.
-* Your code should be compatible with our supported Python version. Currently: Python 3.6, 3.7, 3.8 and 3.9. Again, the CI (powered by Github Actions) will check your code against all those versions so you won't have to.
+* Your code should be compatible with our supported Python version. Currently: Python 3.7, 3.8 and 3.9. Again, the CI (powered by Github Actions) will check your code against all those versions so you won't have to.
 * If you encounter a failure in the `pyupgrade` tox job, you can fix it by running the followinf command: `tox -r pyupgrade`. It'll modify your code so it will pass this test. **Warning:** sometimes, this change can break the `flake8` standards, so you'll have to make sure that both linters will pass.
 
 #### Test-driven start

setup.cfg

@@ -14,14 +14,13 @@ classifiers =
     License :: OSI Approved :: MIT License
     Programming Language :: Python
     Programming Language :: Python :: 3
-    Programming Language :: Python :: 3.6
     Programming Language :: Python :: 3.7
     Programming Language :: Python :: 3.8
     Programming Language :: Python :: 3.9
 
 
 [options]
-python_requires = >=3.6
+python_requires = >=3.7
 zip_safe = False
 include_package_data = True
 packages = find:

tox.ini

@@ -1,5 +1,5 @@
 [tox]
-envlist = pyupgrade,flake8,py36,py37,py38,py39
+envlist = pyupgrade,flake8,py37,py38,py39
 
 [testenv]
 deps =
@@ -28,4 +28,4 @@ deps =
     pyupgrade-directories
 commands_pre =
 skip_install = true
-commands = pyup_dirs --py36-plus --recursive .
+commands = pyup_dirs --py37-plus --recursive .