Message232197
| Author |
serhiy.storchaka |
| 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:25:02 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1417796702.95.0.131301349919.issue22581@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Thank you David.
I have left enumerations of concrete bytes-like classes (bytes and bytearray) because I thought that it is good to be more verbose in the documentation. I left the decision how write it to you: ":class:`bytes`, :class:`bytearray` or :term:`bytes-like object`", ":term:`bytes-like object` such as :class:`bytes` and :class:`bytearray`", or just ":term:`bytes-like object`".
I don't understand your comment about unicodeobject.c. This change doesn't differ from others. May be you mean unicodeobject.h? Yes, "char buffer" is Python 2 term and doesn't make sense in 3.x. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2014年12月05日 16:25:03 | serhiy.storchaka | set | recipients:
+ serhiy.storchaka, georg.brandl, rhettinger, terry.reedy, pitrou, ezio.melotti, eric.araujo, r.david.murray, flox, chris.jerdonek, docs@python, python-dev |
| 2014年12月05日 16:25:02 | serhiy.storchaka | set | messageid: <1417796702.95.0.131301349919.issue22581@psf.upfronthosting.co.za> |
| 2014年12月05日 16:25:02 | serhiy.storchaka | link | issue22581 messages |
| 2014年12月05日 16:25:02 | serhiy.storchaka | create |
|