Use container mount for custom_components inside /config to avoid PYTHONPATH #205
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.
Use container mount instead of relying on PYTHONPATH for integration to be found by hass.
Allow integration to be found by hass without polluting module search path.
It's quite common (good practice or not) in the wild for integrations and their lib
requirement
to share the same package name. Adding custom_components to PYTHONPATH does not support this scenario. Integrations that are currently based on this template will stop working if brought to sync with this repo. The error thrown is confusing since the requirement is installed by hass but will resolve to the integration package itself.fixes #130