I had posted this as a separate suggestion and then realized it was basically the same as this one:

"I'd really like to have the solutions section display the duration that each solution took to execute. I've had to rewrite code a couple times because codewars said it took too long to execute, so it seems to be tracking time.

I'm very new to coding in general and have only been working my way through Python so far, but I learn a ton by looking at other people's solutions. I've also learned that I can't always trust what is marked as "best practice" or "clever" to actually be GOOD.

I can determine readability on my own and I think that's a pretty subjective thing. I sometimes go run other people's solutions to see how they work and how efficient they seem. As far as I can tell, readability and efficiency are the two most important things when differentiating valid solutions to a problem. A display of how much time a solution took to execute (or some other metric for efficiency if something else is better) would help me learn a lot."

Voile, in seeing your answers I still think that a runtime display would be really helpful. Memory usage would be neat as well. Maybe I don't understand what a code length metric would mean, but can't we visibly see how long the code is? You mention difficulty of benchmarking random tests, but couldn't you just display runtime metrics for whatever the set tests happen to be?

There is no difference between "in dictionary order" and "alphabetic order", I think ;-)
About the code, I can't give you more help, unless you give more information about fails, or paste your code below(Mark as having spoiler content)

Changed < to <=, Thanks for your feedback ;-)

The part of the description that says "unique letters (2 < length <= 26)" should be changed to "unique letters (2 <= length <= 26)" because the random tests include strings with 2 letters. This was a really cool kata that forced me to learn more about permutations, though, thanks!

Java version is impossible to complete:

expected:<13.33333[3333333334] is above freezing t...> but was:...

Thank you for the responses. I've been learning Pythin 3.x so I hadn't run into this before. I guess I'll need to pay more attention to which version of python the kata is available in.

Not an issue

Could someone break this down for me? I'm pretty new to python (and coding in general) and don't know what the re module does.