Message216422
| Author | vstinner |
|---|---|
| Recipients | josh.r, neologix, njs, pitrou, skrah, vstinner |
| Date | 2014-04-16.02:40:55 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1397616056.23.0.259994659332.issue21233@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> So what is the point of _PyObject_GC_Calloc ? It calls calloc(size) instead of malloc(size), calloc() which can be faster than malloc()+memset(), see: https://mail.python.org/pipermail/python-dev/2014-April/133985.html _PyObject_GC_Calloc() is used by PyType_GenericAlloc(). If I understand directly, it is the default allocator to allocate Python objects. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-04-16 02:40:56 | vstinner | set | recipients: + vstinner, pitrou, njs, skrah, neologix, josh.r |
| 2014-04-16 02:40:56 | vstinner | set | messageid: <1397616056.23.0.259994659332.issue21233@psf.upfronthosting.co.za> |
| 2014-04-16 02:40:56 | vstinner | link | issue21233 messages |
| 2014-04-16 02:40:55 | vstinner | create | |