Florian has raised the issue of custom user models which define these methods, "Allowing custom user models to have a method is a security risk since all checks will now return true." I proposed a compatibility system check error to detect that situation to alert the user. Do you think the backwards incompatibility is justified here or do you prefer some other solution? I cannot think of much we could do besides monkey-patching the custom-user model.
On Thursday, December 3, 2015 at 3:54:39 AM UTC-5, Aymeric Augustin wrote: > > 2015-12-03 7:02 GMT+01:00 Josh Smeaton <josh.s...@gmail.com <javascript:>> > : > >> I think we should be asking.. why not? If there's not a good reason not >> to, let's make it a callable and a property. >> > > The original discussion dates back to 2008; back then I believe we were > slightly more resistant to change, especially when it came to complicating > things to increase user-friendliness ;-) > > -- > Aymeric. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/92b34bce-c875-45d1-b6b7-95b5b9857ea6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
