virtualenv definitely makes testing python modules a lot easier allowing you to create/purge a development sandbox quicker and painlessly. I don't think their mutually exclusive as you can use either or both in combination as your development requires. But if you've got one development machine and cant afford the resources to allocate to a VM, then virtualenv is the way to go.
Paul On Apr 22, 9:46 am, Mark Ramm <[email protected]> wrote: > You are always free to not use virtualenv. It's recommended to make > life easier, but if for whatever reason you think you know better, > it's probably because you actually do. After all, you're the one who > knows the details of your situation and we don't. > > Remember we're not all doing things the same way. > > --Mark Ramm > > On Wed, Apr 22, 2009 at 9:47 AM, Kirk Strauser <[email protected]> wrote: > > > I understand the point behind suggesting that users install TG2 in a > > virtualenv, but is it *always* necessary? I'm installing TG2 in a FreeBSD > > jail that's built specifically to run a TG2 webapp and absolutely *nothing* > > else. Assuming I ensure that all dependencies are up to date, can't I call > > that good enough? > > -- > > Kirk Strauser > > -- > Mark Ramm-Christensen > email: mark at compoundthinking dot com > blog:www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
