This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | rhettinger |
|---|---|
| Recipients | belopolsky, rhettinger |
| Date | 2008年03月24日.08:53:20 |
| SpamBayes Score | 0.058314543 |
| Marked as misclassified | No |
| Message-id | <1206348800.91.0.18759646695.issue2172@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I'm not sure the class docstring approach is suitable for a mixin. It seems fine to me that pydoc strips the commentary on the mixin as a standalone class; instead it appropriately focuses on the client class that uses the mixin as part of its API. FWIW, all of this code goes away in Py3.0. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年03月24日 08:53:21 | rhettinger | set | spambayes_score: 0.0583145 -> 0.058314543 recipients: + rhettinger, belopolsky |
| 2008年03月24日 08:53:20 | rhettinger | set | spambayes_score: 0.0583145 -> 0.0583145 messageid: <1206348800.91.0.18759646695.issue2172@psf.upfronthosting.co.za> |
| 2008年03月24日 08:53:20 | rhettinger | link | issue2172 messages |
| 2008年03月24日 08:53:20 | rhettinger | create | |