On Sun, Apr 5, 2009 at 5:45 PM, Tim Hoffman <[email protected]> wrote:
> > I use virtualenv a lot, but to be honest I don't see a lot of value in > it for the > app engine sdk. > > The sdk isn't installed normally into you python site-packages etc.... > > So you just stick it whereever you want and just run the dev server > with a fully > specified path., and everything is fine, > > I usually use virtualenv becuase I need to install lots of > dependancies (ie zope) > and don't want that in my core python. > > Rgds > > Tim I'm not really speaking for the value of it, but if its possible, how to do it, etc. Specifically however, i was running into issues not using virtualenv because easy_install had polluted my standard python site-packages. So in that case, i was trying to use a module/library in my GAE app, where an older version was downloaded already into the site-packages of my python install, and causing very weird things to happen. In this case, virtualenv would have prevented the issue. But as i mentioned, i'm not debating its usefulness in an AppEngine application. I am simply wondering if its possible, and how its possible. So .. i assume you have not done it, but have you tried? Did you run into issues/etc? Would you mind commenting on the actual problem/question of this thread? -- Lee Olayvar --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
