To be fair, I only had one small pet peeve with the current views API after trying the alpha: the use of self.args / self.kwargs.
There's added value on being able to see which parameters a view expects by seeing it's method signature: def publisher(request, publisher_name): publisher = get_object_or_404(Publisher, name__iexact=publisher_name) ... As opposed to (from the release notes): class PublisherBookListView(ListView): ... def get_queryset(self): publisher = get_object_or_404(Publisher, name__iexact=self.args[0]) ... Using keyword arguments help a little more, so you don't pass values around blindly based on indexes only. Still, the keyword will be lost somewhere in the middle of the method. It's a lot less clear than just checking a method signature. In 1.x, I liked the fact of having reverse() automatically fail loud when the method signature didn't matched my URL pattern. That helps to catch a lot of views-urls mismatches. Can that behaviour be replicated with the class-based API by overriding it's __init__, instead of tucking parameters away on self.args/kwargs? Or there's really a philosophy that views should just trust URL pattern matching? On 11 nov, 22:30, Łukasz Rekucki <lreku...@gmail.com> wrote: > On 12 November 2010 01:16, hcarvalhoalves <hcarvalhoal...@gmail.com> wrote: > > > What about having an official 1.3 feedback thread at django-developers > > list? ;) > > > I'm liking the pack of small improvements coming in this release, and > > timing is very good, well done. I must say I'm less than happy with > > the view classes though. Is the API on it frozen already? > > IMHO no, but it reached a point where the only way to make it better > was to have it released to the wild and see how people use it. I'm > personally interested in all and any feedback on the class based > views. There's a few thing I would like to improve myself, but just > didn't have the time to sit down and do the work. > > > > > On 11 nov, 05:34, James Bennett <ubernost...@gmail.com> wrote: > >> The first alpha preview package for Django 1.3 is now available. > > >> * Release notes:http://docs.djangoproject.com/en/dev/releases/1.3-alpha-1/ > > >> * Download instructions:http://www.djangoproject.com/download/ > > >> -- > >> "Bureaucrat Conrad, you are technically correct -- the best kind of > >> correct." > > -- > Łukasz Rekucki -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.