I believe PROS only supports C and C++, but not python unfortunately. Are you mistaking PROS with VEXcode Python?
How did you install PROS? If you installed the CLI/toolchain through VSCode , you will not have access to them outside of the VSCode environment unless you modify your system PATH.
When you say “it just doesnt work in the terminal”, which terminal are you referring to (im going to assume command prompt for now)? command prompt on your computer? a random terminal in vscode? the PROS Integrated Terminal in VSCode?
Your error seems to be some weird dependency nightmare between the python version you have installed locally on your machine and the python bundled with the cli through cxfreeze. In any case, my senses are telling me that the cli being used in the attached image is very much out of date.
Ah… I misinterpreted. Looking at the picture, you’re posting a picture of the command line, while simultaneously talking about using the VSCode extension. If you install the PROS VSCode extension, I have tested and the extension for PROS does NOT give you CLI capabilities with just the command line (at least in a simple sense). If you want to use the CLI within the PROS Extension’s integrated terminal, follow the first header. If you want to use PROS CLI in your own native command line, follow the second header.
Note that if you are in VSCode, and installed the PROS CLI and Toolchain on your windows device during the extension installation process, you need to click on the following to use the integrated terminal to run PROS commands within the CLI inside of the extension itself:
And using this, “prosv5” is not a command, but “pros” and “pros v5” is
Looking at the github, it states that the required version is Python 3.6: GitHub - purduesigbots/pros-cli: Command Line Interface for managing PROS projects. Works with V5 and the Cortex
However, the README was updated 5 years ago, whereas the latest PROS change was as early as 2 months ago. It may be possible that the PROS version may require an earlier Python Version (i.e. Python 3.8). @BennyBoy could you verify if the README is correct such that PROS should work for Python 3.6?
I’m testing with a fresh version of Windows and Python 3.12:
From this, I re-open my command prompt and type “pros”:
Additionally, “pros v5”
We have recently updated all packages in the CLI, so a newer python version may be required. I will investigate this and update the Readme once I have time. Our build pipeline uses python 3.9.13.
A reason I suspect the user has a very out of date cli installed is because the prosv5 alias has been removed, and only the pros executable remains. There were two executables created at the transition time from cortex to v5, but last year we removed the prosv5 alias as the two executables were identical. They will need to find the old pros installation and remove it (or remove it from environment variables) to ensure that a newer pros executable is used when they type pros in command prompt.
The installation guide you wrote is mostly correct. Please install pros-toolchain-windows-formatted.zip for the toolchain, as it contains the correct internal directory structure.
Additionally, the user said that things work in VSCode, leading me to believe that they have a functional cli and toolchain within VSCode. It may be simpler for them to add the directories listed here to their environment variables, instead of downloading a new cli installation: Vscode PROS executable location · Issue #192 · purduesigbots/pros-cli · GitHub
@anon82229125 hopefully we could be of help, let us know if you encounter any more issues.
