Closed theGunner295 closed 1 year ago
Currently clean_attributes produces a runtime error when it's referenced as self.clean_attributes() as it's trying to call clean_attributes from sync.py
Having a unique name for it means it'll only ever call the function from within the async class.
I can't repro this and it doesn't make sense that it would ever happen because async classes would be first in MRO list
Currently clean_attributes produces a runtime error when it's referenced as self.clean_attributes() as it's trying to call clean_attributes from sync.py
Having a unique name for it means it'll only ever call the function from within the async class.