On 28 sep, 10:02, Benedict Verheyen <benedict.verhe...@gmail.com>
wrote:
> 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?
I'd be tempted to answer : all of Python - hence my opinion that at
this point it's more about learning Python than anything else.
But the most obvious points are probably about Python's execution
model:
* what happens when a .py file is loaded into the interpreter, whether
thru direct execution ('> python somefile.py') or via an import,
* modules, packages, and the pythonpath
* import hooks and how django use them
> 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 is already explained in Python's fine manual.
> 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
> - ...
Ok, this is more Django-specific, and I agree that sharing experience
on these points might be a good thing.
> 2. Splitting models & views
It's a more general pattern: turning a module (single .py file) into a
package without breaking client code.
> 3. How can you cleanly seperate an application further from a project
Part of this topic is mostly generic dependencies management, but
there are indeed quite a few Django-specific points here.
> 4. Building reusable applications
There are already some threads, blog posts etc on this, but I've met a
couple issues never adressed so far.
> 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.
