On 09/27/10 09:57, Thomas Weholt wrote: > On Mon, Sep 27, 2010 at 10:38 AM, bruno desthuilliers > <bruno.desthuilli...@gmail.com> wrote: >> Using the package's __init__.py as a facade is certainly not "hackish" >> - it's one of - if not the main - the raison d'être of this file. >> >> Now if your app is really growing that big, it's probably time to >> refactor it into a set of related, more specialized apps. It's not as >> easy as just splitting the models / views / whatever as sub-packages >> of a same app, and doing so afterward will probably be more painful >> than designing it right from the start, but in both cases it has the >> benefit that it forces you to think about dependancies management, >> which can greatly helps when it comes to maintainance. > Ok, I see your point, but still - there`s nothing about this in the > main django documentation as far as I know. The docs should have a > section about organizing projects where the standard models.py and > views.py doesn`t fit anymore. >
It's not there as it's a plain Python feature. Please read about it on Python site here - http://docs.python.org/tutorial/modules.html#packages. I've no idea if there are links to Python docs in the first djangobook chapter or on the Django's Introduction page. If such feature should be explained on Django docs, every other Python feature should be there as well. We come to this pretty often in MooTools community - it has to clearly be said that framework is just extending the language. Regards Piotr Zalewa -- blog http://piotr.zalewa.info jobs http://webdev.zalewa.info twit http://twitter.com/zalun face http://facebook.com/zaloon -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
