|
I think I'd prefer an approach that allowed the current versions of all plugins to continue to work with the current built-in framework compatibility features (stripped down to only the necessary functions if necessary). This would give the individual devs time to make the necessary updates to future-proof their plugins at their own pace.
Sort of a layered approach where hopefully plugins get a few new versions under their belts with their dependencies on compatibility_utils.py removed before the compatibility utils actually go away.
Mainly because users don't always update plugins as regularly as they do Sigil. And if the utils disappear while they're still using older versions of plugins, we'll be dealing with a lot of "update the plugin" support threads/posts.
|