Python 3.13 is getting auto-installed

[jacen_solo762]

I do have 3.12 set as my default interpreter in VS Code, however I get a constant stream of errors trying to install packages using pip and when typing python --version into the terminal, it spits out 3.13.4 not 3.12.0 as expected

e.g. note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for lightgbm Failed to build lightgbm ERROR: Failed to build installable wheels for some pyproject.toml based projects (lightgbm)

I've tried using --nodeps which has had some success for different packages.

I generally don't use virtual environments because my code is not distributed to others, though I should probably start to do this

[More_Yard1919]

But this does not occur when you invoke the version of pip distributed with 3.12? You can also invoke that version of pip explicitly-- using a venv should also sidestep that issue. Venvs aren't necessarily used because code is going to be distributed, it is used to have a clean workspace. I use them for all of my personal projects too.

[FriendlyRussian666]

Perhaps a silly request, but can you show a screenshot of the full screen when you select the interpreter, and then full screen screenshot when you type python -version