isort over Language Server Protocol and VS Code extension

The Python team for VS Code has been working on putting various tools we support behind LSP and breaking them out into their own extensions This work is now far enough along that we wanted to share the extension prototypes for your tool with you and see if you had any interest in owning the extension or the Python-based LSP server backing it yourself?

If you don’t want to take on that responsibility that’s totally fine and understandable! If you want to leave the extension to us, then we would publish the extension on the VS Code Marketplace ourselves. We also plan to publish the extension as open source and support the extension for as long as we felt it made sense based on usage numbers. But due to the difficulty of migrating extension ownership, we wanted to ask early whether you wanted to own the extension from the start? If you did want to own the extension we would give you the code, help you publish to the VS Code Marketplace, and do anything else we can to help you be successful with this.

We have attached a zip file to this issue containing a prototype extension to give you an idea of what we are planning. You can download it, extract the .vsix file, and then install the VSIX to try it out python-isort.zip. This prototype version was built with python 3.10 and bundles isort v5.10.1 (as fallback if nothing is found in your environment).

To be very clear, there’s no pressure or expectations from us. We just want to make sure you as a project had an opportunity to own this extension instead of us from the get-go before the extension gained traction.

[karthiknadig]

If you use the pre-release version of the python extension it detects if there isort extension and disables its own import sorting.

[markusdd]

works like a charm! Thanks a lot, really looking forward to the release.

By the way, is there already a change-ticket for the python extension removing i-sorting from there? because each time on saving it still produces this error message in conjunction with .venvs that we talked about in another ticket.