On Mon, Dec 7, 2009 at 11:05 AM, Adrian Holovaty <adr...@holovaty.com> wrote: > My preference is (slightly) for class-based, because it's (slightly) > less magic. I think we should try to avoid requiring people to > remember what to name things.
I like this as well, albeit for a slightly different reason: asking you to provide the name of the class implementing the API puts one less constraint on how your code gets laid out, and so allows people to organize their code logically rather than according to how we expect them to name things. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." -- 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.
