On Sat, Sep 25, 2010 at 8:59 AM, Yo-Yo Ma <baxterstock...@gmail.com> wrote:
> Chuck - Thanks. Perhaps there isn't such room for improvement on the
> topic.
>
> Jacob - It appears to me that you don't read things before you comment
> on them. That's two times in one post. Patience is a virtue, my
> friend.

This conversation may have started as a "lets add an 'in development'
setting". That was very quickly refuted by two members of the
community (one BDFL, and one person that I work with) that told you
pretty clearly that Django best practice already has at least 2
existing solutions that can do what you describe.

The conversation has since devolved into a 'heres all the ways you
could do it right now', and a bunch of people showing you the various
ways that Django configurations can be used to achieve the goal you
describe.

Yes, patience is a virtue. However, in this case, your call for
patience implies that we should have confidence that this is a
productive, on-topic discussion that is leading to a clear design
decision that can be implemented. I've re-read this thread, and I
don't see any indication that this is what is happening.

*You* may think that there is still a feature under discussion. The
remainder of the people in this thread -- who, from a quick mental
count of what experience I'm aware of, have almost 20 years of Django
experience between them (A BDFL and core devs at 5 years each, plus a
number of 2+ year veterans) -- are telling you that this "feature"
isn't needed.  At which point, it's an education activity, and better
suited to django-users.

Yours,
Russ Magee %-)

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to