Please use new python test framework.

Hello, my script is ok for the first tests but not with big numbers By exemple,6590815232 no (but it's a number proposed in the test) but with this number -1, so 6590815231. It's ok. I can't understand where is the problem.

Error messages have been fixed. (2)

Error messages have been fixed. (1)

Thanks to @rowcased this ought to be fixed now. To my understanding your code was indeed wrong, but the wrong error message was used.

Maybe they're used to figuring things out x)

Wow! I'm a bit surprised these wonky error messages made it through 1,734 completions! Thanks for the notice. Should be good now.

Thanks, @natan I'm looking at it now.

Hm. I created an issue for the C translation. Maybe I should have posted HERE instead. Well, here's a notification for you @rowcased

C translation: Error messages don't make sense.

#include <stdbool.h> #include <math.h> bool is_square(int n) { return false; }

^^^ responds with 13368 is not a square number but 13368 wasn't the input or

13368 is not a square number

13368

#include <stdbool.h> #include <math.h> bool is_square(int n) { return true; }

^^^ gives 370081406 is a square number (19238 * 19238) .. no. it is not.

370081406 is a square number (19238 * 19238)

it's keep showing this error (188609022 is a square number (13734 * 13734)) meanwhile sqrt(188609022)=13733.5 which means 188609022 isn't a square

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

Neither number = number nor numbers = number preserve the input list, print it before returning and you'll see it's been mutated.

number = number

numbers = number

Please use new python test framework.

Please use new python test framework.

Hello, my script is ok for the first tests but not with big numbers By exemple,6590815232 no (but it's a number proposed in the test) but with this number -1, so 6590815231. It's ok. I can't understand where is the problem.

Error messages have been fixed. (2)

Error messages have been fixed. (1)

Thanks to @rowcased this ought to be fixed now.

To my understanding your code was indeed wrong, but the wrong error message was used.

Maybe they're used to figuring things out x)

Wow! I'm a bit surprised these wonky error messages made it through 1,734 completions! Thanks for the notice. Should be good now.

Thanks, @natan I'm looking at it now.

Hm. I created an issue for the C translation. Maybe I should have posted HERE instead. Well, here's a notification for you @rowcased

C translation: Error messages don't make sense.

## Click me for details

^^^ responds with

`13368 is not a square number`

but`13368`

wasn't the inputor

^^^ gives

`370081406 is a square number (19238 * 19238)`

.. no. it is not.it's keep showing this error (188609022 is a square number (13734 * 13734))

meanwhile sqrt(188609022)=13733.5 which means 188609022 isn't a square

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

Neither

`number = number`

nor`numbers = number`

preserve the input list, print it before returning and you'll see it's been mutated.## Loading more items...