The "Run Python File in Terminal" button is handy if creating plain scripts, but when creating packaged applications, it causes confusion. It attempts to run the current file as a Python script which can cause import errors if using dot-style relative imports.
I suggest the button instead executes the first entry in launch.json in a non-debug session, allowing for configurability over its behavior. If no launch configurations are available, it should fallback to its current behavior.
The "Run Python File in Terminal" button is handy if creating plain scripts, but when creating packaged applications, it causes confusion. It attempts to run the current file as a Python script which can cause import errors if using dot-style relative imports.
I suggest the button instead executes the first entry in launch.json in a non-debug session, allowing for configurability over its behavior. If no launch configurations are available, it should fallback to its current behavior.