On Feb 03, 2010, at 09:55 AM, Guido van Rossum wrote:

On Wed, Feb 3, 2010 at 9:09 AM, Barry Warsaw <barry@python.org> wrote:

...

-----snip snip----- from __future__ import unicode_literals

def func(foo, bar):    print foo, bar

kw = {'foo': 7, 'bar': 9} func(**kw) -----snip snip-----

That will raise a TypeError in 2.6 but works in 2.7.  Is it appropriate and feasible to back port that to Python 2.6?  I remember talking about this a while back but I don't remember what we decided and I can't find a bug on the issue.

I don't know about feasible but I think it's (borderline) appropriate. There are various other paths that lead to this error and it feels to me it's just a long-standing bug that we never took care of until 2.7. However, I don't think it needs to support non-ASCII characters in the keywords (even though 2.7 does seem to support those).

The back port from trunk of r68805 to fix this was really pretty trivial. http://bugs.python.org/issue4978 http://bugs.python.org/file16124/py26-backport.patch Assigned to Benjamin for review. -Barry