Timeline for Python code style - blank lines in long list
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 27, 2013 at 23:11 | review | First posts | |||
| Mar 27, 2013 at 23:18 | |||||
| Mar 24, 2013 at 1:36 | vote | accept | Chris Krycho | ||
| Mar 22, 2013 at 19:09 | comment | added | Chris Krycho | A reasonable question. My thought was simply that "easier to read" has some things that are constant, but some things that vary by convention in the community. What's easier to read for a Java gal isn't necessarily the same as what's easier to read for a Python guy isn't necessarily the same as what's easier to read for a Lisp gal. Conventions aren't hard rules, but they're worth at least being aware of. | |
| Mar 22, 2013 at 19:04 | comment | added | Izkata | If it makes the code easier to understand, who cares about "pythonic"? | |
| Mar 22, 2013 at 18:45 | answer | added | Jerrad Genson | timeline score: 3 | |
| Mar 22, 2013 at 18:25 | history | edited | Chris Krycho | CC BY-SA 3.0 |
Add clarifying note.
|
| Mar 22, 2013 at 14:18 | answer | added | Demian Brecht | timeline score: 1 | |
| Mar 22, 2013 at 14:05 | history | asked | Chris Krycho | CC BY-SA 3.0 |