|
Once again, strings are being changed to unicode literals throughout calibre's codebase. This is the best incremental way to minimize regressions when moving to python3.
And I will note that calibre has not used bytestrings for paths for almost a decade. The original python2 decision to use bytestrings for paths was probably inspired by linux's bone-headed decision to have paths be bags of bytes in unknown encodings. I reversed that python 2 mistake a long time ago. So using them in recipes is unsupported. You should have been using unicode literals in recipes, anyway.
|