On Thu, Jun 17, 2021 at 12:46 AM SeongJae Park <sj38.park@xxxxxxxxx> wrote:
>
> Commit 87c9c1631788 ("kunit: tool: add support for QEMU") on the 'next'
> tree adds 'from __future__ import annotations' in 'kunit_kernel.py'.
> Because it is supported on only >=3.7 Python, people using older Python
> will get below error:
>
> Traceback (most recent call last):
> File "./tools/testing/kunit/kunit.py", line 20, in <module>
> import kunit_kernel
> File "/home/sjpark/linux/tools/testing/kunit/kunit_kernel.py", line 9
> from __future__ import annotations
Chatted offline with David about this.
He was thinking if we could instead drop the minimal version back to 3.6.
I think we can do so, see below.
Perhaps we should drop the import and then chain this patch on top of
that, specifying a minimum version of 3.6?
Checking out https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git/?h=kunit-fixes
The offending "annotations" import is related to type annotations.
Specifically https://www.python.org/dev/peps/pep-0563/
So let's see how the two most popular typecheckers fare.
pytype is happy with or without import.
mypy has the same issues with or without the import.
$ mypy tools/testing/kunit/*.py
tools/testing/kunit/kunit_kernel.py:227: error: Item "_Loader" of
"Optional[_Loader]" has no attribute "exec_module"
tools/testing/kunit/kunit_kernel.py:227: error: Item "None" of
"Optional[_Loader]" has no attribute "exec_module"
tools/testing/kunit/kunit_kernel.py:228: error: Module has no
attribute "QEMU_ARCH"
tools/testing/kunit/kunit_kernel.py:229: error: Module has no
attribute "QEMU_ARCH"
So clearly it's not doing anything for them.
Taking a look over 87c9c1631788 ("kunit: tool: add support for QEMU")
next then...
I don't see anything that would warrant the import, so we should
probably drop it.
In that case, the minimum supported version should drop back down to 3.6.
We use enum.auto, which is from 3.6
https://docs.python.org/3/library/enum.html#enum.auto
We could consider stopping using that, and I think we might be then
3.5-compatible.
Maybe we have a chain of 3 patches then, drop the import, drop auto,
and then add in a >=3.5 version check?
> ^
> SyntaxError: future feature annotations is not defined
>
> This commit adds a version assertion in 'kunit.py', so that people get
> more explicit error message like below:
>
> Traceback (most recent call last):
> File "./tools/testing/kunit/kunit.py", line 15, in <module>
> assert sys.version_info >= (3, 7), "Python version is too old"
> AssertionError: Python version is too old
>
> Signed-off-by: SeongJae Park <sjpark@xxxxxxxxx>
> Acked-by: Daniel Latypov <dlatypov@xxxxxxxxxx>
> ---
>
> Changes from v1
> - Add assertion failure message (Daniel Latypov)
> - Add Acked-by: Daniel Latypov <dlatypov@xxxxxxxxxx>
>
> tools/testing/kunit/kunit.py | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tools/testing/kunit/kunit.py b/tools/testing/kunit/kunit.py
> index be8d8d4a4e08..6276ce0c0196 100755
> --- a/tools/testing/kunit/kunit.py
> +++ b/tools/testing/kunit/kunit.py
> @@ -12,6 +12,8 @@ import sys
> import os
> import time
>
> +assert sys.version_info >= (3, 7), "Python version is too old"
> +
> from collections import namedtuple
> from enum import Enum, auto
>
> --
> 2.17.1
>
