On 15 juil, 18:22, Shawn Milochik <sh...@milochik.com> wrote: > A discussion broke out in our office today about using these features, > because there are blog posts[1] bashing them and a comment by JKM > saying they should go away[2]. > > It seems that all of the arguments against are based on the fact that > there were bugs in the past (links in the comments of the blog post > above). However, the "go away" comment is five years old and they're > still there, and the bug tickets have been patched.
Indeed. > It's easy enough to do what these features do in a more explicit way. Yeah, quite a lot of things are "easy to do in more explicit way" in Python (if by explicit you mean low-level). Who needs a class statement ? Just call type() with the relevant args, that's way more explicit... ;) > Considering these facts, I'm wondering what the consensus is in the community: > > A. They're still there because they're too annoying to deprecate > or just not important enough to spend time on. > > B. They're useful shortcuts and their use is preferable to manual > replacements. As far as I'm concerned, a named argument in a field definition is "more explicit" than some ad-hoc code in a model's save method. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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.
