manager: replace mentions of Python 3.6 with 3.7

Support for Python <3.7 has been dropped - mentions of 3.6 are therefore
outdated.

diff --git a/doc/build.rst b/doc/build.rst
index 6401b1cc8c645b6c47fa2092d85c6fc0ca722fc2..718a0f17d99e9620a97fa6a3e94f47b0158d733d 100644 (file)
--- a/doc/build.rst
+++ b/doc/build.rst
@@ -95,7 +95,7 @@ All dependencies are also listed in `pyproject.toml <https://gitlab.nic.cz/knot/
 .. csv-table::
    :header: "Requirement", "Notes"
 
-   "python3_ >=3.6.8", "Python language interpreter"
+   "python3_ >=3.7", "Python language interpreter"
    "Jinja2_", "Template engine for Python"
    "PyYAML_", "YAML framework for Python"
    "aiohttp_", "HTTP Client/Server for Python."

diff --git a/doc/manager-dev.rst b/doc/manager-dev.rst
index 1e68a99b5ac1931437ce4d7891721f90a632fb26..cdf65267ba791b95a496b7e6b9987c9fd3672472 100644 (file)
--- a/doc/manager-dev.rst
+++ b/doc/manager-dev.rst
@@ -10,7 +10,7 @@ In this guide, we will setup a development environment, discuss tooling and high
 Development environment
 =======================
 
-The Manager is written in Python 3 with the goal of supporting multiple versions of Python available in current Linux distributions. For example, at the time of writing, this means we support Python 3.6 and newer. These compatibility requirements also force us not to rely heavily on modern runtime libraries such as Pydantic.
+The Manager is written in Python 3 with the goal of supporting multiple versions of Python available in current Linux distributions. For example, at the time of writing, this means we support Python 3.7 and newer. These compatibility requirements also force us not to rely heavily on modern runtime libraries such as Pydantic.
 
 Tools
 -----
@@ -26,7 +26,7 @@ First run of the Manager from source
 
 1. clone `the Knot Resolver repository <https://gitlab.nic.cz/knot/knot-resolver>`_
 2. enter the directory ``manager/`` in the repository, all following tasks will be performed from within that directory
-3. run ``poetry env use $(which python3.6)`` to configure Poetry to use a different Python interpreter than the default
+3. run ``poetry env use $(which python3.7)`` to configure Poetry to use a different Python interpreter than the default
 4. run ``poetry install`` to install all dependencies into a newly created virtual environment
 5. run ``./poe run`` to run the Manager in dev mode (Ctrl+C to exit)
 

diff --git a/manager/.python-version b/manager/.python-version
index 22c263a47c9f1df086bdd8cecdfe11fa3f9c865a..94dd2db15b0007ebbcab5a73554b1011dd9d98a4 100644 (file)
--- a/manager/.python-version
+++ b/manager/.python-version
@@ -1,4 +1,3 @@
-3.6.12
 3.7.9
 3.8.7
 3.9.1

diff --git a/manager/README.md b/manager/README.md
index dce1eb297ae3515e6704b3153a92d8796744fb47..80f3d2a50c4415548a8ca9a0ec9e875ec6ec340c 100644 (file)
--- a/manager/README.md
+++ b/manager/README.md
@@ -17,7 +17,6 @@ Be careful, that you need the latest version of Poetry. The setup was tested wit
 After installing the tools above, the actual fully-featured development environment can be setup using these commands:
 
 ```sh
-pyenv install 3.6.12
 pyenv install 3.7.9
 pyenv install 3.8.7
 pyenv install 3.9.1