On Tue, 2018-07-24 at 17:38 +0200, Patrick Ohly wrote:
I'm definitely interested.
I asked, but failed. It seems python folks are covered with more
priority work, at least there where I tried. Thus I'm sorry, I do not
have anyone able to port the files at the moment. I've been redirected
For what I tried myself, by simply changing the shebangs to python3 in
the build-time scripts, some worked, but some failed on the syntax. I
cannot speak of the actual results of those scripts though.
The Arch maintainer filed an issue for the
same problem and attached his own patch here:
I see. It seems there are covered more files, even not in the generic
way as with my patch.
But as you said, the real solution has to be a port to Python3.
it be okay to drop Python2 support entirely?
From my point of view yes, because python2 support will be dropped
of soon anyway: https://pythonclock.org/
Doing so in a 1.5.x maintenance release sounds too intrusive.
I agree, changing dependencies in the stable release is not ideal.
Should I target a 1.6.0 release with Python3 as dependency and also
include my "cxx-future" branch, where I require C++11?
Sounds good to me, though I cannot talk for all interested parties.
Thanks and bye,