>> Are there any "best practices" tips for swapping among them for >> testing/experimenting? Preferably without causing /too/ much >> damage. :) > > Hey Tim, > > I've added some more instructions to the "Using branches" part of our > documentation. Let me know if this helps. > > http://www.djangoproject.com/documentation/contributing/#using-branches
Yes, thanks! I think with a combo of symlinks and the other response regarding a personalized environment, I think my final solution will be to 1) adjust my $PYTHONPATH to point to a ~/projects/django symlink 2) redirect that symlink to point to various branches of interest My kudos to the Django team...a while back I had started my own framework (what Python programmer hasn't? ;) with a number of goals in mind. However, as I learned about Django, I found that it already had implemented nearly all of what I wanted. There are still the two aforementioned issues that are solved in branches (row-level permissions and schema evolution), but it looks like those will come down the pike and eventually merge with the trunk. Thanks! -tkc --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
