Does `host-environment-markers` need to be in Pipfile.lock?
See original GitHub issueWhy is host-environment-markers
part of Pipfile.lock? When working on a repository with multiple developers, this part keeps changing based on who last updated the lock file.
Similar systems, like yarn, does not have this information in their lockfile.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:7
- Comments:19 (9 by maintainers)
Top Results From Across the Web
Git - Should Pipfile.lock be committed to version control?
Short - Yes! The lock file tells pipenv exactly which version of each dependency needs to be installed. You will have consistency across...
Read more >Basic Usage of Pipenv - Read the Docs
Pipenv is a reference implementation for using Pipfile. Here is a simple example of a Pipfile and the resulting Pipfile.lock .
Read more >pipenv Documentation - Read the Docs
Generates and checks file hashes for locked dependencies when installing from Pipfile.lock. • Automatically install required Python version when pyenv is ...
Read more >Basic Usage of Pipenv
Here is a simple example of a Pipfile and the resulting Pipfile.lock . ... Ideally, you should only have one target Python version,...
Read more >Use Pipfile | PyCharm Documentation - JetBrains
Pipfile is the dedicated file used by the Pipenv virtual environment to manage ... You might have noticed that along with Pipfile, the...
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 FreeTop 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
Top GitHub Comments
I too find this behavior annoying, and strangely at odds with the cross-platform support I see in (if I understand this correctly) pipenv’s fetching of environment-specific wheels and hashes.
Are you saying it’s useful for some pipenv implementation reason or for pipenv users? I’m having a hard time understanding if you mean the latter.
it’s useful, as the contents of the lockfile are different when created against different versions of python.