I'm new at this Visual Studio Community thing because I've been coding in Excel VBA for many years now and I wanted to switch to another language because VBA is fading out. If we spend hours, that become weeks and then years trying to make something work and then just to see that there is something else on the side that is developed faster than the thing that is supposed to be the real thing, then somebody doesn't understand users needs. Testing (pytest and unittest, Code Coverage)Įvery person on this earth have a life expectancy of a 100y.ĝebugging (both Native Debugging and Standard Debugging).The following capabilities that you know and love will continue to function as normal in Visual Studio for python environments such as: There are also some known issues with using the legacy debugger to attach to a running Python process (see GH5853). Moreover, for f-strings support, our current code analysis will not offer completions. To avoid this, disable the warning by navigating to Tools > Options > Python > Debugging and deselecting the option Prompt before running when errors are present. Using any one of these features may trigger a warning message when you launch the project: While we work to fully support code analysis for the recent inclusions to Python 3.8, below are a list of the language-specific features that our parser will not be able to recognize and will surface as ‘red squiggles’ in the IDE:
0 kommentar(er)
