I sure I’m doing something wrong here, but I’m trying to contribute a change to a library used by an integration custom component and I’m having a devil of a time when attempting to load that requirement from my forked GitHub repo. The docs seem to indicate it’s possible, but when using the format shown here Custom requirements during development & testing I get the following exception showing up in the logs
2022-12-05 20:52:50.866 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration openevse which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2022-12-05 20:53:49.479 ERROR (MainThread) [aiohttp.server] Error handling request Traceback (most recent call last): File "/usr/local/lib/python3.10/site-packages/pkg_resources/_vendor/packaging/requirements.py", line 102, in __init__ req = REQUIREMENT.parseString(requirement_string) File "/usr/local/lib/python3.10/site-packages/pkg_resources/_vendor/pyparsing/core.py", line 1141, in parse_string raise exc.with_traceback(None) pkg_resources._vendor.pyparsing.exceptions.ParseException: Expected string_end, found '+' (at char 3), (line:1, col:4)
It goes on a bit with additional characters that it doesn’t seem to like as it moves through the string.
The requirements entry I’m using is
Has the format for specifying requirements during dev changed?
This is on a fresh docker instance setup specifically for dev work on this component.