Quote:
Originally Posted by eschwartz
"regression" does not mean "it behaves differently", it means "supported functionality was lost or became broken". This has not happened here -- your ambiguous bytestring has never had a formally documented contract of correctness, and it was arguably always wrong
|
I'm a bit confused about the supported statement... supported by whom? Python 2.7 supports it according to the official docs (
https://docs.python.org/2/reference/...tring-literals), if you mean supported by Calibre, where would I find the "documented contracts of correctness" of Calibre regarding this case?
From my point of view, calibre "magically" changed my valid Python 2.7 raw string literal to an illegal raw unicode string literal, which breaks my recipe.