Allow only specific packages to be skipped during startup dependency installation #82758
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.
Proposed change
Add a
--skip-pip-packages
command line argument for more granular control over runtime package installation than--skip-pip
.I use the
--skip-pip
option because I frequently test upgraded/downgraded packages at runtime. When upgrading HA Core, I have to re-launch Core without--skip-pip
, let it install updated dependencies for other integrations, manually re-install my own, and then re-launch with--skip-pip
.Example:
Type of change
Additional information
--skip-pip-packages
for more granular package installation control developers.home-assistant#1555Checklist
black --fast homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.To help with the load of incoming pull requests: