change: Update required python version

[fege]

Description

Update required python version, when using 3.9 version there are some import that are not available for example

    from typing import Self
E   ImportError: cannot import name 'Self' from 'typing' 

This was added only in 3.11 typing.Self
Also | for Union was added in 3.10 typing.Union

How Has This Been Tested?

Merge criteria:

• The commits are squashed in a cohesive manner and have meaningful messages.
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work

[github-actions]

The following are automatically added/executed:

• PR size label.
• Run pre-commit
• Run tox
• Add PR author as the PR assignee

Available user actions:

• To mark a PR as WIP, add /wip in a comment. To remove it from the PR comment /wip cancel to the PR.
• To block merging of a PR, add /hold in a comment. To un-block merging of PR comment /hold cancel.
• To mark a PR as approved, add /lgtm in a comment. To remove, add /lgtm cancel.
  lgtm label removed on each new commit push.
• To mark PR as verified comment /verified to the PR, to un-verify comment /verified cancel to the PR.
  verified label removed on each new commit push.

Supported labels

{'/verified', '/wip', '/hold', '/lgtm'}

[fege]

/verified

[fege]

/verified

[rnetser]

python 3.9 is supported till 20/2025.
the repo uses
from __future__ import annotations

use typing_extensions for Self

[rnetser]

python 3.9 is supported till 20/2025.
the repo uses
from future import annotations

use typing_extensions for Self

[rnetser]

adding as a comment so it is visible in labels:

python 3.9 is supported till 20/2025.
the repo uses
from future import annotations

use typing_extensions for Self

[dbasunag]

adding as a comment so it is visible in labels:
python 3.9 is supported till 20/2025.
the repo uses
from future import annotations
use typing_extensions for Self

@rnetser I personally feel the test repo should be using newer python versions, when possible.
from future import annotations should be fine with 3.12. openshift-virtualization uses 3.12 and uses the same import and did not encounter issues.

For use typing_extensions for Self, not sure if we would need it. https://pypi.org/project/typing-extensions/ says it is for older python versions to enable newer typing features and I see Self is here https://github.com/python/cpython/blob/3.12/Lib/typing.py. So I might be missing something, but it does not seem like from typing import Self should be problematic in 3.12

[rnetser]

adding as a comment so it is visible in labels:
python 3.9 is supported till 20/2025.
the repo uses
from future import annotations
use typing_extensions for Self

@rnetser I personally feel the test repo should be using newer python versions, when possible. from future import annotations should be fine with 3.12. openshift-virtualization uses 3.12 and uses the same import and did not encounter issues.

if there's no reason to restrict a version i do not see any reason why limit

For use typing_extensions for Self, not sure if we would need it. https://pypi.org/project/typing-extensions/ says it is for older python versions to enable newer typing features and I see Self is here https://github.com/python/cpython/blob/3.12/Lib/typing.py. So I might be missing something, but it does not seem like from typing import Self should be problematic in 3.12

[fege]

adding as a comment so it is visible in labels:
python 3.9 is supported till 20/2025.
the repo uses
from future import annotations
use typing_extensions for Self

@rnetser I personally feel the test repo should be using newer python versions, when possible. from future import annotations should be fine with 3.12. openshift-virtualization uses 3.12 and uses the same import and did not encounter issues.

if there's no reason to restrict a version i do not see any reason why limit

For use typing_extensions for Self, not sure if we would need it. https://pypi.org/project/typing-extensions/ says it is for older python versions to enable newer typing features and I see Self is here https://github.com/python/cpython/blob/3.12/Lib/typing.py. So I might be missing something, but it does not seem like from typing import Self should be problematic in 3.12

@rnetser are you suggesting to remove completely requires-python ?
I personally think that there is no harm to update to 3.12 given also that this week ended the active support on it https://endoflife.date/python

[rnetser]

adding as a comment so it is visible in labels:
python 3.9 is supported till 20/2025.
the repo uses
from future import annotations
use typing_extensions for Self

@rnetser I personally feel the test repo should be using newer python versions, when possible. from future import annotations should be fine with 3.12. openshift-virtualization uses 3.12 and uses the same import and did not encounter issues.

if there's no reason to restrict a version i do not see any reason why limit

For use typing_extensions for Self, not sure if we would need it. https://pypi.org/project/typing-extensions/ says it is for older python versions to enable newer typing features and I see Self is here https://github.com/python/cpython/blob/3.12/Lib/typing.py. So I might be missing something, but it does not seem like from typing import Self should be problematic in 3.12

@rnetser are you suggesting to remove completely requires-python ? I personally think that there is no harm to update to 3.12 given also that this week ended the active support on it https://endoflife.date/python

I meant leave it on 3.9

[dbasunag]

adding as a comment so it is visible in labels:
python 3.9 is supported till 20/2025.
the repo uses
from future import annotations
use typing_extensions for Self

@rnetser I personally feel the test repo should be using newer python versions, when possible. from future import annotations should be fine with 3.12. openshift-virtualization uses 3.12 and uses the same import and did not encounter issues.

if there's no reason to restrict a version i do not see any reason why limit

For use typing_extensions for Self, not sure if we would need it. https://pypi.org/project/typing-extensions/ says it is for older python versions to enable newer typing features and I see Self is here https://github.com/python/cpython/blob/3.12/Lib/typing.py. So I might be missing something, but it does not seem like from typing import Self should be problematic in 3.12

@rnetser are you suggesting to remove completely requires-python ? I personally think that there is no harm to update to 3.12 given also that this week ended the active support on it https://endoflife.date/python

I meant leave it on 3.9

@rnetser can you elaborate why you recommend staying with 3.9? 3.9 active support ended in May 22 and eol is on Oct 2025.

[dbasunag]

@fege Based on my conversation with @rnetser , lets do the clean up of imports in the same PR.

[fege]

/verified

[github-actions]

Status of building tag latest: success.
Status of pushing tag latest to image registry: success.