

At the very least, I suggest putting this in the Caveats section. I noticed the following minor inconsistency and I thought I would share it just in case it was important (personally I can live with it) or if the fix is simple (I'm guessing this may only require also registering the ENTER key for the extension when text is highlighted). See the extension on the VSCode Marketplace and its source code on GitHub. See the developer docs for pointers on how to develop this extension.įirst off, thank you for putting in the time to create and share this nifty little tool! kbrose/vsc-python-indent, Python Indent Correct python indentation in Visual Studio Code. If you experience any problems, please submit an issue, or better yet a pull request. Specifically, vim related plugins seem to require special attention.The conditions when the shortcut is triggered have been heavily restricted, but there may still be times this extension is unexpectedly overriding Enter behavior. The extension works by registering the Enter key as a keyboard shortcut.If your python code is not correctly formatted, you may not get correct indentation.Having to modify generated code is never good I use the designers with Visual Studio to generate C and then subclass in IronPython to actually implement the functionality. Using tabs ( \t) for your indentation will not work. The designers target IronPython 1 and the generated code require changes to run them on their own with IronPython.It seems like the maintainers of the python extension at microsoft are not prioritizing indentation, since there has been no progress in the years since it was first asked for. There are many related issues on GitHub (, ,, , ) asking for improved python indentation in VS Code. | # Setting trimLinesWithOnlyWhitespace = true will trim the whitespace.| # The default of false preserves whitespace def f():.
