That's me trying to get some placeholder material in place so that we have somewhere to start from.
I'll replace this with the solution you mention -- I was hoping to spur someone to test and fix this up, but since that's not yet happened, I'll remove the current page and just put a link to > http://code.google.com/p/modwsgi/wiki/VirtualEnvironments --Mark Ramm On Mon, Apr 7, 2008 at 8:26 PM, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > > I just noticed that this page has been recently added to TG site: > > http://docs.turbogears.org/2.0/Deployment/modwsgi+virtualenv > > FWIW, I find it a bit worrisome that it says: > > Status: Totally untested!!! > Warning: I replaced workingenv with virtualenv, but tested nothing. > > In other words, looks like someone took existing workingenv variant > and just changed names without even verifying it works. It even seems > to still mention workingenv in it which makes it even more confusing. > > I also don't understand why the approach described is even used, as > mod_wsgi site documents how to use virtualenv in a much simpler way: > > http://code.google.com/p/modwsgi/wiki/VirtualEnvironments > > Version 2.0 of mod_wsgi even has direct support for virtual > environment type site-packages containing .pth files. > > The example on mod_wsgi site may be for Pylons, but same approach > works with any Python web framework/application. > > I'd suggest someone may want to review the document on TG site and > make sure it works if you want to keep it. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
