I've tried it, and watched many a colleague "struggle" with it. "First class" is definitely an over-statement from my perspective, even if it might be great compared to what you'd get with plain-text editors. It's type-hinting half the time behaves oddly even with type-hinting present.
But it is getting better, that's for sure. Looking forward to see upcoming iterations.
My "first class" remark is because it comes from Microsoft itself and isn't a third party plugin.
Re:Guide to Python Debugging
by kingosticks on Tuesday June 02, 2020 @11:05AM
(#23391778)
Would "first-party" be more accurate? First-class implies it's the best. Which it is not.
I guess so, not native speaker, thanks.
My goto for Python debugging is always Visual Studio since I'm coming from a Windows C# and C++ background. I find the Python debugger super easy to use if you're already familiar with that environment.
Early on I used Eclipse plugin for similar reasons - unified debugging across multiple platforms.
https://visualstudio.microsoft.com/vs/features/python/
https://code.visualstudio.com/docs/python/python-tutorial
Both include quite capable debuggers, and AI powered code completion, intelicode.
https://marketplace.visualstudio.com/items?itemName=VisualSt...