modify eachdist.py so develop
subcommand works by default
#3435
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.
Description
By default and with a clean checkout,
eachdist.py develop
fails with ano matching distribution
error.However, if you modify the script, setting with_test_deps to False, the script issues a pip command that does not indicate
[test]
extras for each package, and it completes successfully.This PR makes a small change to
eachdist.py
, defaultingwith_test_deps
toFalse
and adding a flag so users can still turn this capability on.Possible workaround for #1846
Related to #1462
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Tested manually by running
eachdist.py develop
in a clean Python environment.Does This PR Require a Contrib Repo Change?
Answer the following question based on these examples of changes that would require a Contrib Repo Change:
The OTel specification has changed which prompted this PR to update the method interfaces of
opentelemetry-api/
oropentelemetry-sdk/
The method interfaces of
test/util
have changedScripts in
scripts/
that were copied over to the Contrib repo have changedConfiguration files that were copied over to the Contrib repo have changed (when consistency between repositories is applicable) such as in
pyproject.toml
isort.cfg
.flake8
When a new
.github/CODEOWNER
is addedMajor changes to project information, such as in:
README.md
CONTRIBUTING.md
Yes?
No.
Checklist: