this post was submitted on 04 Jul 2023
0 points (NaN% liked)

Python

6378 readers
79 users here now

Welcome to the Python community on the programming.dev Lemmy instance!

๐Ÿ“… Events

PastNovember 2023

October 2023

July 2023

August 2023

September 2023

๐Ÿ Python project:
๐Ÿ’“ Python Community:
โœจ Python Ecosystem:
๐ŸŒŒ Fediverse
Communities
Projects
Feeds

founded 1 year ago
MODERATORS
erlingur@programming.dev
jnovinger@programming.dev
norambna@programming.dev
0
pyenv/pyenv: Simple Python version management (github.com)
submitted 1 year ago by jnovinger@programming.dev to c/python@programming.dev
2 comments fedilink hide all child comments
 

Simple Python [executable] version management, that is.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] jeebus@programming.dev 0 points 1 year ago* (last edited 1 year ago) (1 children)

When bringing people online from other languages, I first get them to find out what python there is in their environment and go with that if it's recent enough. Then I tell them about pyenv and it's plugins after a bit. Whenever I go straight into installing pyenv, it feels like I'm throwing some one in the deep ocean.

[โ€“] muppetjones@lemm.ee 2 points 1 year ago

I've seen too many issues caused by relying on the system python. For starters, it's much more difficult to fix if you screw something up.

I tell everyone to use pyenv -- but only to install specific versions of python. I then create a primary venv for a couple of versions, and that's what I use as my "system" version. Each project creates a separate venv based on the pyenv versions. I use autoenv to activate and deactivate as needed.

It's a little more setup, but it avoids so much magic, and it's extremely robust.