This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients Ringding, belopolsky, dangra, ezio.melotti, lemburg, pitrou, serhiy.storchaka, sjmachin, spatz123, vstinner
Date 2012-05-17.18:52:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1337280930.2462.113.camel@raxxla>
In-reply-to <>
> Changing from 'unexpected end of data' to 'invalid continuation byte' for b'\xe0\x00' is fine with me, but this will be a (minor) deviation from 2.7, 3.1, 3.2, and pypy (it could still be changed on all these except 3.1 though).

I probably poorly said. Past and current implementations raise
'unexpected end of data' and not 'invalid continuation byte'. Test
expects 'invalid continuation byte'.
Date User Action Args
2012-05-17 18:52:51serhiy.storchakasetrecipients: + serhiy.storchaka, lemburg, sjmachin, belopolsky, pitrou, vstinner, ezio.melotti, Ringding, dangra, spatz123
2012-05-17 18:52:51serhiy.storchakalinkissue8271 messages
2012-05-17 18:52:50serhiy.storchakacreate