Oh. Of course.

oh. the print

Woah. First time realizing you can 2D slice if you use np.

I'm learning a lot here in Codewars.

you could simplify it a bit (pun intended) by avoiding the != 0 in gray2bin

Oh I should have thought of this.
My inner math teacher is screaming.
Well played.

Merged! :)

Nice! Thanks a lot :)

Just merged them.

Maybe the admin can push it up to 6kyu then.
I would indeed prefer that the rank properly matched the perceived difficulty.

Thanks for stepping in and managing the discrepancy!
We'll see what the admin decides.

Is there a way I can bump it up to 6 though? Or is it some admin thing?

I think, ejini, you're being hostile for no reason.
I chose my guessed rank way before knowing anything about that competition, based solely on my experience solving 7kyu and 6kyu recently. I have no idea about how the final rank was assigned, neither about weateher this kata has ended up on the suggested competition or not. And also it seems almost half of the people that made it thought it was indeed 7kyu.

If anyone with power to change the final rank thinks it should be changed, feel free to do it. I for one can't even see the complete list of perceived difficulty votes.

Hey! I didn't even know that was a thing.

Yes I'd love to enter that challenge! Do I need to do anything from my side?
Also, do we need to wait for the kata to be approved? It's still in Beta now.

I've added now the input on the message= argument of the test assertion.

Woah, you're right. My own example solution wasn't even accounting for thin but with a seagull, even if the kata description explicitly asked for it.

I've added now fixed and randomised tests for that, and fixed my own solution.
I guess it may break some of the solutions by other people too, if they too didn't account for it. Not sure how codewars handles that.

Thanks a lot!
It's my first time writing one, just got authoring permission :)