Hi Russ and all,
On Wednesday 04 March 2009, Russell Keith-Magee wrote:
>
> 1) Now isn't the time in the Django development cycle for new
> proposals. [...] If you wait a bit, you'll find you get more
> attention for your proposals.
>
Point taken.
> 2) [...] Your proposal spends a lot of time on the how, but not a lot of
> time on the why - that is, why is the idea is required in the first
> place.
>
Actually, if I understand correctly, there are two 'why's I need to answer:
1) Why would an app writer want to use something like this, or, in other
words, why is this a good django-snippet;
2) Assuming the above, why I think it belongs in django.conf and not
djangosnippets.org.
In short, the answers are that I think the benefit to the app-writer is better
abstraction, making the code more tool-friendly and more self-documenting;
the benefit to django as an ecosystem is standardization; and the benefit to
django as a framework is better control of application settings (allowing
easy implementation of, e.g, name-spacing tricks under a rug the applications
stand on, transparently).
But, taking your first point, I will return to elaborate on this later, and
for now just do my best to help the 1.1 effort.
Thanks again for your attention,
Shai.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
