#1236 closed task (fixed)
PEP8 fixes for sugar
| Reported by: | sascha_silbe | Owned by: | sascha_silbe |
|---|---|---|---|
| Priority: | Unspecified by Maintainer | Milestone: | |
| Component: | Sugar | Version: | Git as of bugdate |
| Severity: | Minor | Keywords: | |
| Cc: | Distribution/OS: | Unspecified | |
| Bug Status: | New |
Description
pep8.py has lots of complaints for sugar. We didn't manage to get fixes for them checked in in time for 0.86, so need to do that for 0.88.
Change History (6)
comment:1 Changed 15 years ago by sascha_silbe
- Owner changed from tomeu to sascha_silbe
- Status changed from new to accepted
comment:2 follow-up: ↓ 3 Changed 14 years ago by sascha_silbe
comment:3 in reply to: ↑ 2 Changed 14 years ago by tomeu
Replying to sascha_silbe:
Can we (i.e. I) have a go at this now that 0.86 has been branched off? Do you want to review my changes or should I commit them (one commit per type of change, i.e. number of empty lines between blocks, overlong lines, ...) directly?
Do you see any advantage on doing several commits instead of only one?
I think we should go through the review queue now, then do this cleanup and push it once for all.
comment:4 Changed 14 years ago by tomeu
- Milestone changed from 0.88 to 0.90
comment:5 Changed 13 years ago by sascha_silbe
- Resolution set to fixed
- Status changed from accepted to closed
Note: See
TracTickets for help on using
tickets.
Can we (i.e. I) have a go at this now that 0.86 has been branched off? Do you want to review my changes or should I commit them (one commit per type of change, i.e. number of empty lines between blocks, overlong lines, ...) directly?