-
Notifications
You must be signed in to change notification settings - Fork 0
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
Create extension pack "inwt Python IDE" #1
Comments
We should check these out https://github.com/microsoft/vscode-python/wiki/Migration-to-Python-Tools-Extensions |
What do we actually need?VSCode extensions needed
Settings
|
I removed the smart execute logic and also most of the extensions from the bundle. When we start to configure ruff, black and so on, we have to check if this is now possible using configurationDefaults: Maybe with this we do not need to create a settings.json after all. Also we now have a gh action to publish the extension. This happens as soon as we create a tag on gh. |
I added python-indent |
Did a first release. Had to strip some more configuration to get there. But also verified the gh action works: https://marketplace.visualstudio.com/items?itemName=inwtlab.inwt-python-ide-v2 |
@chamaoskurumi do we actually need python-indent when we autoformat at the same time? |
Well I trusted the author of python-indent when he says But tbh I didn't try it out, maybe this information is outdated and python-indent is not needed. |
Besides, I tried to updated the npm packages in this branch, but unfortunately it created all sorts of problems. We either accept that we work with (very) old package versions or we need to update one by one to see how far we get without breaking things. |
Since they are only relevant for development and we do not need them for the extension, I would leave them as they are. If you want to follow that road, I would start from scratch, following https://code.visualstudio.com/api/get-started/your-first-extension for an extension pack, and simply update/copy the contents from the package.json. |
I went through some of the examples and I think with autoformatting, there is not much you gain. Also some of the mentioned tickets are closed, because they have become part of pylance and got implemented. |
I think the doc string extension is missing. |
The text was updated successfully, but these errors were encountered: