190

submitted 5 days ago by Ragdoll_X@sh.itjust.works to c/programmer_humor@programming.dev

51 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] SlurpingPus@lemmy.world -2 points 4 days ago* (last edited 4 days ago)

Pyenv and venv are independent and don't do any ‘same thing’, so you must be really talented to mess them up or be confused by them.

I also don't know what's difficult about understanding why the system-wide installation exists or how to add local modules to the path (which venv does for you anyway).

[-] ExLisper@lemmy.curiana.net 6 points 4 days ago* (last edited 4 days ago)

Yes, you have to be talented not to get lost in the pyenv ('env' as in 'version' management), venv, virtualenv, pyvenv and god knows what else. All those tools either manager versions, virtual environments or both. Super simple! I'm sure you're enjoying working with them and that's fine. I avoid it.

[-] SlurpingPus@lemmy.world 2 points 4 days ago

If a programmer needs a whole ‘standard’ to figure out that two orthogonal tools are all they need, it's not a good sign.

[-] ExLisper@lemmy.curiana.net 1 points 4 days ago

[-] SlurpingPus@lemmy.world -2 points 4 days ago

Learn to RTFM, noob.

[-] tyler@programming.dev 1 points 4 days ago

Have you ever actually read the manual? I have. It’s thousands of words for how to build a single python library. If you look at almost any other language it will be a tenth of that. Ruby’s is literally like 4 commands total. The only people that think Python tooling is even halfway good are people that have never used a language with proper tooling.

https://chriswarrick.com/blog/2023/01/15/how-to-improve-python-packaging/