Timeline for Create output twice the length of the code
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2020 at 9:04 | history | edited | CommunityBot |
Commonmark migration
|
|
| Jul 30, 2019 at 16:09 | comment | added | mbomb007 | @wizzwizz4 I can't figure out how to show you in a comment. Try looking here: meta.stackexchange.com/a/70679/285610 I think it was triple backticks, the code, then a space, then triple backticks, but I can't be certain. Sometimes escaping with backslashes is necessary | |
| Apr 13, 2017 at 14:16 | comment | added | mbomb007 |
You mean print`+.1`?
|
|
| Oct 27, 2015 at 21:32 | comment | added | xnor |
@MartinBüttner Here, changing it to `print`+.1 would compensate for the trailing newline.
|
|
| Oct 27, 2015 at 16:20 | comment | added | Martin Ender | Same comment as for your other answer: doesn't this print a trailing newline, giving 21 bytes of output? | |
| Oct 6, 2015 at 2:01 | comment | added | Anders Kaseorg | @mbomb007 Apparently. GitHub suggests that’s hardly the only thing it’s wrong about. Ideone agrees with CPython. | |
| Oct 5, 2015 at 18:17 | comment | added | mbomb007 | @AndersKaseorg So repl.it is wrong, then? | |
| Oct 3, 2015 at 1:31 | history | edited | xnor | CC BY-SA 3.0 |
added 2 characters in body
|
| Oct 3, 2015 at 1:27 | comment | added | Anders Kaseorg | This no longer works in Python 2.7 or 3.1. | |
| Oct 2, 2015 at 23:35 | history | answered | xnor | CC BY-SA 3.0 |