Absolutely. The pip install command is perfect for a Dockerfile where your entire filesystem state is captured and snapshotted. It is a poor way to build a de

Absolutely. The pip install command is perfect for a Dockerfile where your entire filesystem state is captured and snapshotted. It is a poor way to build a deb, where dependencies are supposed to be explicit and user-pinnable. That's all! :) Thanks for writing back. (In the Heroku deb example, you can't even guarantee that you are going to get the version back from the server that the deb file says it contains. That's probably by design, because Heroku does not intend to break backwards compatibility with new releases of the client, and wants to force upgrades so that they know that you have the latest version of the client at all times.)