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

support PEP 735 "peerDependencies" #13101

Closed
1 task done
Eliav2 opened this issue Dec 5, 2024 · 1 comment
Closed
1 task done

support PEP 735 "peerDependencies" #13101

Eliav2 opened this issue Dec 5, 2024 · 1 comment
Labels
S: needs triage Issues/PRs that need to be triaged type: feature request Request for a new feature

Comments

@Eliav2
Copy link

Eliav2 commented Dec 5, 2024

What's the problem this feature will solve?

pep 735, which based on my understanding, is currently a draft, introduces "peerDependencies" field.

I could not find any docs about possible support or implementation for pip in this PEP so i opened an issue.

does peerDependencies is going to be supported soon? i wonder cause i'm going to publish a package python and i wonder if i should stick with dependencies and use wide range of versions for my actual peer dependencies and use peerDependencies as pep735 suggest.

Describe the solution you'd like

.

Alternative Solutions

.

Additional context

.

Code of Conduct

@Eliav2 Eliav2 added S: needs triage Issues/PRs that need to be triaged type: feature request Request for a new feature labels Dec 5, 2024
@notatallshaw
Copy link
Member

Thanks for inquiring, however the only reference to peerDependencies in PEP 735, at least as I read it, is talking about prior art in other languages and not something for Python packaging to directly implement: https://peps.python.org/pep-0735/#appendix-a-prior-art-in-non-python-languages.

The main specification only defines a new dependency-groups section to a pyproject.toml: https://peps.python.org/pep-0735/#specification

You can follow PEP 735 discussion and implementation in #12963 and #13065 respectively.

@notatallshaw notatallshaw closed this as not planned Won't fix, can't repro, duplicate, stale Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S: needs triage Issues/PRs that need to be triaged type: feature request Request for a new feature
Projects
None yet
Development

No branches or pull requests

2 participants