Bazel pip rules

These rules fetches pip packages using requirements file generated with pip-compile.

Overview

This repository provides support for installing dependencies typically managed via pip. Usage is similar to rules_python. Main difference is that requirement.txt must have been produced by pip-compile. This means that dependencies of all the pip packages are already resolved and Bazel can fetch them in parallel.

There is also support for python version. The assumption is that each python version has its own requirement files and the python binary of that version exists in the global environment.

Setup

• Generate a requirement.txt with pip-compile

• Add the following to your WORKSPACE file:

load("@bazel_tools//tools/build_defs/repo:git.bzl", "http_archive")

http_archive(
    name = "com_github_ali5h_rules_pip",
    strip_prefix = "rules_pip-0.5.0",
    urls = ["https://github.com/ali5h/rules_pip/archive/0.5.0.tar.gz"],
)


load("@com_github_alish_rules_pip//:defs.bzl", "pip_import", "repositories")

repositories()

pip_import(
   name = "my_deps",
   requirements = "//path/to:requirements.txt",
   python_version="3.6",
)

load("@my_deps//:requirements.bzl", "pip_install")
pip_install()

You can optionally pass the same arguments that pip install accepts to pip_install. For example, if you have wheels for all the packages in the provided requirements.txt (do this so your builds are reproducible and tests can be cached) you can have pip_install(["--only-binary", ":all"]).

Updating tools/

All of the content (except BUILD) under tools/ is generated. To update the tools simply run this in the root of the repository:

./update_tools