Provide persistent skip-lock option
See original GitHub issueI’m always frustrated when pipenv
wants to lock things. This happens when I install and uninstall things. The problem is that it takes FOREVER to lock big scientific packages (that probably include sample data).
I would like to be able to specify completely skipping the locking process within the Pipfile itself.
I’ve tried to specify --skip-lock
in many commands that support it, but some commands simply don’t support it. Additionally, if I forget to specify --skip-lock
then I have to force quit the program and hope that it maintains a usable state.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:24
- Comments:16 (9 by maintainers)
Top Results From Across the Web
How to implement a database job queue using SKIP LOCKED
The SKIP LOCKED option will allow us to lock the rows that have not been locked previously. In our example, you can see...
Read more >Select for update skip locked from JPA level - Stack Overflow
Hibernate provides the UPGRADE_SKIPLOCKED Lock mode. ... and the Lock timeout setting, like for example in persistence.xml for your ...
Read more >MySQL 8.0 Reference Manual :: 15.7.2.4 Locking Reads
InnoDB supports two types of locking reads that offer extra safety: ... However, FOR SHARE supports OF table_name , NOWAIT , and SKIP...
Read more >SELECT FOR UPDATE SKIP LOCKED - Ask TOM
Skip locked was introduced (for AQ) to allow concurrent access to rows without each session getting 'tangled' with the other (which I think...
Read more >Skip Lock Screen is a feature Apple should copy from the Pixel 4
Google this evening confirmed to The Verge that it's “been working on an option for users to require their eyes to be open...
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
Pipenv gives you the virtual environment management. Quite nice IMO.
+1 for having that option inside
Pipenv
.It could have both options because some projects doesn’t need locking and you don’t usually track
.env
files. Other than that, env vars are only useful when you already have isolated environments outside pipenv, otherwise is just simpler to pass skip-lock as an argument.