This will for the most part pick up your auto-formatter if you have one installed, that formatter will use the config in your project directory, etc etc. With VSCode you can launch the editor from a Terminal session with your virtualenv activated and it "Just Works". Most of the community and tooling has centralised on them at this point. It's fairly fundamental to multi-project workflows to be able to use virtualenvs. I had many issues with the Python ecosystem. Critically though it's got a great plugin for most things. It's not quite as nice in many ways but it's nice enough. I switched to another editor and it's slower, but fast enough. I used Sublime for many years and it was hard to let it go, the speed was great and the SublimeGit plugin was the best Git client I've used, but multi-project development was a pain because the Python/JS/etc plugins didn't have good support for virtualenvs/per-project config/etc, and it was clear that they were out of active development.
Sublime text 4 software#
This then means that the plugin ecosystem is fairly under developed and inactive because there's little incentive to actively develop plugins for software that appears to be dead. until there's a major version bump and the cycle starts again. It does big-bang releases with lots of features, followed by frequent bug fix releases that quickly resolve issues, followed then by years of silence even though there are still issues. Sublime Text has the strangest development cycle I can think of.