Follow

Activate the virtualenv named like the root of your git repository (my current sensible venv naming scheme):

alias work='workon $(basename $(git rev-parse --show-toplevel))'

@rixx have a look at pew.

It let's you manage venvs, and keeps track of the source dir for each of them. (as well as a few other nifty features)

@mathieu Huh, switching from virtualenvwrapper to pew seemed a lot of effort for the one missing feature I just solved in a one-line alias at first, but pew looks interesting enough to tempt me. Thanks for the tip, I think I'll look into it later!

@rixx I went through exactly the same thought process a couple years ago, wondering whether it really was worth it.

It was. ☺

@ninja @rixx I have not.

Last I checked it was missing a bunch of stuff I liked in pew.

But that was a while ago, I should probably give it another go.

@ninja @mathieu For a large variety of reasons, I'm not moving to Pipfile any time soon. Many of my environments rely on a setup.py, and I'm not willing to have separate workflows between the two of them.

Sign in to participate in the conversation
chaos.social

chaos.social - because anarchy is much more fun with friends.
chaos.social is a small Mastodon instance for and by the Chaos community surrounding the Chaos Computer Club. We provide a small community space - Be excellent to each other, and have a look at what that means around here.
Follow @ordnung for low-traffic instance-related updates.
The primary instance languages are German and English.