Timeline for Full Width Text
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2020 at 9:04 | history | edited | Community Bot |
Commonmark migration
|
|
| Dec 17, 2017 at 17:47 | history | edited | Riker | CC BY-SA 3.0 |
added 38 characters in body
|
| Mar 24, 2016 at 12:32 | comment | added | Yytsi | @manatwork Very good point! Reverted it. Back to 39 bytes :D | |
| Mar 24, 2016 at 12:30 | history | edited | Yytsi | CC BY-SA 3.0 |
deleted 22 characters in body
|
| Mar 24, 2016 at 12:17 | comment | added | manatwork | Just improve it more. ;) In meantime I would revert to the previous version – it demonstrates the usage of a very popular Python feature, which has better chances for positive votes than a duplicate. | |
| Mar 24, 2016 at 11:37 | comment | added | Yytsi | @manatwork I see. Should I change my old answer back or something? Thanks for telling! | |
| Mar 24, 2016 at 10:34 | comment | added | manatwork | This is now exact duplicate of Raffi's answer, which reached this format 1 day 01:30:09 hour earlier. | |
| Mar 24, 2016 at 5:00 | history | edited | Yytsi | CC BY-SA 3.0 |
added 22 characters in body
|
| Mar 23, 2016 at 16:15 | comment | added | wnnmaw |
You could just join with a " " rather than insert it with the comprehension. Then all you need to worry about is the trailing space at the end. print(" ".join(input())+" ") gets you down to 28 bytes
|
|
| Mar 22, 2016 at 20:36 | review | Low quality posts | |||
| Mar 22, 2016 at 20:38 | |||||
| Mar 22, 2016 at 20:35 | history | edited | mbomb007 | CC BY-SA 3.0 |
edited body
|
| Mar 22, 2016 at 19:44 | review | Low quality posts | |||
| Mar 22, 2016 at 20:26 | |||||
| Mar 22, 2016 at 19:28 | history | answered | Yytsi | CC BY-SA 3.0 |