Run Python commands from a shell such as PowerShell or Bash. Python code goes in a .py file or at Python's >>> prompt. If the program cannot find a relative file path, check the working directory first. Python usually resolves that path from where the process started, which can be different from the folder containing the script.
Know which prompt you are looking at
If you see Python's >>> prompt, you are inside its interactive interpreter. A command such as python report.py belongs in the operating-system shell, not at that prompt. Enter exit() to return to the shell.
A tutorial may display a prompt before a command to show its context. Do not type a printed PS C:\> or $ as part of the command. Copy the command itself, and check whether the instructions are for PowerShell or Bash.
Understand the working directory
The working directory is the folder from which a process starts. A relative filename such as results/report.json is interpreted from that location unless the program deliberately chooses another base. It does not automatically mean the folder containing the source file.
Before diagnosing a missing input, inspect the current folder and list its files. In PowerShell, Get-Location and Get-ChildItem help. In a Linux shell, pwd and ls provide the corresponding information. You are checking context, not changing the program.
Quote paths that contain spaces
An unquoted space can split one intended path into multiple command arguments. Quote the full path when changing directories or passing it to a program. Keep quoting rules appropriate to the shell; PowerShell and Bash do not interpret every symbol in the same way.
For a first project, a short folder path is easier to inspect. That is a convenience, not a reason to put files in a protected system directory. Work somewhere your normal account can write.
Diagnose a path error by checking the shell, folder, and filename
Ask which program produced the error, which folder it used, and which file it was trying to open. A shell saying a command is unknown is different from Python reporting a FileNotFoundError. The first may concern installation or command discovery; the second often concerns a specific file or path.
Change one thing at a time. Reinstalling Python will not create a CSV that was never extracted. Renaming a source file will not fix a command entered into the wrong prompt.
A short practice task
Make a folder, put a text file inside it, and open a terminal there. Read the file with a five-line Python program. Then run the same program from its parent directory and compare the behavior. Explain the difference before changing the code. This small exercise makes later file, report, and database projects much easier to understand.
If a path works but the launch command still fails, see how to run a Python script from the terminal.