Add Python 3.11 support

[lisphilar]

Summary of request

Python 3.11 will be released on 24Oct2022 and we need to check if we can use covsirphy with Python 3.11 regularly.
https://peps.python.org/pep-0664/
pandas-dev/pandas#46680

(Optional) Why required / what will be improved

Updates cycle of Python and main libraries are very shortened nowadays and we need to catch up the speed. Python 3.11+ improves performance drastically and covsirphy users are highly recommended to use the latest version of covsirphy as soon as we can.

The current Version

CovsirPhy version I used: 2.26.2

[lisphilar]

cf. https://github.com/actions/setup-python/blob/main/docs/advanced-usage.md#using-the-python-version-input

[lisphilar]

@fpgmaas
Do you have any ideas to check compatibility of dependencies (linsted on pyproject.toml) with specific Python versions? This may be a new project (or within the scope of deptry), but checking compatibility will be more and more heavy task of developers.

I found a issue regarding this for pip, but I think not resolved.
pypa/pip#7649 (comment)

[lisphilar]

After Python 3.11 releases, pull request will be created and tested to check we can use covsirphy with Python 3.11.
The pull request will be rebased when new changes detected in main branch.
https://github.com/marketplace/actions/rebase-pull-requests

[fpgmaas]

Hi @lisphilar, sorry for my late reply! I must have missed the notification. If I understand correctly, maybe tox can help you out? See it in use in e.g. my repository cookiecutter-poetry. It allows you to install the environment and run unit tests for various Python versions.

deptry also checks for compatibility with Python 3.11.

[lisphilar]

@fpgmaas Thank you for your comment despite the sudden mention!
GitHub Actions workflow runs pytest with python-version matrix at this time in this project, but tox can be a used for tests with various Python versions.

covid19-sir/.github/workflows/test.yml

Lines 65 to 86 in 7fa13f0

	pip-test:
	name: test with pip
	runs-on: ubuntu-latest
	strategy:
	matrix:
	python-version: ["3.8", "3.9", "3.10"]
	steps:
	- name: Checkout
	uses: actions/checkout@v3
	- name: Set up Python ${{ matrix.python-version }}
	uses: actions/setup-python@v4
	with:
	python-version: ${{ matrix.python-version }}
	- name: pip install and test
	run: |
	pip install pip --upgrade
	pip install .
	pip install pytest pytest-cov pytest-xdist
	pytest -v --maxfail=1 tests -n auto

Sorry for not explaining enough.
Regarding this issue, I'd like to get "FAILED" notification only when all dependencies support Python 3.11. Just after "FAILED" notification, we will start to support Python 3.11 (i.e. replace python = "^3.8,<3.11" with python = "^3.8,<3.12", update python-version matrix if tox not used).

[Edited] With the latest versions of dependencies,

• All dependencies support Python 3.8, 3.9, 3.10, and some dependencies does not support Python 3.11
  -> Developers do NOT work on tasks for Python 3.11 support and keep the supported Python versions ("^3.8,<3.11")

• All dependencies support Python 3.8, 3.9, 3.10, 3.11
  -> Developers start to work on tasks for Python 3.11 support

• Some dependencies does not support Python 3.8, and all dependencies support Python 3.9, 3.10, 3.11
  -> Developers start to work on tasks for drop Python 3.8 support