Summary: | Remove awkward/incorrect pydoc from portage.util.grabdict | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Greg Turner <gmturner007> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | trivial | Keywords: | InVCS |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 409383 | ||
Attachments: | Remove confusing pydoc line |
Description
Greg Turner
2012-03-27 09:27:38 UTC
Created attachment 306827 [details, diff]
Remove confusing pydoc line
This is in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=ae8070542fcee0516fbfa270f6ef3f3e53a8d220 (In reply to comment #0) > By the way, is '@returns' correct? I see a lot of '@returns' in portage > (and a lot of '@return') but pydoc.py doesn't say anything about > 'returns'...? It should be '@return'. (In reply to comment #2) > (In reply to comment #0) > > By the way, is '@returns' correct? I see a lot of '@returns' in portage > > (and a lot of '@return') but pydoc.py doesn't say anything about > > 'returns'...? > > It should be '@return'. Fixed now: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=b2147b15e11b3d30d646098696ef69d749aeb5b2 This is fixed in 2.1.10.52 and 2.2.0_alpha96. |