Skip to content

Migrate azdev and azure-cli-diff-tool to pyproject.toml - #556

Open
aryasadeghi1 wants to merge 2 commits into
Azure:devfrom
aryasadeghi1:feature/pyproject-extension-compat
Open

Migrate azdev and azure-cli-diff-tool to pyproject.toml#556
aryasadeghi1 wants to merge 2 commits into
Azure:devfrom
aryasadeghi1:feature/pyproject-extension-compat

Conversation

@aryasadeghi1

Copy link
Copy Markdown
Member

Related issue

Azure/azure-cli-extensions#7740, Phase 3 (modernise packaging to pyproject.toml).

What this does

  • Migrate azdev and azure-cli-diff-tool to PEP 621 pyproject.toml with the setuptools.build_meta backend. Both setup.py files are removed.
  • CI builds with python -m build; tox validates metadata with twine check instead of setup.py check -r -s.
  • Add azdev/utilities/packaging.py, which resolves a package's build configuration from either setup.py or pyproject.toml. setup.py keeps precedence, and tool-only pyproject.toml files are not treated as distributions.
  • Drop the setuptools<80 cap. It guarded setup.py develop, which azdev stopped calling in 0.2.12. The >=78.1.1 floor for CVE-2025-47273 is retained.
  • Bump to 0.2.14b1.

Not included

azdev extension add|list|build still hardcode setup.py, so pyproject-only extensions are not yet supported. That is the next stage and is intentionally out of scope.


This checklist is used to make sure that common guidelines for a pull request are followed.

  • pylint azdev --rcfile=.pylintrc -r n

  • flake8 --statistics --append-config=.flake8 azdev

@aryasadeghi1 aryasadeghi1 self-assigned this Jul 28, 2026
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant