Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Treat Groups as Extras #4841

Closed
jaymegordo opened this issue Nov 28, 2021 · 1 comment
Closed

Treat Groups as Extras #4841

jaymegordo opened this issue Nov 28, 2021 · 1 comment

Comments

@jaymegordo
Copy link

Great to see this feature is now available, thanks. Also great that this neatly generalizes the dev-dependencies in a compatible way :-)

I've read through the documentation, and am left with a few questions:

  1. After reading this section, I wonder: What's the difference between poetry install --default and a plain poetry install? Does the former install only dependencies, and the latter also the package itself? Or is there another reason for --default to exist?
  2. How do dependency groups interact with extras? From the docs, it seems that these two features now coexist but are completely separate? Wouldn't it be possible to also integrate these? Essentially, AFAICS, extras are just optional dependency groups, so it would be nice if they could be treated (and specified) as such? That would mean that --with and --extras become essentially the same option (--extras could be deprecated maybe), and extras could be specified using the new dependency group syntax (and the [tool.poetry.extras] section and optional attribute on individual dependencies could also become deprecated, I think). I might be missing some subtle differences that prevent this, though?

Originally posted by @matthijskooijman in #1644 (comment)

Copy link

github-actions bot commented Mar 2, 2024

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant