3 ms·
> python3 -m venv venv && source venv/bin/activate && pip install -r requirements.txt ... bless my `zsh` shell history for these incantations. I don't think I
by kaidon 5y ago
> python3 -m venv venv && source venv/bin/activate && pip install -r requirements.txt
... bless my `zsh` shell history for these incantations. I don't think I have any hope of remembering it -- probably because of all the old virtualenv incantations!
Kind of agree with pipenv though. It's painfully slow, but it abstracts away having to worry about various requirements files (eg: dev vs prod) and the .lock keeps things consistent.
- nsotelo 5y agoI use this same setup but with a requirements folder. Inside I have a base.txt, dev.txt and tests.txt where dev.txt starts with '-r tests.txt', etc. It's very handy for having different environments but doesn't lend itself to a lockfile.