-
-
Notifications
You must be signed in to change notification settings - Fork 421
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 per-package --prerelease
option
#774
Comments
I have a different idea to implement this. We may not need any extra table, Say we want to add a package
Because in PEP 440, However, this won't work if you want any future prereleases to be picked but there are only stable releases currently. For example, you add with |
@frostming this would work! Maybe there would also be an option for |
Is there any way to make it work with
I mean, in the prod environment, I don't want to install pre-releases of 3rd party packages. But I have a dependency from
but still can't be resolved. |
Is your feature request related to a problem? Please describe.
Poetry provides the user with the ability to specify
--prerelease
on a perpoetry add
basis. This is likely more useful than a per-project setting, because (in my experience) most of the time it's only certain packages that should be pre-releases.Describe the solution you'd like
A
--prerelease
option forpdm add
which allows the user to install pre-releases for the given dependencies. This would require an entry intool.pdm
, e.g.tool.pdm.pre-dependences
to store this for future resolutions.The text was updated successfully, but these errors were encountered: