Quote:
Originally Posted by eschwartz
Aside: it might be more advisable, at least for Windows, to explicitly work with bytes and decode to utf-8. Windows paths are weird and fragile things. But I don't know why your recipe hardcodes a path to C:\ so  |
And I don't know why you are so obsessed with Windows paths. A regular expression for example could have the same issue or any other raw string literal which happens to contain a "\u".
Quote:
|
Report a bug to the Python Software foundation that python2 unicode string literals don't act like python3 unicode string literals and therefore introduce behavior that surprised you.
|
I don't see how this should be a Python issue. Python didn't change my valid raw string literal into a broken unicode raw string literal, calibre did by importing unicode_literals.
Quote:
|
nor contributing to the ongoing development of the recipe subsystem -- so who exactly is supposed to *know* that you're having an issue?
|
I don't know why you think one has to contribute before one can report issues, but my first recipe included in calibre is from 2010. And anyone reading this thread is supposed to know...