News for hackers. Stuff that matters.
Re:Python Application Deployment with Native Packages by hynek on Friday May 04, 2012 @03:50AM (#3927490)
I think you missed one point here: The package _contains_ the virtualenv, so you even _must_ have multiple copies of the same package for every app that needs it.

That’s the whole point of it: have a consistent and reliable way to deploy whole applications including all dependencies.

Re:Python Application Deployment with Native Packages by j-kidd on Friday May 04, 2012 @10:31AM (#3928512)
That is exactly my point - you have to build multiple packages for the same app, even for the same version (app1_venv_a-1.0, app1_venv_b-1.0), if there is a need to have more than one instances of it running on the same machine.

Until emerge/apt-get/yum/etc add support for virtualenv, I will stick with .egg packages and be python-native rather than system-native.

Re:Python Application Deployment with Native Packages by hynek on Friday May 04, 2012 @10:53AM (#3928623)
That’s wrong. The package contains only the application, it’s up to you how you start it. That’s where for configuration (e.g. Puppet or Chef) comes into the game.