-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
new 'pre' syntax in Pipfile #1760
Copy link
Copy link
Closed as not planned
Labels
Category: FutureIssue is planned for the future.Issue is planned for the future.Category: PipRequires pip update to addressRequires pip update to addressType: Enhancement 💡This is a feature or enhancement request.This is a feature or enhancement request.Type: Vendored DependenciesThis issue affects vendored dependencies within pipenv.This issue affects vendored dependencies within pipenv.
Metadata
Metadata
Assignees
Labels
Category: FutureIssue is planned for the future.Issue is planned for the future.Category: PipRequires pip update to addressRequires pip update to addressType: Enhancement 💡This is a feature or enhancement request.This is a feature or enhancement request.Type: Vendored DependenciesThis issue affects vendored dependencies within pipenv.This issue affects vendored dependencies within pipenv.
Placeholder ticket for the proposition we talk with Kenneth.
Add the following syntax in the
Pipfile:This would allow to allow prerelease resolution for one package only.
Change the
pipenv install mypkg --prebehavior. It will set the setting described above only for this very package. Today it turns on a general 'pre' setting for the whole Pipfile, leading other packages to also resolve to prerelease.Change the
pipenv updateandpipenv lockbehavior. They should take into account the presence of thepre=truesetting for some package.Here are some impact I think might happen
>=1.0in one dependency, and another package define thepre=truewhile a new version 2.0.0.b1 is available on pypi,pipenv installshould take itpresetting in the Pipfile. Maybe we can document users need to do apipenv update --preorpipenv lock --preto turn the general 'pre' settings on.