Message259390
| Author | vstinner |
|---|---|
| Recipients | Yury.Selivanov, jtaylor, pitrou, rhettinger, serhiy.storchaka, vstinner, yselivanov |
| Date | 2016-02-02.14:48:38 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1454424518.45.0.277729800673.issue26249@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
>> It looks like some benchmarks are up to 4% faster: > What this says is that some internals uses of PyMem_XXX should be replaced with PyObject_XXX. Why not changing PyMem_XXX to use the same fast allocator than PyObject_XXX? (as proposed in this issue) FYI we now also have the PyMem_RawXXX family :) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2016-02-02 14:48:38 | vstinner | set | recipients: + vstinner, rhettinger, pitrou, Yury.Selivanov, jtaylor, serhiy.storchaka, yselivanov |
| 2016-02-02 14:48:38 | vstinner | set | messageid: <1454424518.45.0.277729800673.issue26249@psf.upfronthosting.co.za> |
| 2016-02-02 14:48:38 | vstinner | link | issue26249 messages |
| 2016-02-02 14:48:38 | vstinner | create | |