After upgrading from 2.7 to 2.8 in VS Code, I consistently receive a prompt to select a Python interpreter, even after selecting one. Furthermore, the script execution is not recognized.

[TotheAnts]

After upgrading from 2.7 to 2.8 in VS Code, I consistently receive a prompt to select a Python interpreter, even after selecting one. Furthermore, the script execution is not recognized.

[muhammadmobi]

2.8.0 replaced the old interpreter picker with a check per workspace folder (4fdc1ff), and the message now names the problem. When it keeps coming back after you pick an interpreter, check these first:

1. An old robotcode.python setting. It's deprecated, but if it's set it still wins over the interpreter you select, so picking another one changes nothing. Search your user settings, the workspace settings.json and any .code-workspace file for "robotcode.python", remove it, then run RobotCode: Restart Language Servers.
2. No Robot Framework in the selected environment. RobotCode needs Python 3.10+ with Robot Framework 5.0+ in the environment the Python extension selected for that folder. With the Python Environments extension, that's the one its Python view shows, which may not be the one you used before. Choose it with RobotCode: Select Python Environment and check it there with python -m robot --version.
3. Multi-root workspace: the check runs per folder, so each folder with Robot files needs its own environment.

To see what RobotCode actually uses, hover the {} next to "Robot Framework" in the status bar, or run RobotCode: Copy Environment Info.

If runs don't show up where they used to: 2.8.0 also starts runs in RobotCode's own terminal by default (552a354). This brings back the 2.7 behavior:

"robotcode.debug.defaultConsole": "integratedTerminal"

If it still asks after that, please post the exact text of the message and the output of Copy Environment Info.

Docs: The Python environment, Troubleshooting, 2.8.0 changelog

[d-biehl]

@TotheAnts please don't cross post, is it now an question here in the discussions or a question in the issues? where we should discuss this?

@muhammadmobi is right, you can check these things, except that defaultConsole thing, it has nothing todo with the recognition of the python interpreters.

@TotheAnts there are some smaller issues with that message I already fixed it, but I have not released a new release, but you can try the dev releases and try if it is fixed. If not than I need some more information from you, like what kind of python environment you use, package managers, did you use the python environments extensions, what ever you that can help me to reproduce the bug or whatever it is.