virtualenv venv —-python=python3.7
touch requirements.txt
echo "flask" > requirements.txt
source venv/bin/activate
pip install -r requirements.txt
Done, what’s so difficult about that?
touch requirements.txt
echo "flask" > requirements.txt
source venv/bin/activate
pip install -r requirements.txt
Done, what’s so difficult about that?
Yes, pipenv is mostly just a frontend to pip+venv, but that doesn't mean it isn't useful.
requirements-dev.txt
pip install -r dev.txt
pip freeze > prod.txt
And then on production environment:
pip install -r prod.txt
The same time I think there is some corner cases. As nature of the python packages can be a bit different comparing to the other packaging systems. File setup.py actually is python file and it is executed when processes. So, it possible that depending on existence of some libraries on your system you will get very different results. For example packages can require very different dependency if you build on Windows or Linux. This case hashes can't do much to guaranty consistency.