bazel-contrib / bazel-contrib/rules_python
Need a method to build native libraries for pip imports
- Linguagem predominante
- Starlark
- Estrelas
- 690
- Forks
- 722
- Merge médio
- 15h 7min
- PRs com merge (30d)
- 76
Descrição
This is probably a long-term / aspirational wish, though I'd be happy to be shown otherwise.
Packages installed via `pip` often depend on native libraries. As a random example, https://pypi.python.org/pypi/cairocffi is a set of python bindings around the native `cairo` library. The bindings themselves don't include the native library, but they do require it to be installed on the system in a way which can be found by `setuptools` when compiling native code to build the relevant wheel.
It seems like requiring a system-installed library (which could change between builds) would violate hermeticity. We should instead provide a way to specify the dependent libraries required for a given pip import as Bazel targets, which can themselves be build.
This is likely related to bazelbuild/bazel#1475
Guia de contribuição
Avaliação
Esta issue ainda não foi avaliada.