TEST-#7316: Run a subset of CI tests with python 3.10 and 3.11 on a scheduled basis.

anmyachev commented 5 months ago

What do these changes do?

Python 3.11 has been tested separately in https://github.com/modin-project/modin/pull/7317. It works.

[x] first commit message and PR title follow format outlined here

NOTE: If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.
[x] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] signed commit with git commit -s
[x] Resolves #7316
[x] tests ~added and~ passing
[x] module layout described at docs/development/architecture.rst is up-to-date

YarShev commented 5 months ago

Can we now switch to testing with python 3.10?

anmyachev commented 5 months ago

Can we now switch to testing with python 3.10?

I don't think so, we can easily start using python functionality that isn't in 3.9 and break the code.

YarShev commented 5 months ago

Maybe we should add weekly testing on python 3.10 to catch such breaking changes so as to be prepared for transition to python 3.10?

YarShev commented 5 months ago

Why only a subset of CI tests? Which tests are missing?

anmyachev commented 5 months ago

Why only a subset of CI tests? Which tests are missing?

For example, test-fuzzydata.