2013-11-29, 06:59
As anyone who has run Gotham alpha's since A9 knows, the xbmc.python bump caused a bit of a hassle. On the plus side, that hassle highlighted some bugs, on the minus the constant nagging isn't much fun...
If a change is required anyway due to things being broken, then fair enough, the minimum backward compatibility version needs bumping.
However, if things aren't broken, why force add-on authors to make changes they wouldn't otherwise need to do?
I propose that we revert the xbmc.python minimum versioning to 2.0, under the assumption that it is still backward compatible to 2.0. If it's still compatible, there's no reason to bump it.
Opinions most welcome - if there's a decent reason why it was bumped, then please elaborate what that is.
Cheers,
Jonathan
If a change is required anyway due to things being broken, then fair enough, the minimum backward compatibility version needs bumping.
However, if things aren't broken, why force add-on authors to make changes they wouldn't otherwise need to do?
I propose that we revert the xbmc.python minimum versioning to 2.0, under the assumption that it is still backward compatible to 2.0. If it's still compatible, there's no reason to bump it.
Opinions most welcome - if there's a decent reason why it was bumped, then please elaborate what that is.
Cheers,
Jonathan