-
Notifications
You must be signed in to change notification settings - Fork 540
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
compile_pip_requirements + 3.11 failing on some packages #1140
Comments
Facing same issue |
same |
We are upgrading our internal dependencies, so I wonder if it will fix this. |
Has to do a little with inter-dependencies between packages too. Some very outdated packages seem to cause errors like these and the |
Facing the same issue still |
This issue has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs in 30 days. |
🐞 bug report
Affected Rule
The issue is caused by the rule:
compile_pip_requirements
Is this a regression?
I don't think this is a regression in rules_python, but this works with Python 3.10 and does not work with 3.11.
Description
When I try to use
compile_pip_requirements
to recompile a lockfile with certain packages it cannot handle it. I would have thought the libraries were wrong, however a)pip install
works in a non-Bazel venv and b) if I manually resolve the lockfile thenpip_parse
successfully can parse it and the dependencies work in mypy_binary
targets.This seems similar-but-different to #914, but
enable_implicit_namespace_pkgs
does not seem to be an argument tocompile_pip_requirements
and anywaypip_parse
has no problem parsing this package. Plus adding or removing--incompatible_default_to_explicit_init_py
has no effect on this problem.🔬 Minimal Reproduction
WORKSPACE
:BUILD
:requirements_lock.in
:Then run
bazel run //:requirements_lock.update
If you create
requirements_actual.txt
with the same content asrequirements_lock.in
, then you canbazel build @python_deps_docopt//:pkg
or use it as a dependency of apy_binary
target succesfully.🔥 Exception or Error
🌍 Your Environment
Operating System:
Output of
bazel version
:Rules_python version:
Anything else relevant?
I'm also seeing this with another package,
umi-tools
, though there are some other 3.10->3.11 problems there I think so I feltdocopt
was a cleaner demonstration.PS thank you so much for maintaining this project! Super amazing to have so much complexity hidden behind relatively simple rules.
The text was updated successfully, but these errors were encountered: