Re:Python Application Deployment with Native Packages
by oasisbob on Friday May 04, 2012 @01:34AM
(#3927192)
For some environments, this may be the case.
I find native packaging to be really helpful in mixed environments. On a daily basis I need to deploy Rails/PHP/Python, and using a native package manager is a nice common denominator.
When I first heard about this strategy I thought it was crazy -- but have since come to really like it.
Re:Python Application Deployment with Native Packages
by sciurus on Thursday May 03, 2012 @10:49PM
(#3926787)
Sure you can have multiple version installed with native packages; for examples, see the discussion at https://groups.google.com/group/devops-toolchain/browse_thre...
Re:Python Application Deployment with Native Packages
by j-kidd on Friday May 04, 2012 @03:46AM
(#3927482)
Of course, it has always been possible to have multiple versions installed with native packages. Gentoo supports that since day 1. What I was talking about though (and I didn't make it clear), is having the same version installed multiple times in different locations (i.e. separate virtualenv).
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.
1. activate virtualenv
2. run `easy_install -U app`
and no root permission is required. It also has the added benefit to allow having multiple copies of the same package in the same machine [1], which can't be done with native package.
[1] In one deployment, we have staging instance and production instance in the same machine...