Message126421
| Author | lavajoe |
|---|---|
| Recipients | belopolsky, docs@python, georg.brandl, lavajoe, r.david.murray |
| Date | 2011-01-17.18:01:06 |
| SpamBayes Score | 1.4446062e-09 |
| Marked as misclassified | No |
| Message-id | <1295287272.57.0.518096435974.issue10921@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> I assume this means it raises a KeyError when given a bytes object as an argument. Yes, a KeyError is raised when arg is bytes, but passing a string also fails (raising TypeError). The latter might also be a separate bug, in that strings cannot be passed as they could be in Python 2. > This looks like a 2 to 3 port oversight and we can probably fix it in RC. Probably, since many strings have been changed to bytes elsewhere in the file. BTW, I just attached a patch for Python 2.7 that fixes the subset of non-py3k-related issues. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-01-17 18:01:12 | lavajoe | set | recipients: + lavajoe, georg.brandl, belopolsky, r.david.murray, docs@python |
| 2011-01-17 18:01:12 | lavajoe | set | messageid: <1295287272.57.0.518096435974.issue10921@psf.upfronthosting.co.za> |
| 2011-01-17 18:01:06 | lavajoe | link | issue10921 messages |
| 2011-01-17 18:01:06 | lavajoe | create | |