tree 1b4e80616a713b36a179c6a7bb26d7144c871a13
parent dd4f904bcad7c7d79ceb759f816794d616505097
author Alex Eagle <alex@aspect.dev> 1698968638 -0700
committer GitHub <noreply@github.com> 1698968638 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJlRDRNCRBK7hj4Ov3rIwAA8wkIAHtpXW542NRiPFaH1onYdXT4
 JhZCTxhP36xnlLYSPeEOb9v4R6Qg7/giJPMclwp4EqJHkTc50NStz5/3wBVH1dfY
 7J0DUJ4HycTU65RVJBcWKz9uC3g4OqiW4cPHY0cYH5hEa5xbqCcl5C7jto21Rywc
 hq3cILJYtbcGrPqt+5fXEf0auxmOdtXCkC7ZLXRQTe6mX0OH5uNZV7FujCUpBdjO
 pUBmn6f++Nf0QfVZuDxoz9XJCrePKU6kVCmMd5K5QBAtmaE1BFsLGbhmrBaX65By
 mlv9s4lhCZ96vKmMiFQTH3y7YdgF7B9FZhMaYw2a3ArJC90q/l5NhUPcINMYdMY=
 =Rmqb
 -----END PGP SIGNATURE-----
 

feat(pip): provide pypi -> whl target mapping in requirements.bzl (#1532)

Currently a BUILD file can load `all_whl_requirements` but then can't
determine which one is associated with a given package installed by the
user.
This makes it impossible to build rules where the user can choose a
given package and then override the wheel used, for example. @mattem and
I are working at a client where we need this ability.

This PR makes a small, non-breaking refactoring to the generated
`requirements.bzl` file so that this information is available in a new
`all_whl_requirements_by_package` symbol.

Users can then do something like this:

```
load("@pip//:requirements.bzl", "all_whl_requirements_by_package")

some_rule(
  wheels = dict(all_whl_requirements_by_package, **{
    "charset-normalizer": "@charset_1_2_3//:file"
  }),
)
```