You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Could you show me an example where _meta doesn't work? _meta is populated by Django ORM when the model class is defined, you can't do getattr(User, 'username'), that will drop an attribute error since the model class doesn't have that attribute.
Python Social Auth's Django App directly references a property that is marked for internal use only.
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.The text was updated successfully, but these errors were encountered: