Message71846
Since this is marked "release blocker", I'll provide a shallow comment:
I don't think it should be a release blocker. It's a bug in the compile
function, and there are various work-arounds (such as saving the bytes
to a temporary file and executing that one, or decoding the byte string
to a Unicode string, and then compiling the Unicode string). It is
sufficient to fix it in 3.0.1.
I don't think the patch is right: as the test had to be changed, it
means that somewhere, the detection of the encoding declaration now
fails. This is clearly a new bug, but I don't have the time to analyse
the cause further.
In principle, there is nothing wrong with the tokenizer treating latin-1
as "raw" - that only means we don't go through a codec. |
|
Date |
User |
Action |
Args |
2008-08-24 17:57:04 | loewis | set | recipients:
+ loewis, brett.cannon, benjamin.peterson |
2008-08-24 17:57:04 | loewis | set | messageid: <1219600624.65.0.619297673716.issue3574@psf.upfronthosting.co.za> |
2008-08-24 17:57:03 | loewis | link | issue3574 messages |
2008-08-24 17:57:02 | loewis | create | |
|