Georg Brandl

> > Wild idea: how about a macro that can be applied to a whole module/scope and _removes_ the pyo3 related attributes? It can then be added with `cfg_attr(not(feature =...

I'm not sure what you're reporting here... if you try to highlight Python as C#, that's expected.

Agreed, the recognition of the import blocks (especially with alternates) is currently not smart enough.

A blacklist would still work around that. Another possibility would be indexing C modules in a subprocess; this would avoid both crashing completely, and introducing incompatibilities between multiple C modules,...

> Yeah I agree re. blacklist (my last sentence stated that). Sorry, I overlooked that.

That's certainly possible. Currently rankings are assigned at parse time, but I can imagine adding after-the-fact reranking of modules. In the context of elpy, elpy would inform the backend about...

Hi, thanks for raising this issue! While it wouldn't be hard to make the Client `Send`, the current implementation is not compatible with making requests simultaneously from multiple threads (which...

Thanks for the report!

That's ambiguous though in the case of `vec![1; 3]`.