Dmitry Selyutin wrote:
> hopefully most Unices
> either have Python 3 by default or at least have it in repositories, ports,
> etc.
Yes, they do. You can assume Python >= 3.2 nowadays when you invoke 'python3'.
[1]
'python2' is also widely deployed [2]; I assume that's because of backward
compa
Dmitry Selyutin writes:
> Wow, that's a surprise. Sure, we must support all Python 3 versions. Thank
> you, I've applied it. Please check if everything is OK, I'm not a Git guru:
> since parser and config were a bit ahead, I did the same as you did,
> committed, then exported a patch via $(git
Hi Mathieu,
thank you for submitting it.
> Here is a patch that removes the use of 'enum.Flags' that didn't exist
> until python 3.6. It seems that 'enum' classes are not well supported
> with older version too. So it seems more reasonable to not use them at
> all.
Wow, that's a surprise. Sure,
Hello,
I have checked the "python" branch.
Here is a patch that removes the use of 'enum.Flags' that didn't exist
until python 3.6. It seems that 'enum' classes are not well supported
with older version too. So it seems more reasonable to not use them at
all.
>From 84b81d499f2b926c2771ed700b01