Sure, I see that. My intent in commenting was merely to point out to others that are learning the craft/language that lambdas generally shouldn't be assigned to names.

EDIT: Poking around the site, I see that there are a lot of code golf type answers around. I guess it's probably not worth being so pedantic around here.

As I should normally agree with you, you seem to forget that main purpose of PEP 8 is to provide some guidance to write cleaner code, not to be an absolute reference when coming to code conventions.

PEP8 introduction states itself that

Many projects have their own coding style guidelines. In the event of any conflicts, such project-specific guides take precedence for that project.

The only moment when you have to follow PEP8 strictly and blindly is when writing an official builtin module for Python distribution itself. Even third party packages listed on PyPi are not confined to PEP8 recommendations.

So please keep in mind that this solution main purpose is code golf - a type of recreational computer programming game where an answer is favoured for its shortness rather than its clearness and designed to be entertaining.
That is also the reason why CodeWars provides two distinct categories to classify solutions:

• Best practices where solutions tend to enforce readibility and performance.
• Clever where solutions are twisted and definitely not designed for production but providing an original approach to resolve a problem.

Assigning a lambda expression to a name is a PEP8 violation, though:

https://www.python.org/dev/peps/pep-0008/#programming-recommendations

Aaaaand coming round the final bend, we have team FP with another tight lambda expression!