this post was submitted on 04 Jul 2023
22 points (95.8% liked)

Python

6421 readers
27 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
 

Simple Python [executable] version management, that is.

top 16 comments
sorted by: hot top controversial new old
[–] Andy 5 points 1 year ago (1 children)

I highly recommend rtx over pyenv/asdf. For one thing, you'll still be able to which python and get a useful response, as it works by altering your PATH rather than relinking shims.

[–] brettvitaz 2 points 1 year ago (1 children)

I wouldn’t argue that a useful response from which isn’t a good thing, but how often do you need to use it with Python? I’ve been using pyenv with pipenv for years and almost never need to do this.

[–] Andy 1 points 1 year ago

How often? Sometimes 🤷.

There are other benefits to the tool that may be more meaningful for your usage, but of course I wouldn't claim there's anything wrong with using the tools you like.

I think when I used pyenv it was the single slowest part of my shell initialization.

[–] [email protected] 4 points 1 year ago* (last edited 1 year ago)

I use it everyday. I feel it’s my secret sauce in python dev… pyenv-virtualenv is pretty useful with it also

[–] CodeBlooded 3 points 1 year ago

I found pyenv to be buggy at times, not properly setting the default (global) python version. I ultimately uninstalled pyenv and also uninstalled any additional Python installs outside of the system default.

Now, I do 100% of my Python work inside of Docker containers. This has solved any issues I’ve ever had with Python environments and PYTHONPATH . It’s also made me a stronger developer when it comes to using Docker.

I don’t see myself ever going back. A Docker container is the perfect Python environment.

[–] jeebus 3 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.

[–] [email protected] 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.

[–] [email protected] 2 points 1 year ago (2 children)

Another useful Python version manager is asdf with python plugin. The most helpful feature of asdf is ability to specify what Python version to use in certain directory by simply placing a .tool-versions file (contains the version number to use) in that directory. This makes working with multiple projects that requires different version of Python very seamless.

[–] jim 4 points 1 year ago (2 children)

pyenv also has this with the .python-version file which will switch versions. And with the plugin, you can use virtualenvs in pyenv so that a .python-version can be simply: my-cool-project-virtualenv and switching to that directory automatically switches to it.

[–] [email protected] 3 points 1 year ago

Automatically switching to virtual environment seems like an even useful thing to me. Thanks for mentioning it.

[–] [email protected] 3 points 1 year ago

This is a great feature

[–] jnovinger 2 points 1 year ago (1 children)

Ooh, thanks for mentioning asdf! I've heard of it, but didn't realize it could that

[–] Andy 2 points 1 year ago (1 children)

AFAIU, asdf uses pyenv for its Python plugin, but rtx does it all just a little better.

[–] hosaka 3 points 1 year ago
[–] jim 2 points 1 year ago

I've used pyenv for years and it's an awesome tool. Keeps python binaries separate and it has a virtualenv plugin. I've gotten others to use it as well.

It works great for library owners who need to run tox/nox on multiple versions of python in test suites. Love it.

[–] [email protected] 1 points 1 year ago

I'm just incredibly happy that Fedora has every Python version in its official repo and I don't need pyenv at all.

load more comments
view more: next ›