Fix GH Azdev Linter/Style CI: replace azdev extension add with legacy pip editable install#10077
Draft
william051200 with Copilot wants to merge 2 commits into
Draft
Fix GH Azdev Linter/Style CI: replace azdev extension add with legacy pip editable install#10077william051200 with Copilot wants to merge 2 commits into
azdev extension add with legacy pip editable install#10077william051200 with Copilot wants to merge 2 commits into
Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
|
Hi @copilot, |
…fo in source
azdev 0.2.12 added `_PIP_EDITABLE_OPTS = "--config-settings editable_mode=compat
--no-build-isolation"` to its `add_extension()` function. With modern setuptools
(64+), this forces a PEP 517 editable install that writes dist-info only to
site-packages, not egg-info to the source directory.
azdev's `get_path_table()` finds extensions by scanning source repo paths for
`*.*-info` files while explicitly excluding site-packages, so extensions
installed via `azdev extension add` are no longer detected and linting fails
with "ERROR: unrecognized modules: [ <ext-name> ]".
Fix: replace `azdev extension add "${mod}"` with
`pip install -e "src/${mod}" --no-build-isolation` in both AzdevLinter.yml and
AzdevStyle.yml. Without `--config-settings`, pip uses the legacy `setup.py
develop` path for setup.py-only packages, creating egg-info in the source
directory where azdev can find it.
Copilot
AI
changed the title
[WIP] Fix the failing GitHub Actions job GH Azdev Linter
Fix GH Azdev Linter/Style CI: replace Jul 6, 2026
azdev extension add with legacy pip editable install
Collaborator
|
Fix GH Azdev Linter/Style CI |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
azdev 0.2.12 introduced
_PIP_EDITABLE_OPTS = "--config-settings editable_mode=compat --no-build-isolation"inadd_extension(). With setuptools ≥ 64, this forces a PEP 517 editable install that writesdist-infoonly into site-packages — noegg-infoin the source directory. azdev'sget_path_table()scans source repo paths for*.*-infowhile explicitly excluding site-packages, so every extension becomes undetectable, and linting/style checks fail with:This is a systemic regression affecting all extensions since azdev 0.2.12 was adopted.
Changes
.github/workflows/AzdevLinter.yml— Replaceazdev extension add "${mod}"withpip install -e "src/${mod}" --no-build-isolation.github/workflows/AzdevStyle.yml— Same fix;azdev styleuses the sameget_path_table()code pathWithout
--config-settings, pip falls back to legacysetup.py developforsetup.py-only packages, creating*.egg-infoin the source directory where azdev can find it.This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
N/A — CI infrastructure fix only.
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally? (pip install azdevrequired)For new extensions:
About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update
src/index.jsonautomatically.You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify
src/index.json.