Is there a reason you didn't go with PyCharm? I tried vscode, and it works out of the box for particular things, but Pycharm is just a breeze on latger projects.
No major reason other than I might as well use VS Code since it seemed very popular for writing Python.
But I actually recently wrote a todo to try out PyCharm Pro. I haven't decided if that's pointless yak shaving since VSC works pretty well for me. But I would like to configure VSC more to make my workflow faster. And my guess is PyCharm Pro is probably better out of the box vs having to spend time configuring VSC settings (so many settings...) and plugins.
Re:Nova by Panic
by hutattedonmyarm on Tuesday January 25, 2022 @12:44AM
(#30068559)
I’m still using it for Python, but I agree, its support for the language is incredibly flaky
What plugin(s) exactly are you using in VSCode for Python support?
I have the official Python plugin and the Pylance plugin. I also have mypy enabled though that's not a separate plugin. I've avoided bugs because of that.
I really, really wanted to use Nova, would have paid full price no problem, but for some reason the one main Python plugin was extremely flaky for me. Linter highlighting would sometimes work and sometimes not, unaffected by the plugin settings, and the primary Python plugin I was using was based on somebody’s github repro that hadn’t been touched in a year or two.
I spent a bunch of time but couldn’t figure it out. So I ended up going to VS Code. It works well. The Python plugins work well. It’s a pain in the behind to configure, and it’s not the prettiest thing to look at. But I can grind out working code fast, partially because those plugins catch problems almost as fast as I can type them.
I would try Nova again in a heartbeat if the Python support improves.