Ad
  • Default User Avatar

    ok :)
    thanks for the tip !

  • Default User Avatar

    the real question is : who do you play with who couldn't tell you the rules ? :d

  • Default User Avatar

    didn't read the notes, shame on me. While clicking "attempt" I thought "Oh, forgot to take care of 'en passant' !"
    Would be nice to make a new kata with all the rules ;)
    Anyway, good one, tks !

  • Default User Avatar

    tip :
    "and then empty arrays"

  • Default User Avatar

    This comment is hidden because it contains spoiler information about the solution

  • Default User Avatar

    You should add bigger numbers in the tests, at least for python, since the naive approach can pass. Or remove "beware of big numbers" from the description.
    Also, as stated by others, the description is not consistent about the sum asked for.

    Just make things clearer, will be a perfect kata.

  • Default User Avatar

    no, we shouldn't
    thanks for noticing the small attribute :p

  • Default User Avatar

    To my opinion, it is useless. You can hard coding only if you got the answer, and there's no huge chance to just guess it.
    But I hoped you enjoyed coding the random cases :p. Anyway, that's still an added feature, doesn't hurt.
    Thanks to all for helping getting through beta.

  • Default User Avatar

    This comment is hidden because it contains spoiler information about the solution

  • Default User Avatar

    I didn't know the for...else structure, thanks guys !
    In this particular situation, would you agree that the 'else:' can be removed, or do I miss something ?

  • Default User Avatar

    yep it's working
    pity I just wrote a bypass to the flaw while you were uploading the new one ^^

  • Default User Avatar

    Thanks, I've learnt a lot through this kata and discovered a lot more interesting things still to be learnt...

    Be aware that I could "submit final" with incomplete/bad solutions. If it passed some tests, but threw error on the latests like output error (max buffer lenght reached for example) or even an IndexError, it was still considered as valid.
    I don't know if it comes from your particular tests or from a bug in CW python test module.

    edit : appears to be a flaw in CW

  • Default User Avatar

    This comment is hidden because it contains spoiler information about the solution

  • Default User Avatar

    This comment is hidden because it contains spoiler information about the solution

  • Default User Avatar

    Hi,
    There's an issue with the random tests

    Testing for [{'age': 4, 'name': 'Kyoko Hayagawa'}, {'age': 20, 'name': 'Katsutoshi Imai'}, {'age': 3, 'name': 'Taro Koyama'}] and [{'age': 7, 'name': 'Ryoko Morigawa'}, {'age': 18, 'name': 'Shuichi Takasaki'}, {'age': 3, 'name': 'Yuichi Sakakigawa'}, {'age': 1, 'name': 'Ryo Tanaka'}]
    It should work for random tests too: 'Katsutoshi Imai' should equal 'Shuichi Takasaki'

    Well... 20>18. Or did I miss something ?
    And it happened also in various cases (with or without added up ages, for ex. http://pastebin.com/viCwfvjd )