I use it everyday. I feel it’s my secret sauce in python dev… pyenv-virtualenv is pretty useful with it also
this post was submitted on 04 Jul 2023
20 points (95.5% liked)
Python
6160 readers
3 users here now
Welcome to the Python community on the programming.dev Lemmy instance!
📅 Events
October 2023
- PyConES Canarias 2023, 6-8th
- DjangoCon US 2023, 16-20th (!django 💬)
November 2023
- PyCon Ireland 2023, 11-12th
- PyData Tel Aviv 2023 14th
Past
July 2023
- PyDelhi Meetup, 2nd
- PyCon Israel, 4-5th
- DFW Pythoneers, 6th
- Django Girls Abraka, 6-7th
- SciPy 2023 10-16th, Austin
- IndyPy, 11th
- Leipzig Python User Group, 11th
- Austin Python, 12th
- EuroPython 2023, 17-23rd
- Austin Python: Evening of Coding, 18th
- PyHEP.dev 2023 - "Python in HEP" Developer's Workshop, 25th
August 2023
- PyLadies Dublin, 15th
- EuroSciPy 2023, 14-18th
September 2023
- PyData Amsterdam, 14-16th
- PyCon UK, 22nd - 25th
🐍 Python project:
- Python
- Documentation
- News & Blog
- Python Planet blog aggregator
💓 Python Community:
- #python IRC for general questions
- #python-dev IRC for CPython developers
- PySlackers Slack channel
- Python Discord server
- Python Weekly newsletters
- Mailing lists
- Forum
✨ Python Ecosystem:
🌌 Fediverse
Communities
- #python on Mastodon
- c/django on programming.dev
- c/pythorhead on lemmy.dbzer0.com
Projects
- Pythörhead: a Python library for interacting with Lemmy
- Plemmy: a Python package for accessing the Lemmy API
- pylemmy pylemmy enables simple access to Lemmy's API with Python
- mastodon.py, a Python wrapper for the Mastodon API
Feeds
founded 1 year ago
MODERATORS
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.
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.
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.
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.
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.
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.
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.
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.
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.
This is a great feature
Automatically switching to virtual environment seems like an even useful thing to me. Thanks for mentioning it.
Ooh, thanks for mentioning asdf! I've heard of it, but didn't realize it could that
AFAIU, asdf uses pyenv for its Python plugin, but rtx does it all just a little better.
I'm just incredibly happy that Fedora has every Python version in its official repo and I don't need pyenv at all.
view more: next ›