#11909: Django 'eating up' method errors in templates
--------------------------------------+-------------------------------------
          Reporter:  wojteks          |         Owner:  nobody
            Status:  closed           |     Milestone:        
         Component:  Template system  |       Version:  1.1   
        Resolution:  wontfix          |      Keywords:        
             Stage:  Unreviewed       |     Has_patch:  0     
        Needs_docs:  0                |   Needs_tests:  0     
Needs_better_patch:  0                |  
--------------------------------------+-------------------------------------
Changes (by russellm):

  * status:  reopened => closed
  * resolution:  => wontfix

Comment:

 Swearing will get you nowhere.

 Neither will ignoring Django's process. If you disagree with a decision
 that has been made, then follow the
 [http://docs.djangoproject.com/en/dev/internals/contributing/#id1 well
 documented process] and start a discussion on Django Developers.

 Implying that the Django core developers (of which I am one) are simpering
 morons won't get you far either. You seem to be forgetting that I, the
 other core developers, and *many* other people have been using Django for
 a *lot* longer than you, and yet somehow we haven't had the entirety of
 our development life sucked into a black hole of hidden template errors.

 I'm open to any reasonable suggestion for how to improve Django. My
 tolerance for irrational ranting is remarkably short.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/11909#comment:3>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to