Being new in the Python/Django camp (2 weeks) but doing php for several years, I find this a very interesting topic and I would like to extend the question a bit, like "when is an app becoming too big?" The use case here is when you develop a rather complicated "app" which need to have quite some functionality and all bits need to be there for i to work. Mutual dependencies so to speak. I think one such good example is the Satchmo ecommerce app. It's kind of built up as a project of apps, which makes it (unnecessarily?) difficult to implement in an existing site, imho, unless you make it a "sub-site" like shop.domain.com to integrate with a www.domain.com.
Having studying Python/Django intensively these weeks, trying to merge it with my general developing knowledge, I kinda tend to look at this (optimaly) being 1 app, and things like discount, giftcertificate, etc. isn't really apps but modules making up a bigger app or is this "wrong" thinking? Remember, I am very new to Python but not to programming in general and what I realy try to arrive at is to "think Python/Django" - which of course will take its time;-) To sum up, if you write such a "big" app, how is the best and "correct" Django way to organize such code as some files could get really lengthy of code? Surely splitting it up in smaller files is the way to go, but are there any "rules" there? And by the way, yet another one moving from php to python - I just can't understand why I haven't done this long time ago, although better late then never as it's said. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
