I'm sorry if I came across that way, that wasn't my intention at all. Andre Terra who was the one to initially raise opposition has changed his stance on the functionality since he first posted, as per his email 4 days ago. Aside from him there is Tino de Bruijn who voiced opposition, although he seems to be the only other person in the history of the thread (not counting your post just now). There was also Michael van Tellingen, however I'm not 100% sure what his position on the topic is.
>From my count there are 8 people in this thread in support of the functionality, and 2 people against it (1 at the time of my previous message). I figured that to be a good amount of support for the feature, and having not had any direction from a core dev at that time (that I was aware of anyway, once again excuse my ignorance if that is not the case) I decided to go ahead and try and get something moving. In regards to your concerns, which mainly seem to be in regards to how many people would actually utilize this feature / are currently working around it I'm not sure how to address that. I suppose mixins are the solution for now then, however it does seem to me like something that anyone who is making extensive use of class based views will eventually come up against. Cheers, Jordan On Tuesday, 6 November 2012 12:07:19 UTC+13, Russell Keith-Magee wrote: > > > On Tue, Nov 6, 2012 at 2:20 AM, Jordan Hagan <[email protected]<javascript:> > > wrote: > >> As it seems that there is no longer any real opposition to this ticket >> (if there is, now would be the time to speak up) I'll go ahead and prepare >> a patch against the current trunk and get it uploaded to trac and see where >> we get to from there. >> >> Hopefully I'll get a chance to take a look at this this week, I'll post a >> link to the trac ticket here once I've opened it. >> > > It's a bit presumptuous to say there's "no longer any real opposition" > when the people who raised the original opposition haven't said anything. > > I haven't seen anything that addresses my original concerns -- that this > is a niche requirement that complicates the default case, and can be > achieved in end-user code for that small subset of people that are affected. > > The internal mechanics of CBVs are already complex. I'm afraid I still > don't see the general-purpose value in what is being proposed here. > > Yours, > Russ Magee %-) > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/Eny_7ct5I78J. 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.
