Message292239
| Author | vstinner |
|---|---|
| Recipients | orent, serhiy.storchaka, vstinner |
| Date | 2017-04-24.20:59:20 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1493067560.62.0.00749013935485.issue30156@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Come on, yet another crash from property_descr_get()??? It's the 3rd time... Do we really need this micro-optimization? Previous bugs and workarounds: - issue #26811 - issue #24276 Using the FASTCALL calling convention, no temporary tuple is created to pass arguments if you use the _PyObject_FastCall() API and if the called function supports this calling convention. Sadly, namedtuple.attr uses operator.itergetter, itemgetter_call() doesn't support the FASTCALL, and my tp_fastcall patch was rejected: issue #29259. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017-04-24 20:59:20 | vstinner | set | recipients: + vstinner, orent, serhiy.storchaka |
| 2017-04-24 20:59:20 | vstinner | set | messageid: <1493067560.62.0.00749013935485.issue30156@psf.upfronthosting.co.za> |
| 2017-04-24 20:59:20 | vstinner | link | issue30156 messages |
| 2017-04-24 20:59:20 | vstinner | create | |