i'm feeling like some retarded, lmao :D

Use of deconstruct for spliting world
Use of backticks for join
Use of sort rather than reverse
Writing of a basic test

yup. although i did the same thing

sigh

Golfing on the variable name
Use of count method
Use of an direct return
Condition without if/else

The return True is not neccessary.

The problem is simple, maybe add random tests

This is correct according to PEP 8 styling for python code but in terms of 1 liners, hardly most of them follow this structure. I guess it's all based on preference.

According to PEP 8 – Style Guide for Python Code

Imports are always put at the top of the file, just after any module comments and docstrings, and before module globals and constants

Additionally,

Compound statements (multiple statements on the same line) are generally discouraged:

Correct:

if foo == 'blah':
    do_blah_thing()
do_one()
do_two()
do_three()

Rather not:

# Wrong:
if foo == 'blah': do_blah_thing()
do_one(); do_two(); do_three()

I don't think it matters if you use an import outside or inside since the code is still one line right?

Yup, I tried to prioritize performance and lines of code. But you are right, this solution would not be suitable for work environments.

Yo, this looks clever, but it's very difficult to understand to a third party or yourself at a future date. I'd prioritize readability more.

Me, trying to be popular on Codewars comment section: "This should be disallowed, it's almost cheating! Plus you didn't really learn anything from this kata!! Python is for noobs!!!"

Also me, to myself: hehe this is brilliant, I wish I thought of this, I love Python

Hello,

I don't know if it´s intended, but a function wrote in one single line is extremely difficult to read and understand what it is doing, mainly because of all the if-elses.

Cool quotes