aiida-vasp
No attribute is_active on the User object
We get these errors:
def by_user(left, right):
> if left.user.is_active and not right.user.is_active:
E AttributeError: 'User' object has no attribute 'is_active'
This is used to sort the potential so that the ones supplied by the active user is used first. This is now disabled until we figure out how to resolve this.
@sphuber do you have some suggestions on how to address this in 1.x? Thanks.
The is_active column of the DbUser database model has been removed completely. I removed it because we never really had a concept of an active or inactive user. This was just a remnant of the very first design that piggy-backed of the user model of Django. I would either just remove it, or you can change the logic to prefer pseudos created by the "default user" : orm.User.objects.get_default(). This corresponds to the default user specified in the config.
