hi all newforms-admin has been merged, so you can go back to trunk.
anyway, maybe you can do the same as i do: put a django.pth file in site-packages which includes all the paths to the branches you want to use. just uncomment the one you want to use at a given moment. you can add more paths to the same file, like project paths and such. http://docs.python.org/lib/module-site.html cheers André On Sun, Jul 20, 2008 at 8:13 AM, ge <[EMAIL PROTECTED]> wrote: > > Don't know if this helps for your case, but I simply clone the django > repository using git-svn, and then sym link the django directory to > site-packages in the usual fashion. When you want to switch to a > different branch, its as simple as running 'git checkout <branch- > name>'. You can switch back and forth freely between all the > branches this way. You can only be using one branch at a time this > way, but I'm not in a situation where this matters. > > On Jul 19, 10:19 pm, Rodrigo Culagovski <[EMAIL PROTECTED]> wrote: > > Great, thanks for the advice. > > So, using virtualenv, I basically install two separate environments, > > one for each django version, and manually call "\path\to\djangoversion > > \bin\activate.bat" depending on which version I need? Or is there a > > way to activate the correct version directly from the project itself? > > Using Windows for development, Linux for production. > > Thanks! > > > > Rodrigo > > > > On Jul 19, 9:43 pm, "[EMAIL PROTECTED]" > > > > <[EMAIL PROTECTED]> wrote: > > > Do not install django as part of site-packges. > > > Treat it as a python package like any other. > > > Create two directories: > > > django-0.96/ > > > django-pre-1.0/ > > > > > put the old django in 0.96 (as a sub directory 'django') > > > put the new svn in pre-1.0 > > > > > Then for your projects have your PYTHONPATH set appropriatly. > > > > > because you need django for settings.py, you can not set it in > > > settings. > > > custom env scripts work well (and I recommend virtualenv) > > > > > hope this helps. > > > > > -Doug > > > > > On Jul 19, 9:26 pm, Rodrigo Culagovski <[EMAIL PROTECTED]> wrote: > > > > > > I'm looking foward to trying out the merged newforms-admin on my > > > > upcoming projects. However, I have a few ongoing projects already > > > > developed using pre-newforms-admin django. > > > > I make changes to the projects on my local machine and test them > > > > before comitting them to the remote production sites, so, unless I > > > > want to refactor all these sites, I need to keep the current django > > > > version on my development machine. > > > > Question: Is it possible to have two django versions on a single > > > > machine? Is there a way to tell each project which one to use, maybe > > > > in settings.py? > > > > I realize that it might make sense to refactor the existing projects > > > > to work with newforms-admin, just not sure how much time this would > > > > take for some already considerably complex and extended model > > > > definitions, plus testing, etc. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
