Message232199
| Author |
r.david.murray |
| Recipients |
chris.jerdonek, docs@python, eric.araujo, ezio.melotti, flox, georg.brandl, pitrou, python-dev, r.david.murray, rhettinger, serhiy.storchaka, terry.reedy |
| Date |
2014-12-05.16:47:45 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1417798065.38.0.89272709535.issue22581@psf.upfronthosting.co.za> |
| In-reply-to |
|
| Content |
Yeah, just ignore the unicodeobject.c comment comment.
It seems to me that the stuff in the parens is supposed to be a precise description of what the format code handles, with elaboration in the following text. So I'd prefer to just use the :term: in those lists. But like I said I'm not that familiar with the C api, so I'm not sure how much weight my opinion should carry :)
The biggest thing is consistency. If you want to keep all of them in the list, I'd favor the "such as" formulation. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2014-12-05 16:47:45 | r.david.murray | set | recipients:
+ r.david.murray, georg.brandl, rhettinger, terry.reedy, pitrou, ezio.melotti, eric.araujo, flox, chris.jerdonek, docs@python, python-dev, serhiy.storchaka |
| 2014-12-05 16:47:45 | r.david.murray | set | messageid: <1417798065.38.0.89272709535.issue22581@psf.upfronthosting.co.za> |
| 2014-12-05 16:47:45 | r.david.murray | link | issue22581 messages |
| 2014-12-05 16:47:45 | r.david.murray | create | |
|