Kenneth Gonsalves wrote:
> I personally would put everything in one app at the start. If things start to
> grow and you want to reuse that part in another project, or release it to the
> public (and become famous), then it makes sense to factor it out into a
> separate app - maybe a separate project somewhere in your system path so that
> all your projects can use it. Over engineering at the start is usually
> counter
> productive.
Interesting, I'm pretty sure I remember Jacob saying almost the exact
opposite in his Django tutorial at PyCon...
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
