UVviewsoft forums

I had no trouble to get Cud up and running on my Linux boxen with Python 3.5 (this is a Debian Stretch based system).

However, some (but only some) plugins I insatlled later on do seem to require a version Python greater than 3.5. I say "seem" because so far I could always patch them with a few trivial changes to run under Python 3.5 as well. Apparently it's not that hard to write code that's compatible with earlier versions.

Of course, what does "earlier" mean? Python 3.4? Python 3.3? Or whatever Python 3 people happen to have on their system?

I'd appreciate it if the Python experts (mostly Alexey and the plugin writers) could agree on some minimal Python version that's REQUIRED (so perhaps some, me included, have to install additional packages) but on the other hand MAKE SURE all plugins are compatible with that minimal version.

Are these Kvichans' plugins?
(see readme/readme.txt)
He said to me that he agree to get patches for Py3.5, if it's minor changes. you can send him Pull-reqs.
Github links are in the install.inf files.

The common rule is that plugins must support 3.5 or 3.6.

Alexey wrote:The common rule is that plugins must support 3.5 or 3.6.

So, 3.5 OR 3.6 means in practice that Python v3.6 is required because 3.6 is backwards compatible to 3.5 but not the other way round. I can side-install a Python version 3.6 or even 3.7 or 3.8 but I am not sure all users could or want to do that.

Alexey wrote:Are these Kvichans' plugins?

At least one of those but possibly more. Also the reworked snippets plugin.

Alexey wrote:if it's minor changes. you can send him Pull-reqs.

Ah, I see... so because some plugin writer is not willing or able to support 3.5 I have to patch his code and send him a pull request? Sure, I can patch Python sources and I could send in a pull request (though only for the few plugins I use)... but what about all the other plugins and the many users who can't do that?

If you want to get more (Linux) users for Cud, IMHO this is not the way to get them.

I can only work on my plugins. Kvichans has his own rules. He wants to drop 3.5. but says he will accept small patches for 3.5.

Alexey wrote:Kvichans has his own rules.

Fair enough.

Alexey wrote: He wants to drop 3.5. but says he will accept small patches for 3.5.

I could understand his wish to drop 3.5 if the changes between 3.5 and 3.6 were so significant that it's just not possible to write plugin code (with reasonable effort) that works for 3.5.

Anyway, I've said what I wanted to say. What you (and any plugin writers) make of it is your (and their) decision.