| 125 | | * Split off as much of !auth.User into orthogonal mixins that can be reused. |
| 126 | | * Modify !auth.User to inherit these mixins. Care must be taken to ensure that the database expression of the new User model is identical to the old User model, to ensure backwards compatibility. |
| 127 | | * Unrelated and third-party apps can indicate that they depend on various orthogonal mixins. For example, contrib.admin can specify that it works with !auth.User out of the box, and with any model implementing !PermissionsMixin if you supply your own login forms. |
| 128 | | |
| 129 | | Exposing pieces of !auth.User as mixins is optional, and potentially advantageous for any solution that allows you to define your own user models, such as solution 2. |
| | 125 | * Split off as much of auth.User into orthogonal mixins that can be reused. |
| | 126 | * Modify auth.User to inherit these mixins. Care must be taken to ensure that the database expression of the new User model is identical to the old User model, to ensure backwards compatibility. |
| | 127 | * Unrelated and third-party apps can indicate that they depend on various orthogonal mixins. For example, contrib.admin can specify that it works with auth.User out of the box, and with any model implementing !PermissionsMixin if you supply your own login forms. |
| | 128 | |
| | 129 | Exposing pieces of auth.User as mixins is optional, and potentially advantageous for any solution that allows you to define your own user models, such as solution 2. |