-
Notifications
You must be signed in to change notification settings - Fork 143
ModuleNotFoundError: No module named 'refresh_compile_commands' #137
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
Comments
Hey! Thanks for giving the tool a try and for writing in. We're using the same commit internally (as you'd expect) and I'm not seeing the same error, unfortunately; I'm having trouble reproducing. I also tried running it in an empty bazel project and things ran successfully with both the latest bazel rolling and stable releases; so it's not dependent on some quirk of our .bazelrc. Any idea what might be different about your setup? Some super old bazel version? Does it run cleanly in an empty project? All the best, |
bazeltest.zip |
Aha! 🤦🏻♂️ Yep, so the issue is that, in trying to get a better error message for folks who try to run this under very old python versions, I inadvertently broke support for calling refresh_compile_commands in sub-packages. Most people put it in the top level BUILD file (probably because of the recommendation in the readme), so it'd gone unnoticed. Thanks so much for taking the time to bring it to my attention and help me understand. I've pushed up a commit that I think will fix things. Could I ask you to give them a try and tell me how it goes? |
Yes, (e160627) appears to fix it. |
Executing
bazel run :refresh_compile_commands
produces this error.I'm using the latest commit (ecafb96)
The text was updated successfully, but these errors were encountered: