Conversation
k-dovgan
commented
Jun 15, 2026
k-dovgan
commented
- Switch to venv in tests according to recommendations
- Make post-commit optional for non-main branches
- Also fix doctest for Python3.14 new warning format
|
Here is the summarized build result: Here is the link to Github Actions build: https://github.com/Samsung/Universum/actions/runs/27533336011 |
|
Here is the summarized build result: Here is the link to Github Actions build: https://github.com/Samsung/Universum/actions/runs/27537002934 |
|
Here is the summarized build result: Here is the link to Github Actions build: https://github.com/Samsung/Universum/actions/runs/27537156529 |
| def fixture_runner_with_analyzers(docker_main: UniversumRunner): | ||
| docker_main.environment.install_python_module("pylint") | ||
| docker_main.environment.install_python_module("mypy") | ||
| # This particular test set needs system-wide Python, because analyzers somehow don't support venv |
There was a problem hiding this comment.
As I know, you can just use pip and python bins directly from the venv dir, and it should work without regular venv activation.
What was the exact issue with the analyzers in your case?
There was a problem hiding this comment.
In this particular case we pass python version to analyzers and it launches like "python{version} -m ". So trying to launch this tests launches the system-wide python bin for running analyzer, while using the venv bin for handling the test
There was a problem hiding this comment.
Shortly: pip-in-venv logic works if you are not trying to launch it in docker via python framework :)
2 participants
