There is a file called "validation.py" which attempts to do validation checking for the admin.
Though I realize it might be useful for the beginners (as a basic sanity check) quite often I find it standing in my way and being annoying. The reasons are: 1) Python does not have interfaces. It relies on "duck typing". This file attempts to check whether the class follows the interface, yet in a very naive way. 2) All the check_isseq calls stop you from turning attributes into properties, which can be useful for inheritance purposes 3) sometimes the developer does not want a particular sanity checking. My recent problem was trying to create a widget for a many-to-many field with a custom through table. At the moment it is completely impossible - validation.py will just raise an error, and there is no way to go around it (if you won't count monkey-patching django). Without validation.py I would've been able to specify the widget in the admin settings and just do my own POST-data processing. In my personal opinion this whole file needs either removal, or sufficient relaxation of many constraints. Any thoughts? -- 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.
