Ad
  • Custom User Avatar

    Already raised as issue

  • Custom User Avatar

    Python 2 is no longer supported.

  • Custom User Avatar

    Wouldn't it be better to accept any iterable like range or tuple?, for me they are good options too

  • Default User Avatar

    Please note a language when reporting issues. This works fine in Ruby for example.

  • Default User Avatar

    This was added (maybe by you) to the list of affected kata: https://github.com/Codewars/codewars.com/wiki/List-of-Affected-Kata.

  • Default User Avatar

    Well, at least I got different error messages as you can see, so I thought there should have been something changed. I tried refreshing but it didn't work.

    I just try again, everything works fine now. (more preciously, works well with py2, and well with py3 only after change the range(...) to list(range(...))) :D

  • Default User Avatar

    Fixed just now.

  • Default User Avatar

    I can't get the alpha even run print alpha for sample tests.
    Should be caused by changement of CW..

  • Default User Avatar

    That line (the one you've copied and pasted) should read assert_not_eq([3, 1000], random_ints). I'm not exactly sure why it hasn't updated for you, because it works for me. Can you try refreshing the page?

  • Default User Avatar

    No, it's not fixed yet.
    Now I get this when running sample tests:

     STDERR
    Traceback (most recent call last):
      File "main.py", line 14, in <module>
        assert_not_eq([3, 1000])
    TypeError: assert_not_eq() takes at least 2 arguments (1 given)
    
  • Default User Avatar

    Ah yes, sorry about that; it's fixed now.

  • Default User Avatar

    I know that my code is not complete and may have errors. I just wonder why it can pass the kata with error raised. I thought it should raise errors which tell me what to modify while I got a sudden pass..

    Since I've not seen such bizarrerie before and I haven't try to create a kata, I don't know if it can be caused by the system or by the testing code. I just want to remind you to check if there's a bug in the testing code. ;)

  • Custom User Avatar

    Do you see, that you actually have an Error?

    IndexError: tuple index out of range

    Ii seams you are using a O(n) time complexity algorithm. It will not pass. I dont know why the Test suite is giving you a "You have passed all of the tests! :)" message. It is indeed irritating. Probably its a bug in the suite itself. But it does not changes the relation to your solution, which is not passing. In general: Error messages are bad signs when you submit a Solution.;)

  • Default User Avatar

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

  • Default User Avatar

    Could you please paste your code here and mark it as a spoiler?

  • Loading more items...