Feature request: concise "compatibility" matching

I’d really like a concise expression for “is version x compatible with version y?”

Specifically, suppose I write code against one version of an API, and the API exposes a semver-compliant version. Is v_caller compatible with v_api?

The most concise expression I can come up with is something like v_caller <= v_api and v_caller.major == v_api.major, but I really wish this was simpler and more readable. Maybe v_caller.compatible(v_api); or maybe v_caller.can_call(v_api) better illustrates which operand is which.

I know this would be covered by #241, but its scope is quite broad. I wanted to specifically call out this feature.

[tlaferriere]

From what I understand, the current a.is_compatible(b) shows if you could replace package b with package a without any problems right? I don’t think the is_breaking would reflect that behaviour at all?

Just so I understand

• 1.2.0 is compatible with 1.1.1
• 2.0.0 is not compatible with 1.1.1
• 1.1.1 is compatible with 1.1.1
• 1.1.0 is not compatible with 1.1.1

Right?

@Lexicality you are very right indeed. The direction of the relation I was talking about was not that of the dependency, but the bump (I totally misunderstood that). Therefore this would make more sense:

def is_compatible_with(self, new: Version) -> bool:
    ...

Or

def is_compatible(old: Version, new: Version):
    ...

So please disregard anything I said about dependency relationships, and replace it with old/new relationship instead 😅

[Lexicality]

From what I understand, the current a.is_compatible(b) shows if you could replace package b with package a without any problems right? I don’t think the is_breaking would reflect that behaviour at all?

Just so I understand

• 1.2.0 is compatible with 1.1.1
• 2.0.0 is not compatible with 1.1.1
• 1.1.1 is compatible with 1.1.1
• 1.1.0 is not compatible with 1.1.1

Right?