| 2017-02-22 09:07:41 |
RJVB |
description |
A priori there is nothing platform-specific in the qarte code, and indeed it works on Mac and MS Windows without significant patching.
There is a difference in the way Python/Mac handles Unicode strings, though, that lead to runtime failure. Attached is a patch that handles the few remaining expressions where this is a blocking problem in basic usage. From the looks of it these are all cases where a filename is retrieved from the server that is UTF8-encoded.
If there is no way to make the `open()` function treat its filename argument as a unicode string then there are probably other locations where equivalent operations are carried out (e.g. in the scheduled loader implementation). |
A priori there is nothing platform-specific in the qarte code, and indeed it works on Mac and MS Windows without significant patching.
There is a difference in the way Python/Mac handles Unicode strings, though, that leads to runtime failure. Attached is a patch that handles the few remaining expressions where this is a blocking problem in basic usage. From the looks of it these are all cases where a filename is retrieved from the server that is UTF8-encoded.
If there is no way to make the `open()` function treat its filename argument as a unicode string then there are probably other locations where equivalent operations are carried out (e.g. in the scheduled loader implementation). Alternatively it should be possible to override/replace the open function with one that calls codecs.open .
Edit: the patch is safe to use on Linux. |
|
