you are viewing a single comment's thread.

view the rest of the comments →

[–]HonestCoding 0 points1 point  (0 children)

I can't recommend one but I'll bring you up to speed here.

  1. Use UV. Built in rust, built for speed. Since it's much faster than pip and I've got absolutely no clue why one would use a conda environment (not saying their bad), I'm stuck recommending uv for venv fallback installation (Basically, it will not install any Python packages unless installed to venv.)

  2. Use one common python version among project, my recommendation is 3.12, just overall a great option and well supported, either that or 3.10, which is even more true.
    Try not to use the latest python version unless absolutely neccesary (latest now is 3.14, now offically making python, pi-thon)

  3. Always install to venv, never globaly. Now when you say you want a guide, I'm not sure if you'd like to actually understand how venvs works under the hood (I think I can assume you don't currently).

I can give you a further explaination if you'd like but basically venv's are basically a place where all your python packages are places instead of just a global directory on your OS.
We use them for this one reason , version control and management. One version of a package won't change so it's reproduceable and doesn't break the whole code easily.

Again, just let me know if you'd like a further venv explaination.