Timeline for equalprg to use for Python
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 10, 2015 at 15:35 | vote | accept | Khelben | ||
| Feb 8, 2015 at 5:41 | comment | added | Martin Tournoij | ... exceptions to PEP8 are sometimes required... Using an automated tool to "fix" the code style can't do these exceptions, and is a flawed concept ... If you want PEP8-compliant code, then type PEP8 compliant code, and when it makes sense, make an exception. | |
| Feb 8, 2015 at 5:39 | comment | added | Martin Tournoij | PEP8 says: "But most importantly: know when to be inconsistent -- sometimes the style guide just doesn't apply. [...] Some other good reasons to ignore a particular guideline: 1. When applying the guideline would make the code less readable, even for someone who is used to reading code that follows this PEP. [...]" ... PEP8 are guidelines only. The universe is complex. Code is complex. You can't make rules for every possible scenario, so this is why PEP8 are guidelines, and not rules. The whole point of Python is readability, and especially because of that ... | |
| Feb 8, 2015 at 5:15 | history | edited | 200_success | CC BY-SA 3.0 |
edited body; edited tags
|
| Feb 8, 2015 at 0:30 | answer | added | Jay Thompson | timeline score: 3 | |
| Feb 7, 2015 at 14:08 | history | edited | Martin Tournoij |
edited tags
|
|
| Feb 7, 2015 at 12:12 | history | asked | Khelben | CC BY-SA 3.0 |