I really don't know how you think you'll be getting a different response in other frameworks, because the core developers' attitude on this is correct.
There are over 20000 tickets in the bug tracker for a project used by tens of thousands of people. Code has to pass style guidelines, regression tests, documentation must be made, features must be integrated into a release schedule, obscure platform bugs and overall consistency with the rest of the code has to be verified. This takes a *long* time. Adding an extra method to the Model class is something that may take weeks to discuss and to consider in a myriad possible aspects. And what's worse, someone after you will have to maintain the whole thing, because retrospectively removing things is a *really bad* practice on code that you don't own. Discussions take place on the mailing list and chat rooms because bug trackers are not and have never been a place to discuss design decisions or implementation details; just a place to track the progress in the development and status of a bug or feature request. Finally, Django as a framework is *massive*, and really good reasons have to be had in order to increment the line count even more for something that is ostensibly a corner case for people who don't wish to do a bit of additional work by working within the framework's constraints and opinions instead of against them. Unfortunately, given that no framework is as large or feature-complete (Pyramid supports a lot of things, but is against including too much in the core framework and instead depends on external libs), you'll have even *less* luck with other pieces of code. And I would certainly distrust any framework that has less rigor than Django for including features; what core devs giveth, core devs may deprecate on the next release. Also, I beleive your perception of Django's openness if flat-out erroneous. Go try to add an unrequested feature in Rails or Yii without discussion and see how you're welcomed, never mind the fact that both of these framework's development is done completely in the dark for many of the most important features. On Fri, May 10, 2013 at 12:45 PM, Simon <[email protected]> wrote: > Hi. > > I'm a newcomer to both Python and Django and just wanted to share my > experience trying to solve a couple of problems. > > When I started coding in Python a month ago, Django was sufficiently > common in Google searches that it was my first port of call. I've found > quite a few features which I love and a few which seem a little quirky. > > Unfortunately, every time I come across a problem, I seem to end up back > at the ticket system which almost invariably results in lots of people > saying "It's important to me" and a core developer saying (rather > arbitrarily) "I don't see the need" and closing as wontfix. > > Of course, once the ticket has been closed, the only way to appeal is > through the mailing lists. To myself as a newcomer, that just feels like a > way of making further dissent less visible. I'm sure this isn't the case > but that's certainly the feeling I got. > > The most recent example, which prompted this post is > https://code.djangoproject.com/ticket/901 but this is the 5th or 6th time > I've ended up at similar tickets with similar outcomes. I think comment > #20 <https://code.djangoproject.com/ticket/901#comment:20> demonstrates > my point perfectly - While the point being made is valid, the tone and > general attitude is poor to say the least. > > In any case, I shall be moving away from Django before I get too tied to > it. I know this won't impact you in the slightest but I suspect other > newcomers will be doing the same and not taking the time to post. > > All the best > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-developers?hl=en > . > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Andrés Osinski http://www.andresosinski.com.ar/ -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
