On 9/27/2010 11:31 AM, Thomas Weholt wrote: > On Mon, Sep 27, 2010 at 4:52 PM, bruno desthuilliers > <bruno.desthuilli...@gmail.com> wrote: >> On 27 sep, 12:55, Thomas Weholt <thomas.weh...@gmail.com> wrote: >>> On Mon, Sep 27, 2010 at 12:40 PM, Steve Holden <holden...@gmail.com> wrote: >>>> I think the point is to learn enough Python that you don't need >>>> Django-specific advice. >>> >>>> [Thinks: definitely time for a "Python for Djangonauts" class]. >>> >>> I`m asking for a best-practice advice, and have gotten plenty of good >>> examples of ways to solve this "problem", but I still think this >>> should be covered by the standard django docs anyhow, >> >> What would you suggest exactly ? > > I section under "The model layer -> Advanced" called "Organizing > models and code in larger projects". Details on how to splitting > models over several files, if and how you should seperate logic from > models etc. > >>> especially since >>> there are some django specific magic related to the files generated by >>> using manage.py startapp. >> >> ??? Which "django specific magic" ??? > > I was referring to syncdb. As far as I know, models defined outside > any models.py or models module won`t be picked up by syncdb, but I > might be wrong. > An addition to the documentation about why your models may not be picked up could well be useful.
>> >>> It`s obviously not clear to all django users >>> how to best handle growing projects, split into modules etc >> >> I can only second Steve on this : time for "Python for Djangonauts" >> class then. FWIW, I'm amazed at how many persons seem to pick up >> django without any background in Python. > > Hmmm ... do you or Steven know anything about my programming > background? My googling and even answers on this thread seem to > indicate that I`m not alone pondering about how to organize my django > code. I know how to structure my code in modules, but for > re-usability`s sake for instance it would be nice to have some > guidelines on how to structure your code in larger django projects and > it would be nice to have those guidelines in the otherwise excellent > django docs. > Hold hard, there! That's Steve, not Steven, Thomas. And I was musing about it being an opportunity to write and promote a new training class, rather than specifically suggesting that you personally needed training. >> >>> and just >>> taking some of the info in this thread, re-writing it and giving a few >>> examples and then adding it to the std docs would be enough. >> >> Mmm... Not sure this would help. A pointer to Python's doc and a >> strong emphasis on the fact that you definitly have to learn Python to >> go any further would be more helpful in the long run IMHO. But well, >> if you think you can contribute something useful, please go ahead and >> submit your patch to the team - it's an OSS project, isn't it ? > > I`m trying to contribute to the django community by writing code, > reusable apps, being active on gropus like this etc. I could even try > to help out writing docs, but if my questions are going to be answered > by people who question my competence that wouldn`t be very motivating, > would it? > I don't think anyone's questioning your competence, and your desire to help in a community-spirited way is very welcome. But you should realize (and probably will if you think about it) that many people who do ask questions on this list could use better Python knowledge than they currently have. If you aren't in that position then fine. > I`ll take all the hints and advice given in this thread and try to use > it to organize my ongoing project. Thanks for your time, everyone. > You are correct in saying that the Django docs are excellent, but there's only so much they can do. If you do come up with useful guidelines I am sure that nobody is going to complain if you submit a patch to the docs. One of the issues is that size is not the only metric of complexity, and it's difficult to frame generic advice about the organization of large projects. regards Steve -- DjangoCon US 2010 September 7-9 http://djangocon.us/ -- 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.
