Use proper typing

[ItsDrike]

Follow PEP 484 and add type hints to all functions in the code-base. These type-hints are currently compatible with both mypy and pyright.

Now that the code-base is compatible with these, you should consider also integrating them into the automated CI/CD github workflows. (If you don't know how to, let me know if you want them added)

Note: I've renamed ormore attribute for Amount class to a more pythonic or_more name and I've also changed the parameter names for Range class from a and z to start and stop

[ItsDrike]

This may be a bit over-the-top for what it's doing, so I will understand if instead of complex logic like this, you'd prefer this code without any overloads and just have less descriptive and less strict function parameters.

[ItsDrike]

Another option to avoid this mess would be to convert this into 2 separate class methods instead of having both logic for minimum and maximum or for range with optional or_more attribute. This could look like this:

class Amount:
    def __init__(i: int, j: Optional[int] = None, or_more: bool = False):
        if j is not None and or_more:
            raise ValueError("You can't specify both the maximum value and set or_more to True.")
        ...  # The original logic
        
    @classmethod
    def from_range(cls, minimum: int, maximum: int) -> "Amount":
        return cls(minimum, maximum, False)
        
    @classmethod
    def from_repetitions(cls, repetitions: int, or_more: bool = False) -> "Amount":
        return cls(repetitions, None, or_more)

However this will result in having 2 class methods acting very similarly to __init__ at which point it may not even be worth it to do this:

x = Amount(1, 15)
x = Amount.from_range(1, 15)
y = Amount(15, or_more=True)
y = Amount.from_repetitions(15, or_more=True)

The decision is up to you, I'll adapt the code to whichever option you pick.

[GrandMoff100]

Let's go with the overloading direction. It distinguishes the the arguments that can be passed explicitly rather than implying those parameters with less strict default arguments.

[GrandMoff100]

Later today I'll implement pyright into a CI/CD workflow that'll run along the same triggers as the flake8 workflow.

[GrandMoff100]

Are there any more changes that you are intending to make before merging this?