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
I have searched the issues of this repo and believe that this is not a duplicate.
I have searched the documentation and believe that my question is not covered.
Feature Request
Currently, adding an optional dependency to have in extras only allows one dependency per project. The issue here is that I may have two extras for my projects, say distributed and server, with ray and ray[serve] as dependencies respectively.
When I poetry add ray we modify the dependencies as
and then when I add ray[serve] on top it modifies the dependencies as
[tool.poetry.dependencies]
python = "^3.8"
ray = {extras = ["serve"], version = "^1.2.0", optional = true}
getting rid of the default ray. Thus, I don't see any way to have something like
[tool.poetry.extras]
distributed = ["ray"]
server = ["ray[serve]"]
without also installing ray[serve] as part of the distributed extra!
I cannot think of any reason this would be desired behavior to not allow treating dependency extras as separate. While I haven't spent a great deal of time thinking about a design for a proposed solution, the above seems reasonable to me (that when specified in extras, a reference to ray does not include ray[serve] by default).
The text was updated successfully, but these errors were encountered:
Feature Request
Currently, adding an optional dependency to have in
extras
only allows one dependency per project. The issue here is that I may have twoextras
for my projects, saydistributed
andserver
, withray
andray[serve]
as dependencies respectively.When I
poetry add ray
we modify the dependencies asand then when I add
ray[serve]
on top it modifies the dependencies asgetting rid of the default
ray
. Thus, I don't see any way to have something likewithout also installing
ray[serve]
as part of thedistributed
extra!I cannot think of any reason this would be desired behavior to not allow treating dependency extras as separate. While I haven't spent a great deal of time thinking about a design for a proposed solution, the above seems reasonable to me (that when specified in
extras
, a reference toray
does not includeray[serve]
by default).The text was updated successfully, but these errors were encountered: