On Tuesday, August 25, 2015 at 4:51:51 PM UTC+2, Carl Meyer wrote: > > > I think likely the root problem here is that your monkeypatch is in a > module which is not imported when validation runs. If I were you, I'd > make sure that your `admin.py` imports whatever module does the > monkeypatching, and then I'd expect this error to go away. >
Yes, Django does not "know" about patched user in a validation stage. I will try to change it, but this is an example only. PS. I would like to avoid any monkey patches, hacks, and just omit obstacles. :) Django is a good (the best?) web framework for rapid development, but sometimes is a part of a bigger stack. In that case some unnecessary Django`s limitations/forcings may be problematic to maintain whole projects. BR, Marcin -- 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 http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/94d8fbf8-7e0e-49d5-81e4-2d1372ac3fca%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
