Make the pytest_socket dependency optional

[shocklateboy92]

I'm trying to use this in my E2E/integration tests which need to make a ton of network requests all over the place (because they're E2E tests) and pytest-socket is causing me no end of headaches.

It somehow manages to load itself into all sorts of sub-processes, yet the allowed hosts (and --force-enable-socket) seem to only apply for the immediate test.

Theoretically, I could split out the tests that touch home assistant to their own venv so others will run with an interpreter that doesn't have this package installed. But that would make it impossible to test actual user scenarios where a user does something in Home Assistant, then uses another UI to make changes, then comes back to see if they reflected in HA.

If you could please make that an optional dependency (or make some mechanism to use the very useful fixtures provided by this project without also getting pytest-socket, that would be very much appreciated 🙏 🙏 🙏 🙏 🙏

[MatthewFlamm]

The goal [of pytest-homeassistant-custom-component] is to provide the same functionality as the tests in home-assistant/core.

This request would not follow this goal. I would consider this proposal if Python allowed default optional dependencies, see https://discuss.python.org/t/adding-a-default-extra-require-environment/4898, or allowed optional dependency groups to omit previously defined packages, see https://discuss.python.org/t/optional-dependency-groups-omitting-package-requirements/20833.

[shocklateboy92]

That's fair.

How do you feel about using the same approach as FastAPI?

Essentially, their installation guide just says to install fastapi[standard] which is the "batteries included" version, while fastapi is the more minimal version for advanced users looking for more customizability:

[MatthewFlamm]

I would use that paradigm here if homeassistant/core used it...