"Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design"—unless you want to do something seemingly simple like using email addresses for authentication, in which case you need to monkey patch models and forms to get everything working right, which is neither rapid nor clean. What began as an innocuous feature request five years ago is now a high-level, general purpose, abstract, seemingly insurmountable design problem. The core developers are still perfectionists, but they seem to have forgotten their deadlines.
Is there not a simple, pragmatic solution (optional and for new installations—we're not talking about backwards compatibility here) that could be implemented until the panacea of pluggable User models gets figured out? Something as simple (albeit ugly) as wrapping new models and forms in: if settings.AUTH_EMAIL_AUTHENTICATION: Should these things really take five years? What happened to pragmatic? Clay -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/KebjFDOOBF4J. To post to this group, send email to django-developers@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.