Allow building against system Brotli #1182
Conversation
…ed brotli instead of vendored one
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
|
Also interested. |
|
@eustas any chance we can get this merged? |
|
@eustas following up. Thanks. |
setup.py
Outdated
|
|
||
| CURR_DIR = os.path.abspath(os.path.dirname(os.path.realpath(__file__))) | ||
|
|
||
|
|
||
| def bool_from_environ(key: str): | ||
| value = os.environ.get(key) |
There was a problem hiding this comment.
you probably should use four space indentation like the rest of the file
+ Updated dependency resolution for edge cases in setup.py
|
@anthrotype Hi! Thanks for noting formatting issues. Looks like setup.py was inconsistent prior our changes so it's why my IDE decided to stick with 2 spaces. Reformatted the entire file for 4 spaces + adjusted system Brotli resolution based on some lessons learned from the initial PR. |
|
you're right, it was inconsistent before. Then perhaps better to limit the formatting changes as much as possible to prevent other PRs that touch setup.py to get into merge conflicts? E.g. #1206 |
|
@anthrotype You're right. But probably on the long distance it's better to have everything linted? Plus, spaces rarely cause major merge conflicts. IMO, we should wait for the PR you linked to be accepted. Then, I can rebase my PR on top of that + include formatting fixes. |
|
Would close #933 |
This PR adds the capability to build Python bindings against system-provided Brotli instead of vendored one