@divy9t: here is why it's not an issue (this is a terminology trouble):
(generic message)
Seems you're "rather new" to cw, so here are some general guidelines about the comments:
Issue: problem in the kata itself (description, wrong tests, wrong internal solution...)
Suggestions: well, I guess that part is clear
Question anything else that is related to you having a problem solving a kata -> that's you, currently.
When you post issues:
provide ALL the useful information:
language
input
outputs (actual expected) when relevant
error message when relevant
check, DOUBLE check that this IS an issue, meaning that the problem is in the kata itself and not in your code. If it's in your code, post rather a question
if you pass this step, you still have to prove/explain what the issue is (and if you can provide fixes, it's even better)
When you post a question: well, most of the above apply too x)
EDIT: actually, it's even simpler. As stated by FArekkusu, you're currently just ignoring one of the requirements, so... not surprizing your solution isn't passing:
just so you know and that python completion is irrelevant
LOL! So I guess those thousands of people just got lucky ¯\(ツ)/¯
I'm not sure what you're implying here... Are you saying that those logs you see are fake? Do you think CW code runner interprets python code differently than on your machines? How can you explain your code returning floating point numbers, when only integers are accepted? Spoiler: there's no magic here, what you see is what you're getting.
You're welcome to post your code here (mark it as spoiler) so we can pinpoint the problem in your code, but please stop with this attitude where you know better than everyone. The issue is very clear - your code contains some error, but you're welcome to prove otherwise.
Seems like you didn't read what I said, when I said i ran the test on different machines, I did verified the output and it was same as the one that was displayed and I didn't mention python 2, just so you know and that python completion is irrelevant.
You returned 0.25, expected is 0, because "Divison should be integer division". It's that simple.
It doesn't matter if you tested 100 machines running python 2 or whatnot, python3 uses different operator for integer division, and you can see it in the logs.
How can you say it isn't an issue, when I am facing it and I already tried it on multiple machines I am getting the desired output, I can show you the screenshot.
yes devided by as int a//b is going through.. strange
This comment is hidden because it contains spoiler information about the solution
okay, thanks.
@divy9t: here is why it's not an issue (this is a terminology trouble):
(generic message)
Seems you're "rather new" to cw, so here are some general guidelines about the comments:
Issue
: problem in the kata itself (description, wrong tests, wrong internal solution...)Suggestions
: well, I guess that part is clearQuestion
anything else that is related to you having a problem solving a kata -> that's you, currently.When you post issues:
When you post a question: well, most of the above apply too x)
When you post code, use proper github markdown, so that it's readable.
cheers
EDIT: actually, it's even simpler. As stated by FArekkusu, you're currently just ignoring one of the requirements, so... not surprizing your solution isn't passing:
LOL! So I guess those thousands of people just got lucky ¯\(ツ)/¯
I'm not sure what you're implying here... Are you saying that those logs you see are fake? Do you think CW code runner interprets python code differently than on your machines? How can you explain your code returning floating point numbers, when only integers are accepted? Spoiler: there's no magic here, what you see is what you're getting.
You're welcome to post your code here (mark it as spoiler) so we can pinpoint the problem in your code, but please stop with this attitude where you know better than everyone. The issue is very clear - your code contains some error, but you're welcome to prove otherwise.
Seems like you didn't read what I said, when I said i ran the test on different machines, I did verified the output and it was same as the one that was displayed and I didn't mention python 2, just so you know and that python completion is irrelevant.
Did you even read the output you posted?
You returned 0.25, expected is 0, because "Divison should be integer division". It's that simple.
It doesn't matter if you tested 100 machines running python 2 or whatnot, python3 uses different operator for integer division, and you can see it in the logs.
By the way, Python Completions: 6282.
How can you say it isn't an issue, when I am facing it and I already tried it on multiple machines I am getting the desired output, I can show you the screenshot.
Not an issue.
This comment is hidden because it contains spoiler information about the solution
Facing the same issue