Python Social Auth's Django App directly references a property that is marked for internal use only.
field = UserSocialAuth.user_model()._meta.get_field(username_field)
The use of _meta here is problematic for applications that are service oriented by nature. If your user store is a service consumed by a client that houses python social auth (like a legacy user store) you should not have to implement all the "internal" stuff (like _meta) that a Django model has. By adding a simple check this could probably be avoided.
Python Social Auth's Django App directly references a property that is marked for internal use only.
The use of
_metahere is problematic for applications that are service oriented by nature. If your user store is a service consumed by a client that houses python social auth (like a legacy user store) you should not have to implement all the "internal" stuff (like_meta) that a Django model has. By adding a simple check this could probably be avoided.