[issue46094] Missing unit test on unittest.TestResult to check for required arguments

dhruv added the comment: "Required" meaning that we cannot remove them from the constructor signature even though they aren't used within it. Hope that clears it up! -- ___ Python tracker <https://bugs.python.o

[issue46094] Missing unit test on unittest.TestResult to check for required arguments

Change by dhruv : -- status: open -> pending ___ Python tracker <https://bugs.python.org/issue46094> ___ ___ Python-bugs-list mailing list Unsubscrib

[issue46094] Missing unit test on unittest.TestResult to check for required arguments

Change by dhruv : -- keywords: +patch pull_requests: +28351 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30132 ___ Python tracker <https://bugs.python.org/issu

[issue46094] Missing unit test on unittest.TestResult to check for required arguments

New submission from dhruv : stream, descriptions, and verbosity seem like they aren't needed at first glance but are required to work with multiple inheritance. A simple test can clarify this. -- components: Tests messages: 408674 nosy: DreamSh0t priority: normal severity: normal

[issue25797] Default argument values with type hints break type correctness

New submission from Dhruv Rajvanshi: Specifying default arguments break the type system. The types of default values aren't matched with the type of the argument. Moreover, having None as a default value changes the type declaration to Optional[T]. So, the declaration may be f(a : int