I found a corresponding bug report in Debian (see the attached bug watch) with the same error message. It looks like it is resolved in newer version with the Python3 port, but I don't know the scope of that or if a minimal fix for the specific line in the error message would be enough.
I found a corresponding bug report in Debian (see the attached bug watch) with the same error message. It looks like it is resolved in newer version with the Python3 port, but I don't know the scope of that or if a minimal fix for the specific line in the error message would be enough.