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
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 '. You can switch back and forth
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
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.
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,
5 matches
Mail list logo
