Rather than doing Python + Docker, these folks would rather install .deb packages as means for deployment.
A key part of this process is that we can minimize the complexity of our deploy script by leveraging Debian’s builtin package manager, dpkg.
One of the most important aspects of this strategy is that it achieves consistency and reliability, but still matches our development environment.
At first glance it looks appealing. Deployment involves one command to download, another command to install. If consistency is guaranteed, why not.
On second thought, it's enormous bulky to download GBs for package every time a deployment happens. And deployment may happen every few hours. It doesn't fly for rapid deployment situation.
Being able to build deb package is a nice thing to have, but I'll happily stick to git + Docker workflow.