René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Define own hierarchy of exceptions?","articleBody":"# Situation\r\n\r\nCurrently, our code catches an invalid version and raise an exception. This is good. However, the exceptions are usually builtin exceptions like `TypeError`, `ValueError`, or `AttributeError`.\r\n\r\nThis could make it likely, that an semver exceptions are \"hidden\". It cannot explicitly be checked that a `TypeError` is coming from semver and not from another, unrelated third party library.\r\n\r\n# Proposal\r\n\r\nThis part could be solved by introducing our own hierarchy of exceptions like so:\r\n\r\n```python\r\nclass InvalidVersionError(ValueError):\r\n    \"\"\"Raised by invalid parts in a semver version\"\"\"\r\n```\r\n\r\nThe nice thing about this approach is, any old code would still work (as `InvalidVersionError` is derived from `ValueError`).\r\n\r\n@python-semver/reviewers  would that be an option?\r\n","author":{"url":"https://github.com/tomschr","@type":"Person","name":"tomschr"},"datePublished":"2020-05-07T07:53:09.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/248/python-semver/issues/248"}