Ignas Anikevicius

@hunshcn, @linzhp, should we revert the PR until we can find a fix for this? What do you think? I guess we should add a test in the CI to...

So I guess there are a few alternatives here: 1. Maintain two codebases where the user can chose if they want the pure C `tree-sitter` implementation + `cgo` solution or...

A related issue from the upstream bindings package is here: https://github.com/smacker/go-tree-sitter/issues/120 This issue is a tough one, the fact that the cross-compilation does not work means that it is not...

As discussed in #1931, the main idea to address this would be to use https://github.com/go-python/gpython to try and use a pure go implementation to fix this issue. Within the maintainers...

Yeah, the issues you've mentioned is a real pain. That said, I think `gazelle` should be able to parse the python files for symbols and have an internal mapping somewhere...

My thinking is that if somebody is using `importlib` and `gazelle` then they now what they are doing and the can use the feature from #1863.

I have actually checked this and it seems that there are multiple things going here: 1. If you put the `git` url to `requirements.in` like I did [here](https://github.com/aignas/rules_python/blob/fix/parse-requirements-vcs-url/examples/pip_parse/requirements.in#L4) then compiling...

Hey all, I understand that this is a bug report, and I would love to have some input on understanding the priority of this compared to other issues we have...

Yeah, this way of specifying a direct dependency works, I'll close. the issue as fixed.

FYI, once bazel 8 is out, we will start removing support for bazel 6, but if we can maintain compatibility in an easy way that wouldn't hurt. As for bazel...