Python translation

🐍

Please review and approve. (Kata creator inactive)

Fixed, thanks.

congrats: your update uses language specific syntax, meaning it's incorrect for the JS version

The description was updated to match the original test suite and solutions (which used fixed tags).

As you felt it was an issue, the description was updated to note that the tags are fixed, if you want to rewrite the kata completely to make it a random tag generator / replacement then go ahead.

In this case, having random tasks isn't an issue because it is a kata choice to either use a set of fixed tags (in a random string) or a set of random tags in a random string.

Bullshit again. Try to do some hard kata and just look at what users do when there aren't random tests. Then you'll understand why random tests are needed.

Then, in the name of what you call "kata best practices" (and that you don't generally apply to your doings), you have to extend the notion to any level of katas. To show the good practices, and to avoid tempting people with that kind of "cheats".

As noted, it was a suggestion not an issue as I didn't think it was mandatory for reasons I have noted elsewhere. To repeat, in short I don't flag things as issues which are opinion based.

In this case, having random tasks isn't an issue because it is a kata choice to either use a set of fixed tags (in a random string) or a set of random tags in a random string.

Every solution assumed the former, and it allows very different solutions (as you don't have to pattern match). If you go with the latter you break (almost?) every solution.

If you don't feel it is a suggestion and they are actual issues to the point they break the kata - well just note them as you have and then fix them as you want.

If the author wasn't responsive in a week or so I planned to update the description to match the current solutions as that is how everyone interpreted it, and it was only a white kata.

I see this has been fixed - thank you!

Related issue across the descriptions:

• The JavaScript description has no example message at the end. The final sentence is "You should return this string:", but then no string is displayed. Screenshot.
• The Ruby description has the example message twice. Screenshot.

• description needs to be updated (see below)
• no random test (at all...)

@cliffstamp: you're the most counterproductive approver here, man. And yes, this is supposed to be an issue and not a suggestion, so that the edit panel stays accessible to PUs if needed.

This was either updated, or the issue wasn't one as it is clear now.

Not an issue.

Very similar kata https://www.codewars.com/kata/56ae72854d005c7447000023

JS description isn't full