Message339088
| Author | Rune Tynan |
|---|---|
| Recipients | Rune Tynan, Windson Yang, docs@python, ezio.melotti, matheus.v.portela, serhiy.storchaka, vstinner |
| Date | 2019-03-29.01:16:42 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1553822202.89.0.559996232688.issue18697@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
I have some interest in making a fix for this. From discussion, I'm thinking that, barring names that already have clear meaning (EG, left/right for things with two parameters): - PyObject* that is unknown type remains `obj` - PyObject* with unicode string is `unicode` - const char*, const Py_UNICODE*, and const wchar* becomes `str` - const char, const Py_UNICODE, and const wchar become `ch` Those seem to be the intersect of most common and most descriptive names already seen. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-03-29 01:16:42 | Rune Tynan | set | recipients: + Rune Tynan, vstinner, ezio.melotti, docs@python, serhiy.storchaka, matheus.v.portela, Windson Yang |
| 2019-03-29 01:16:42 | Rune Tynan | set | messageid: <1553822202.89.0.559996232688.issue18697@roundup.psfhosted.org> |
| 2019-03-29 01:16:42 | Rune Tynan | link | issue18697 messages |
| 2019-03-29 01:16:42 | Rune Tynan | create | |