blackwind

It occurs to me that neither of the solutions I've proposed really solve the problem that adding compatibility metadata in the first place does -- if there's no compatibility metadata,...

> I don't know which versioning standard you're using but with semver minor versions should also be backwards compatible. Breaking backwards compatibility should lead to a major version increment. Correct,...

Yet another option for metadata format would be compatibility flags, which would offer fine-grained control: ``` compatibility = { eg.Compatibility.WXPYTHON_3020: True, eg.Compatibility.PYTHON_3: False } ``` If a flag isn't present,...

Yes, I understand how Python works. :P As stated above, the purpose of the `False` value is to denote _incompatibility_. If a plugin developer knows his plugin isn't compatible with...

Just ribbing you. No ill-will intended. :)

So, the compatibility flags method is our winner? No one has any further concerns?

> That way a plugin developer would even know what to change at the plugin without even looking into the change-log of EventGhost. (Only if the flags are properly named...

Anywhere it makes sense to show this information, it'll be shown. This includes plugin install, the "Add Plugin..." dialog, and (hopefully) setup. In the "Add Plugin..." dialog, orange will denote...

If `pip` can be sufficiently bent to our will, I'm in favor of going that route. Doing so would allow us to remove a litany of dependencies from the distribution...

Have you gone through and implemented this in full already, or is it just a really elaborate mock-up? Because it really, really pains me to criticize if it's all already...