Message83240
Why I considered the existing translation incorrect was because it
translates something which was a tuple of types in Python 2.x into a
type of Python 3.x. I fail to see how this can be useful. (A check like
"x in types.StringTypes" gets translated into "x in str", which will
always fail.)
I agree that translating into "(str, bytes)" won't always be correct,
but it seems to have a much better chance of being correct than the
existing translation into "str". Otherwise it should at least be "(str,)". |
|
Date |
User |
Action |
Args |
2009-03-06 06:59:51 | hagen | set | recipients:
+ hagen, loewis, benjamin.peterson |
2009-03-06 06:59:51 | hagen | set | messageid: <1236322791.46.0.229361565578.issue5425@psf.upfronthosting.co.za> |
2009-03-06 06:59:49 | hagen | link | issue5425 messages |
2009-03-06 06:59:48 | hagen | create | |
|