Message292558
| Author | martin.panter |
|---|---|
| Recipients | Arfrever, benjamin.peterson, docs@python, martin.panter, r.david.murray, rhettinger, serhiy.storchaka, vstinner, xiang.zhang, zbysz |
| Date | 2017-04-29.03:07:46 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1493435267.17.0.911335605178.issue21071@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I don’t think the API should be expanded to accept arbitrary bytes-like objects as format strings. Struct formats are strings of ASCII-compatible characters, but not arbitrary chunks of memory. I think the main question is whether it is okay to break compatibility (Victor’s pull request, or my format-str.patch), or whether there has to be a backwards-compatible deprecation of the existing bytes attribute. FWIW I am okay with breaking compatibility, since the main documentation already implies it should be a text string. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017-04-29 03:07:47 | martin.panter | set | recipients: + martin.panter, rhettinger, vstinner, benjamin.peterson, Arfrever, r.david.murray, zbysz, docs@python, serhiy.storchaka, xiang.zhang |
| 2017-04-29 03:07:47 | martin.panter | set | messageid: <1493435267.17.0.911335605178.issue21071@psf.upfronthosting.co.za> |
| 2017-04-29 03:07:47 | martin.panter | link | issue21071 messages |
| 2017-04-29 03:07:46 | martin.panter | create | |