Since the ordering of keyword arguments is now guaranteed, the LRU cache doesn't need to sort any longer.

The will give a small change in behavior that I don't care about.  A call f(a=1, b=2) would now be cached separately from f(b=2, a=1).  That won't arise often and isn't really different than the status quo where f(1, b=2) or f(1, 2) are already cached separately.  Overall it is a net win by saving the sorting step on every call.

I think this is a bug and it should be fixed in 3.6. Currenly lru_cache breaks PEP 468 (Preserving Keyword Argument Order).

>>> from functools import lru_cache
>>> @lru_cache()
... def f(**kwargs):
...     return list(kwargs.items())
... 
>>> f(a=1, b=2)
[('a', 1), ('b', 2)]
>>> f(b=2, a=1)
[('a', 1), ('b', 2)]

C implementation should be changed too.

> I think this is a bug and it should be fixed in 3.6.

I concur.  Do you care to whip-up a patch (it is late here).

Here is a patch that fixes also C implementation and has tests.

New changeset 48c750c26710 by Raymond Hettinger in branch '3.6':
Issue #29203:  functools.lru_cache() now respects PEP 468
https://hg.python.org/cpython/rev/48c750c26710

New changeset cc47d385512b by Raymond Hettinger in branch 'default':
Complete the merge for issue #29203
https://hg.python.org/cpython/rev/cc47d385512b