Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why can't we always use
getattr_static? If there's a reason for not using it always, please describe that in a comment.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is related to my latest comment. Sorry, I didn't make this clear:
getattr_static(...,'__class__')returns<attribute '__class__' of 'object' objects>whereasgetattrwould return<class '__main__.Foo'>. What should getmembers return? Usinggetattr_staticfor every attribute doesn't seem to be the solution. It works fine with methods, functions and properties, but some edge cases seem to requiregetattr(such as__class__). It is not clear what the expected behaviour is.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it, well, describe this in a comment :)