-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
23 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
[:arrow_left: Back to USKPA | ||
Documentation](../docs) | ||
|
||
## Python | ||
|
||
The USKPA site uses [Pipenv] to manage development and production dependencies. | ||
In both development and continuous integration, the Python environment is | ||
established with `pipenv install --dev`. | ||
|
||
To accommodate third-party tools that do not yet support [Pipenv], [Pipenv] generates a `requirements.txt` file (containing | ||
only production dependencies) and includes it in the repository. | ||
|
||
You can update development and production dependencies locally with the following: | ||
|
||
```sh | ||
pipenv update --dev | ||
pipenv lock --requirements > requirements.txt | ||
``` | ||
|
||
This will generate updated `Pipfile`, `Pipfile.lock`, and `requirements.txt` files which must be committed to the git repository. | ||
|
||
[Pipenv]: https://docs.pipenv.org/ |