René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Git.version_info type annotation is overly specific in length","articleBody":"The `version_info` property is declared to be a length-4 tuple:\r\n\r\nhttps://github.com/gitpython-developers/GitPython/blob/afa575454f85b34800460881cc9c3cd7fe78c8e3/git/cmd.py#L833-L841\r\n\r\nBut it often has fewer values, which is intentional:\r\n\r\nhttps://github.com/gitpython-developers/GitPython/blob/afa575454f85b34800460881cc9c3cd7fe78c8e3/git/cmd.py#L814-L826\r\n\r\nSo the type annotation should be changed, but I am unsure what it should be changed to, whether any additional documentation should be added, and whether having fewer than some number of numeric fields should be treated as an error and cause an exception to be raised.\r\n\r\nIf the type annotation should reflect that only a few specific lengths are reasonable, then it could be expressed as a `Union` of specific-length `Tuple` types. Otherwise it could be expressed as a variable-length tuple by writing the type as `Tuple[int, ...]`.\r\n\r\nI recommend this be solved in such a way that the `cast` can be removed. Currently, the `cast` is working around ambiguity in how the return type is intended to be understood.\r\n\r\nThis is separate from #1829, though I noticed it while looking into that and they could possibly be fixed (or improved or otherwise closed) together.","author":{"url":"https://github.com/EliahKagan","@type":"Person","name":"EliahKagan"},"datePublished":"2024-02-19T02:31:52.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":8},"url":"https://github.com/1830/GitPython/issues/1830"}