7 kyu
After(?) Midnight
545 of 1,188Aquila
Loading description...
Date Time
Algorithms
View
This comment has been reported as {{ abuseKindText }}.
Show
This comment has been hidden. You can view it now .
This comment can not be viewed.
- |
- Reply
- Edit
- View Solution
- Expand 1 Reply Expand {{ comments?.length }} replies
- Collapse
- Spoiler
- Remove
- Remove comment & replies
- Report
{{ fetchSolutionsError }}
-
-
Your rendered github-flavored markdown will appear here.
-
Label this discussion...
-
No Label
Keep the comment unlabeled if none of the below applies.
-
Issue
Use the issue label when reporting problems with the kata.
Be sure to explain the problem clearly and include the steps to reproduce. -
Suggestion
Use the suggestion label if you have feedback on how this kata can be improved.
-
Question
Use the question label if you have questions and/or need help solving the kata.
Don't forget to mention the language you're using, and mark as having spoiler if you include your solution.
-
No Label
- Cancel
Commenting is not allowed on this discussion
You cannot view this solution
There is no solution to show
Please sign in or sign up to leave a comment.
got an unexpected exception raised while it runs on my computer version of python3.11
JS: move to Node v18
Approved
Python 3.11 + language agnostic description
Approved
Ruby 3.0 + language agnostic description
Approved
Ruby 3.0 should be enabled.
Hi, I just added a Go translation.
Python 3 should be enabled.
Fixed in this kumite, awaiting for approval
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
This comment has been hidden.
Had the same issue. Had to wrap it in a try/except block specifically for the random tests to strip off the first "datetime". I have no idea why the random tests are doing that, but this seems like it's an issue with the way the tests are written.
This is indeed caused by the way the tests are written. The random tests use "from datetime import datetime". So if you use "import datetime" in your code, when the random tests run, "datetime" is changed to mean not the datetime module, but the datetime.datetime class. So "datetime.datetime" is interpreted as "the datetime attribute on the datetime.datetime class" (which does not exist).
This can be avoided by either using "from datetime import datetime" in your own code or by using an alias (e.g., "import datetime as datemodule").
I've kumited a "fix".
Python as well as Ruby translation has been submitted; this one forced to learn a few new things in said languages, thanks!
My pleasure I'm glad you liked it, and thanks a lot! I've accepted the translations. :-)