This package bridges gab in pipenv tooling by providing quick and easy way to check whether Pipfile.lock in question is consistent with the corresponding Pipfile without doing anything else.
I find it particularly useful with pre-commit hooks (see below)
Usage
check-pipfile-lock <path to Pipfile.lock>
If no path to Pipfile.lock is provided, the current directory is assumed.
Pre-commit hook
Here is the configuration for pre-commit framework.
- repo: https://github.com/haizaar/check-pipfile-lock
rev: v0.0.5
hooks:
- id: check-pipfile-lockDevelopment
echo 'layout pipenv' > .envrc
direnv allow # will take a while
make bootstrap1 maintainer
Metadata
1 maintainer
Release files for check-pipfile-lock 0.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| check-pipfile-lock-0.0.5.tar.gz | 3.8 kB | Details |
Release files / check-pipfile-lock-0.0.5.tar.gz
| Download URL | check-pipfile-lock-0.0.5.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
154946323c9d655222aee6ea3b16f647f9687f54b28a42075a10e82e01022ae7
|
|
BLAKE2b-256 checksum How to use checksums |
29ce8b35d597f24cca34b9bf2e31e949ef77945f22f10f0852c7634cb0e19985
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.8
|
