Talk:Convert seconds to compound duration: Difference between revisions
(→Task is ready for accepting solutions!: Promotion from draft.) |
(→About the python examples: new section) |
||
| Line 5: | Line 5: | ||
:Hi, the usual process is to wait for at least four different language implementations from four people and no unanswered questions on the talk page before promotion from draft to full task status. This helps the task to mature without too many people doing implementations if problems are found. |
:Hi, the usual process is to wait for at least four different language implementations from four people and no unanswered questions on the talk page before promotion from draft to full task status. This helps the task to mature without too many people doing implementations if problems are found. |
||
:I enjoyed doing the Python example and found the task description gave me the info I needed. Thanks. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 03:41, 7 June 2015 (UTC) |
:I enjoyed doing the Python example and found the task description gave me the info I needed. Thanks. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 03:41, 7 June 2015 (UTC) |
||
== About the python examples == |
|||
The first python example doesn't run, because of undefined <code>t</code>. The second one runs, but if fed 0 seconds as input, it gives a blank in return, which is probably not ideal. Other may do the same thing, but I haven't checked. |
|||
Another issue: is it really necessary to post code in the interactive prompt format? It makes testing the code unpleasant because of the ">>>" prompt, and the mixed tab/space indentations looks like crap in my text editor. It may be useful to show users how to use the interactive shell, but since majority of coding is not going to be done in this fashion, having half of the python examples on RC so presented is overdoing it. --[[User:Ledrug|Ledrug]] ([[User talk:Ledrug|talk]]) 04:40, 7 June 2015 (UTC) |
|||
Revision as of 04:40, 7 June 2015
Task is ready for accepting solutions!
I've created it as a draft task for now as a formality, but I consider the task description finished - unless of course there is feedback demanding changes. So code away, and say if anything is unclear! --Smls (talk) 21:56, 6 June 2015 (UTC)
- Hi, the usual process is to wait for at least four different language implementations from four people and no unanswered questions on the talk page before promotion from draft to full task status. This helps the task to mature without too many people doing implementations if problems are found.
- I enjoyed doing the Python example and found the task description gave me the info I needed. Thanks. --Paddy3118 (talk) 03:41, 7 June 2015 (UTC)
About the python examples
The first python example doesn't run, because of undefined t. The second one runs, but if fed 0 seconds as input, it gives a blank in return, which is probably not ideal. Other may do the same thing, but I haven't checked.
Another issue: is it really necessary to post code in the interactive prompt format? It makes testing the code unpleasant because of the ">>>" prompt, and the mixed tab/space indentations looks like crap in my text editor. It may be useful to show users how to use the interactive shell, but since majority of coding is not going to be done in this fashion, having half of the python examples on RC so presented is overdoing it. --Ledrug (talk) 04:40, 7 June 2015 (UTC)