On Fri, 2009-02-13 at 05:07 -0600, Tim Chase wrote: > > I've written about one extreme end of this scale further over here: > > http://www.pointy-stick.com/blog/2007/11/09/django-tip-developing-without-projects/ > > I've gotta admit that I was pretty ambivalent about Malcolm's > ideas here until I needed to rename a project -- at which point > the switch flipped and I realized how correct/useful his > suggestions were on this page. They would have saved me an > afternoon of pain debugging. So all work since then has been > project agnostic.
Which is kind of the point: you shouldn't worry about stuff like what I wrote there until you need it. Even then, projects don't get renamed that often. People get very hung up on "best practices" or doing things the way everybody else is. Fact is, there's nothing particularly wrong with using a project directory or even the project name, providing things remain within that namespace. A large portion of code that's written isn't going to be reusable apps -- they'll be apps for a particular project. Maybe later they'll move around, but, often as not, they won't. The best condition to be in is to understand the choices you're making and know why you're making them. Then you have options down the track. Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
