I agree with Skaperen here. The docs clearly state that the only result of running
Looking at tests to see how internals to Python core work shouldn't (ever) be needed to understand how to use Python, or any library for that matter.
Looking at the source of Python could involve looking at C code, which isn't a viable option for everyone writing Python.
This is a very clear case of the documentation not matching current functionality. Since fixing the bug would involve breaking changes (and returning False to a function who's name clearly indicates it returns a bool), the docs should be updated to more clearly indicate what's actually returned.
issubclass()
is either True, or an exception.Looking at tests to see how internals to Python core work shouldn't (ever) be needed to understand how to use Python, or any library for that matter.
Looking at the source of Python could involve looking at C code, which isn't a viable option for everyone writing Python.
This is a very clear case of the documentation not matching current functionality. Since fixing the bug would involve breaking changes (and returning False to a function who's name clearly indicates it returns a bool), the docs should be updated to more clearly indicate what's actually returned.
Quote:Return True if class is a subclass (direct, indirect or virtual) of classinfo. A class is considered a subclass of itself. classinfo may be a tuple of class objects, in which case every entry in classinfo will be checked. In any other case, a TypeError exception is raised.I don't even see this as a discussion. There's no argument about ambiguous docs, they're just incorrect. Either True is returned, or a TypeError is raised. Any other functionality (such as returning False) is undefined behavior.