new 'pre' syntax in Pipfile
See original GitHub issuePlaceholder ticket for the proposition we talk with Kenneth.
Add the following syntax in the Pipfile
:
...
mypkg = { version = "*", pre="true"}
...
This would allow to allow prerelease resolution for one package only.
Change the pipenv install mypkg --pre
behavior. 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 update
and pipenv lock
behavior. They should take into account the presence of the pre=true
setting for some package.
Here are some impact I think might happen
- if a version of package is describe at
>=1.0
in one dependency, and another package define thepre=true
while a new version 2.0.0.b1 is available on pypi,pipenv install
should take it - I don’t see any syntax to turn the general
pre
setting in the Pipfile. Maybe we can document users need to do apipenv update --pre
orpipenv lock --pre
to turn the general ‘pre’ settings on.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:143
- Comments:45 (12 by maintainers)
Top Results From Across the Web
Basic Usage of Pipenv - Python Packaging Authority
Pipfiles contain information for the dependencies of the project, and supersedes the requirements.txt file used in most Python projects. You should add a ......
Read more >Advanced Usage of Pipenv - Read the Docs
Pipenv will expand environment variables (if defined) in your Pipfile. Quite useful if you need to authenticate to a private PyPI:.
Read more >Common Pipenv Errors - Towards Data Science
After this command, your Pipfile has a new variable; 'allow_prereleases = true.' Note that this will allow the installation of any pre-release ...
Read more >pipenv Documentation - Read the Docs
pipenv install is fully compatible with pip install syntax, for which the ... Pipfile.lock takes advantage of some great new security improvements in...
Read more >How to resolve Python package dependencies with pipenv?
Hint: try $ pipenv lock --pre if it is a pre-release dependency. ... Clearing the cache on pipfile.lock , uninstalling your package and...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Just noting that
pipenv
isn’t currently abiding by one of the usability recommendations that was included in the PEP 440 specification. Specifically: “By default, dependency resolutions tools SHOULD … accept remotely available pre-releases for version specifiers where there is no final or post release that satisfies the version specifier”It constantly bits me, because
black
doesn’t have stable releases yet.pipenv + black = 💥