If the regular Python CFLAGS include directories that already have the
zstd headers available, a different and possible incompatible version
can be picked up otherwise. Sadly, it seems like Python has no easy way
to prefix flags before the rest.
Details
Details
- Reviewers
- None
- Group Reviewers
hg-reviewers
Diff Detail
Diff Detail
- Repository
- rHG Mercurial
- Branch
- stable
- Lint
No Linters Available - Unit
No Unit Test Coverage
Event Timeline
Comment Actions
Do you think we can do this upstream?
I think the vendored version of python-zstandard can be upgraded to the latest version now that Python 2 support has been dropped. (Although there may be a Python 3.5 support question.)
I'd prefer if we could facilitate this workaround in the upstream project and not require Mercurial to patch python-zstandard's sources.