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 | petdance |
|---|---|
| Recipients | corona10, nascheme, petdance, serhiy.storchaka, shihai1991, steve.dower, vstinner |
| Date | 2020年02月15日.21:34:35 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1581802475.94.0.893629627194.issue39573@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
@vstinner would it be helpful if I went on a sweep looking for places we can use the new Py_IS_TYPE macro? Getting away from Py_TYPE(op) would also mean a move to making the internals const-correct. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2020年02月15日 21:34:35 | petdance | set | recipients: + petdance, nascheme, vstinner, serhiy.storchaka, steve.dower, corona10, shihai1991 |
| 2020年02月15日 21:34:35 | petdance | set | messageid: <1581802475.94.0.893629627194.issue39573@roundup.psfhosted.org> |
| 2020年02月15日 21:34:35 | petdance | link | issue39573 messages |
| 2020年02月15日 21:34:35 | petdance | create | |