René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Reuse of “exc” name in __init__.py confuses Pylint","articleBody":"It’s not entirely clear how one is supposed to name GitPython’s exceptions:\r\n* According to [the API reference](https://gitpython.readthedocs.io/en/stable/reference.html#module-git.exc), they live in the `git.exc` module.\r\n* In `__init__.py`, the very first line does `from git.exp import *`, meaning they can actually just be referenced in the `git` module instead if one wishes (is that intentional/public knowledge?).\r\n\r\nThen, further down `__init__.py`, there are two places where `except Something as exc` is done in module-level code. While those won’t execute on success (and will prevent the module from importing on failure), they do confuse Pylint: if I try to `except git.exc.InvalidGitRepositoryError` in my own code and then lint it, Pylint complains that `Instance of 'GitError' has no 'InvalidGitRepositoryError' member`, because it believes the name `git.exc` itself might actually be an instance of `GitError` (as it would be if [this `except` clause](https://github.com/gitpython-developers/GitPython/blob/main/git/__init__.py#L59) were taken).\r\n\r\nIs it intended that we refer to exception classes from `git` rather than `git.exc`? If so, could the documentation be updated? If not—if we are not supposed to know about the `from git.exc import *`—could the variable names used in those `except` blocks be modified to not collide with a submodule name?","author":{"url":"https://github.com/Hawk777","@type":"Person","name":"Hawk777"},"datePublished":"2023-05-13T00:26:44.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/1587/GitPython/issues/1587"}