On 28/09/2010 0:48, bruno desthuilliers wrote:
> 
> 
> On 27 sep, 17:31, Thomas Weholt <thomas.weh...@gmail.com> wrote:
>> On Mon, Sep 27, 2010 at 4:52 PM, bruno desthuilliers
>>
> 
>>> ??? 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.
> 
> s/module/package/ !-)
> 
> but there's no "magic" involved here - just a naming convention - and
> startapp has nothing to do with it.
> 
>>>> 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?
> 
> Nope, and neither Steve nor I did question your competence. The above
> remark was not specifically about you, and was not intended as
> criticism FWIW, quite on the contrary. Now I don't think there's that
> much Django-specific knowldege involved when it comes to managing a
> growing code base, and Django's manual is about Django, not about
> Python.
> 
> (snip the remaining - Steve already answered better than I could do)
> 

I agree with Thomas that at least some guidelines would be nice.
As what you and Steve have been saying about the need for a "Python for 
Djangonauts" class,
i think it would be a good idea also.
I'm wondering though what specific Python topics you would touch?
One that comes to mind is the use __init__,py and this modules in general as 
this
knowledge is needed to understand how you can split your models and views.

This would be what i would put in the guidelines for code structuring.
Topics i think would be interesting:
1. Project vs App
    - What is a project? When do you use applications?
    - Possible examples of coding structure
        - 1 site in 1 project
        - many sites in 1 project
        - ...
2. Splitting models & views
3. How can you cleanly seperate an application further from a project
4. Building reusable applications
5. Advanced building methods
    - Buildout
    - Virtualenv
    - ...

If we could agree on a list of topics, we can start writing it ourselves.
We have people here with lots of experience regarding these kind of
more advanced topics.
I wouldn't mind to write something on point 2 but that would need
to be verified by someone with loads more experience than me before
it could be published.

Regards,
Benedict


-- 
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.

Reply via email to