Clarify beginner Python setup steps in VS Code documentation### Documentation issue
During a usability test with a participant who was comfortable with computers but new to traditional programming tools, the participant was able to install VS Code successfully but needed clearer guidance around the first-time Python workflow.
The current beginner experience could be improved by making the Python setup sequence more explicit for new users:
- Install VS Code.
- Install the Python extension.
- Restart shell step
- Install or verify a Python interpreter.
- Open or create a
.py file.
- Select the interpreter.
- Run a simple
print("Hello, World!") script.
- Confirm where the output should appear.
The issue is that the first-time Python path can be unclear for users who are comfortable with computers but unfamiliar with IDEs, interpreters, extensions, and terminals. There was confusion around the "restart shell" terminology for a new user. Users who are newer to Computer Science terminology will be unfamilar with the term, and may not know what a "shell" means.
Suggested improvement:
Add or revise a short beginner-oriented section that clearly distinguishes between VS Code, the Python extension, and the Python interpreter. This would help users understand that VS Code is the editor, the extension adds Python support, and the interpreter is what actually runs the code.
This came up during a usability test for a course assignment. The user was not blocked by installation, but the programming workflow required more context than expected. A small documentation clarification could reduce friction for new Python users.
Clarify beginner Python setup steps in VS Code documentation### Documentation issue
During a usability test with a participant who was comfortable with computers but new to traditional programming tools, the participant was able to install VS Code successfully but needed clearer guidance around the first-time Python workflow.
The current beginner experience could be improved by making the Python setup sequence more explicit for new users:
.pyfile.print("Hello, World!")script.The issue is that the first-time Python path can be unclear for users who are comfortable with computers but unfamiliar with IDEs, interpreters, extensions, and terminals. There was confusion around the "restart shell" terminology for a new user. Users who are newer to Computer Science terminology will be unfamilar with the term, and may not know what a "shell" means.
Suggested improvement:
Add or revise a short beginner-oriented section that clearly distinguishes between VS Code, the Python extension, and the Python interpreter. This would help users understand that VS Code is the editor, the extension adds Python support, and the interpreter is what actually runs the code.
This came up during a usability test for a course assignment. The user was not blocked by installation, but the programming workflow required more context than expected. A small documentation clarification could reduce friction for new Python users.