You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the latest version installs all the dependencies necessary for all the underlying transports:
requests
websockets
aiohttp
It should be possible to install gql without all the dependencies if we only use one transport!
My first idea was to try that by default, all the dependencies are added, but that it could be possible to remove dependencies if you only need one transport.
Why not make it required to include an extra when installing the package? I don't think this is necessarily a bad thing and you would know you are missing a dependency when you attempted to import a transport (each transport should probably be separated into their own file to make sure the transport-only dependencies are only required for their class). In many cases users could even use transports like requests without including the extra as it's such a common dependency (although it should be documented that using the extra is still recommended in case another dependency is added for a specific transport)
Currently, the latest version installs all the dependencies necessary for all the underlying transports:
It should be possible to install gql without all the dependencies if we only use one transport!
My first idea was to try that by default, all the dependencies are added, but that it could be possible to remove dependencies if you only need one transport.
Apparently this is not possible
Please comment if you have an idea.
The text was updated successfully, but these errors were encountered: