4a884d379f
I suspect the PyQt maintainer uploaded a new wheel and yanked the old one, which made pip fall back on a source install which failed. If that's the case, he really should have used a new version number, as this makes building/bisecting older releases more cumbersome. |
||
|---|---|---|
| .. | ||
| 5_14 | ||
| 5_15 | ||
| 6 | ||
| BUILD.bazel | ||
| defs.bzl | ||
| install.py | ||
| README.md | ||
We handle PyQt specially for a few reasons:
- It ships with a few issues in its .pyi files that we want to correct.
- Bazel's Python tools install each package in a separate folder, but the various PyQt packages expect to be installed in the same location, and will give runtime linking issues when they are split up.
To update the version lock file, change to the folder with requirements.in, modify the file, and then run "bazel run //python:update". PyQt does not depend on platform-specific packages, so the update can be run on any platform.