Migrating to Pipenv is actually really easy. Pipenv checks this when installing to make sure that you are installing the dependencies you think you are. With Pipfile.lock, every dependency has a hash that is generated from the package contents-so if the package contents change, the hash would change. Malicious code could be added without anybody knowing, and that is dangerous. This way you can know if the dependency has in some way been modified but the version number has not changed.Ī dependency can change without its version number changing if, for example, someone hacks into where the dependency is stored and modifies the dependency without you knowing. When downloading the dependency, if it does not match the hash for that version, it won't work. It's safer to use Pipenv than virtualenv, because every dependency installed has a hash which is saved in a file called Pipfile.lock.It's easier to work with Pipenv than virtualenv and pip, because it creates the virtual environments for you and manages them too.The two main reasons to migrate for this course are: There are more reasons to migrate when doing larger applications. There are two main reasons to migrate to Pipenv for this course, and for small application development. This blog post is to help students of the first course migrate to Pipenv, since that's used in the second course.

However, the 'beginner' course-REST APIs with Flask and Python-used virtualenv. Our most recent course, Advanced REST APIs with Flask and Python, uses Pipenv.

Pip env