Message330676
| Author | vstinner |
|---|---|
| Recipients | ZackerySpytz, serhiy.storchaka, vstinner |
| Date | 2018-11-29.10:57:54 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1543489074.99.0.788709270274.issue35337@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> This is compatibility breaking change. Right. The question is if you are ok with it :-) > Currently you can get the address of the array of tuple items by using &PyTuple_GET_ITEM(obj, 0). I don't get your point. I know that you access directly obj->ob_item to use directly the C array rather than PyTuple_GET_ITEM/PyTuple_SET_ITEM, but the issue is about making PyTuple_GET_ITEM/PyTuple_SET_ITEM stricter in debug mode. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-11-29 10:57:55 | vstinner | set | recipients: + vstinner, serhiy.storchaka, ZackerySpytz |
| 2018-11-29 10:57:54 | vstinner | set | messageid: <1543489074.99.0.788709270274.issue35337@psf.upfronthosting.co.za> |
| 2018-11-29 10:57:54 | vstinner | link | issue35337 messages |
| 2018-11-29 10:57:54 | vstinner | create | |