Quote:
Originally Posted by chaley
The plugin updater processes Abstract Syntax Trees to find the information. ASTs don't compile the source, so the eventual value isn't visible.
You could test if this is the problem by changing the plugin zip to put the text of the version number in plugin.../device/driver.py instead of the reference.
|
I tried to run the plugin_updater locally, but, I am using Windows and there was enough code in it that is non-Windows (os.rename fails if the destination exists), that I ran out of patience fiddling to fix that.
Looking at the history of it, the last change was in November. Which is before the last version of the plugin that is showing on the updater. And I don't see any difference in how the plugin is defining the version. So, I don't see why there is a difference. Unless the version of the plugin updater on the server is not the same as the version on Github.