Skip to content

Table of initial tox checks #42616

@l0lawrence

Description

@l0lawrence

Some background:
In our package pipelines we have Analyze checks that we run. Currently these are run using tox, and pip. We want to update these to be faster by switching away from tox, and adding the option to use uv.

These are the first analyze checks that we want to try to implement using our new deployment pattern (aka no longer using tox). The anticipated CLI commands are outlined, as well as the actually script that each command should be triggering.

Below ranked in order of execution:

Tox Check Name Old Command New Command Script Called / Main Logic How the Check Works
mypy tox -e mypy -c ./eng/tox/tox.ini --root <pkg_path> uv run azsdkpy mypy packageName ` mypy Installs mypy, runs static type checking on the package.
pylint tox -e pylint -c ./eng/tox/tox.ini --root <pkg_path> uv run azsdkpy pylint packageName pylint (with custom plugins) Installs pylint and out custom azure-pylint-guidelines-checker package, runs static analysis using repository guidelines.
sphinx tox -e sphinx -c ./eng/tox/tox.ini --root <pkg_path> uv run azsdkpy sphinx packageName eng/tox/run_sphinx_build.py Builds Sphinx documentation for the package, this check is a little more difficult as it looks at the sdist.

Metadata

Metadata

Assignees

Labels

EngSysThis issue is impacting the engineering system.feature-requestThis issue requires a new behavior in the product in order be resolved.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions