You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+46-32Lines changed: 46 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,38 +1,15 @@
1
1
# rules_python_external
2
2
3
-
Contains Bazel rules to fetch and install Python dependencies from a requirements.txt file.
3
+
Bazel rules to transitively fetch and install Python dependencies from a requirements.txt file.
4
4
5
-
## Usage
6
-
7
-
#### Setup `requirements.txt`
8
-
9
-
While `rules_python_external`**does not** require a _transitively-closed_`requirements.txt` file, it is recommended. But if you want to just have top-level packages listed, that works.
10
-
11
-
Transitively-closed requirements specs are very tedious to produce and maintain manually. To automate the process we recommend [`pip-compile` from `jazzband/pip-tools`](https://github.com/jazzband/pip-tools#example-usage-for-pip-compile).
12
-
13
-
For example, `pip-compile` takes a `requirements.in` like this:
14
-
15
-
```
16
-
boto3~=1.9.227
17
-
botocore~=1.12.247
18
-
click~=7.0
19
-
```
20
-
21
-
These above are the third-party packages you can directly import.
5
+
## Features
22
6
23
-
`pip-compile` 'compiles' it so you get a transitively-closed `requirements.txt` like this, which should be passed to `pip_install` below:
0 commit comments