On Mon, May 12, 2014 at 12:09 PM, David Malcolm <djmalc...@gmail.com> wrote: > thanks for your reply WB. > > I was hoping to avoid virtualenv. My webapp is a frontend to a vulnerability > scanner in a large corporation. > They are very picky about what I can use and what I can't. Is virtualenv > suitable for such a production system?
If I ever come across a production system where a python app is not installed in a virtualenv, I consider that a bug. virtualenv is the basis of all of our python production systems (our dev systems too). > They insist that I cannot use mod_wsgi (it annoys me intensely, but hey > that's life) and HAVE to use mod_python. mod_python is old, insecure, unmaintained, unmanaged - and most importantly - not supported for django. > Is there any other way to get this working without virtualenv? Find the right person to talk to your in your org, tell them that mod_python is dangerous, and that virtualenv is the industry standard way of deploying a python application, and that wsgi is the industry standard way of connecting a python web application to a web server. Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAFHbX1KKVS_ULyJi%3DEOG8n10yn5AO775U3-5qF-sq6zavADgeA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
