Remove pluggy racing #222
Remove pluggy racing #222
Conversation
This allows the user to choose between Rope and Jedi for completions. It also remove the pluggy racing since Jedi's cache isn't thread safe. Closes #189
|
With this the user is allowed to enable both completion providers and would receive duplicated completions. I think this would be a nicer configuration interface for users. What do you think. I can test this branch tomorrow and provide detailed feedback. |
|
So we could either pass I'd rather not have config to switch between them because it means the user needs to understand the pros/cons of each. Also, it's similar behaviour to firstresult=True, but less powerful since there's no fallback. The disadvantage of first result (and your solution too), is that it becomes impossible for a plugin to add extra completions into the mix. Which was the point of plugins in the first place. |
|
I think this is the most flexible solution for now. We can think about merging to filter duplicates in the future once people start using this. As for the configuration, editor integrations can always decide for them selves to present a different config schema to the users. |
@lgeiger does this work for you?
Fixes #212
Fixes #189