The en-dash (–) caused a UnicodeDecodeError for me. It should not since the # *-* coding comment is set at the top of the file but it still did for me while recording a terminal session with asciinema.
As far as I can see (grepping [^\x00-\x7F]) this is the only instance of a non-ascii char in the source.
Coverage remained the same at 83.502% when pulling 54d2edd805ff60c3c836c8211dbe894809985a94 on kba:non-unicode-source-char into 8a8263e02d4b2bb95de4835e8d49fc70fd964f97 on LibraryOfCongress:master.
Coverage remained the same at 83.502% when pulling 54d2edd805ff60c3c836c8211dbe894809985a94 on kba:non-unicode-source-char into 8a8263e02d4b2bb95de4835e8d49fc70fd964f97 on LibraryOfCongress:master.
Coverage remained the same at 83.502% when pulling 54d2edd805ff60c3c836c8211dbe894809985a94 on kba:non-unicode-source-char into 8a8263e02d4b2bb95de4835e8d49fc70fd964f97 on LibraryOfCongress:master.
The en-dash (
–
) caused aUnicodeDecodeError
for me. It should not since the# *-* coding
comment is set at the top of the file but it still did for me while recording a terminal session withasciinema
.As far as I can see (grepping
[^\x00-\x7F]
) this is the only instance of a non-ascii char in the source.