On Sat, Oct 2, 2010 at 1:40 PM, Russell Keith-Magee <russ...@keith-magee.com> wrote: > On Sat, Oct 2, 2010 at 7:05 PM, Patryk Zawadzki <pat...@pld-linux.org> wrote: >> Classes that represent real objects have state. Like cars have color, >> make and registration number, your models have attributes that >> differentiate them from other objects of same class. >> >> "Utility" classes (usually singletons) that represent a function >> (service) should not have state. > Ok, now show me keyword in Python that identifies a class as a > "utility class". Or the page in the Python documentation where it > talks about "utility classes" and how you identify them and use them > properly.
There is no Python documentation that teaches you how to write good and robust code. There are only docs that tell you what "print" or "raise" does. I wouldn't pick software engineering during my studies if I expectes language references to teach me all there was about programming. > You can't, because Python doesn't make that distinction. Python has > classes. Class instances have state. Period. People certainly write > classes that are stateless. But providing a base API based around > classes, encouraging people to subclass and add their own behavior, > and expecting *documentation* to prevent them from using self is > complete folly IMHO. I was going to respond to that. I wanted to mention things like compiled languages and their expectance of you being able to write good code. I respect you too much to drag you through that. After all I am not forced to use whatever the standard becomes. If I am ever forced to use this sort of class-based views, I'll file bugs, until then I'll try to remain quiet. There are more important decisions to be made. Cheers, -- Patryk Zawadzki -- 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.
