This is a good start, but it has issues. You probably don&#x27;t want <i>all</i> of your locally installed packages in a requirements.txt file. Instead, they should be curated. I&#x27;ve been using pip-compile [0] for a while now (see the author&#x27;s blog post [1] for a detailed explanation) and have become a big fan of it. With this model, you should enumerate only what your application uses directly and let pip-compile convert this list to a full version-locked requirements.txt. (Shameless plug: I also wrote a bit about why this is the best currently available option for specifying Python dependencies [2].)<p>[0] <a href="https:&#x2F;&#x2F;github.com&#x2F;nvie&#x2F;pip-tools#example-usage-for-pip-compile" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;nvie&#x2F;pip-tools#example-usage-for-pip-comp...</a><p>[1] <a href="http:&#x2F;&#x2F;nvie.com&#x2F;posts&#x2F;better-package-management&#x2F;" rel="nofollow">http:&#x2F;&#x2F;nvie.com&#x2F;posts&#x2F;better-package-management&#x2F;</a><p>[2] <a href="https:&#x2F;&#x2F;www.jonafato.com&#x2F;2015&#x2F;12&#x2F;15&#x2F;Rethinking-requirements-txt" rel="nofollow">https:&#x2F;&#x2F;www.jonafato.com&#x2F;2015&#x2F;12&#x2F;15&#x2F;Rethinking-requirements-...</a>