Georg Brandl ge...@python.org added the comment:
I think the canonical message is expected X, not Y. Otherwise, fine to
commit.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11032
___
Changes by Georg Brandl ge...@python.org:
--
assignee: georg.brandl - haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11032
___
___
Eric Smith e...@trueblade.com added the comment:
It looks like the canonical message is expected X, got Y. With that change
I've checked it in in r88226. I'll backport.
--
assignee: haypo - eric.smith
___
Python tracker rep...@bugs.python.org
Eric Smith e...@trueblade.com added the comment:
Actually this error doesn't exist on older versions because these used to be
methods on a string. The error was introduced in r85456 (issue 9418) when these
became functions in the _string module.
No need to backport.
--
resolution: -
Eric Smith e...@trueblade.com added the comment:
Release manager: You can decide if this fix should go in before 3.2. It's a
trivial fix to a crasher, but it's extremely unlikely anyone would trip over
it. It's been a crasher since 3.0.
It's also a crasher in 2.7, although there it's in the
Benjamin Peterson benja...@python.org added the comment:
2011/1/28 Eric Smith rep...@bugs.python.org:
Eric Smith e...@trueblade.com added the comment:
Release manager: You can decide if this fix should go in before 3.2. It's a
trivial fix to a crasher, but it's extremely unlikely anyone
