-
-
Notifications
You must be signed in to change notification settings - Fork 126
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
1 changed file
with
26 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
## Motivation | ||
|
||
A project consists of multiple python packages in different subdirectories. Each | ||
of these has dependencies and optional dev dependencies. Compiled requirements | ||
with hashes exist, written with pip-compile: | ||
|
||
- ``code1/pypkg1/requirements.txt`` | ||
- ``code1/pypkg1/requirements-dev.txt`` | ||
|
||
Two modes of operation: | ||
|
||
1. Use compiled requirements files and create nix lock files accordingly. | ||
2. Create nix lock files without using compiled requirements, but only | ||
dependency declarations in pyproject.toml, and pip-compile afterwards for | ||
projects not using nix. | ||
|
||
We'd like to create environments where requirements for individual packages and | ||
combinations of these packages are available. | ||
|
||
For the projects' python packages: | ||
|
||
1. Do not install, environment with requirements only. | ||
|
||
2. Install selected packages. | ||
|
||
3. Install selected packages in editable mode. |