#197 closed task (fixed)
Contributors to the code may be surprised to learn of PEP-8
| Reported by: | Caleb Davis | Owned by: | Will Kahn-Greene |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.2.1 |
| Component: | documentation | Keywords: | |
| Cc: | Parent Tickets: |
Description (last modified by )
I know I was...There are places in redmine mentioning PEP-8 style guidelines (http://www.python.org/dev/peps/pep-0008/), but there is no prominent mention in the contributor docs. This suggestion just came up again in IRC. This issue needs:
- decide where to mention and link to PEP-8
- add it to the contributor documentation
Change History (7)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
| Owner: | set to |
|---|
Chris and I bandied about what should be in a code style guide for a bit now. I'll grab this bug and throw one together soon.
comment:4 by , 15 years ago
| Milestone: | 0.1.0 → 0.2.0 |
|---|
Bumping to 0.1.1. Also this seems super simple. Shouldn't we just do it? ;)
comment:5 by , 15 years ago
| Milestone: | 0.2.0 → 0.2.1 |
|---|
comment:6 by , 14 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → fixed |
| Status: | accepted → closed |
Added a simple note on http://wiki.mediagoblin.org/HackingHowto#So_you_want_to_hack_on_GNU_MediaGoblin.3F
... closing this out!
Note:
See TracTickets
for help on using tickets.
[+ Jim Campbell, Will Kahn-Greene]
I think we need a style guide page on the wiki altogether.
Maybe that belongs on http://wiki.mediagoblin.org/Code_style_guide ?