- Python Home
- About
- News
- Documentation
- Downloads
- Community
- Foundation
- Developer's Guide
- Issue Tracker
- Issues
- Summaries
- User
- Administration
- Help
Message216451
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 | vstinner |
|---|---|
| Recipients | josh.r, neologix, njs, pitrou, skrah, vstinner |
| Date | 2014-04-16.08:04:31 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <CAMpsgwb0voGcf5OdOUf4Cq9iPxEb4S5ASLvXS7d0Dar6hQDA4w@mail.gmail.com> |
| In-reply-to | <534E167F.3060200@free.fr> |
| Content | |
|---|---|
>>> So what is the point of _PyObject_GC_Calloc ? >> >> It calls calloc(size) instead of malloc(size) > > No, the question is why you didn't simply change _PyObject_GC_Malloc > (which is a private function). Oh ok, I didn't understand. I don't like changing the behaviour of functions, but it's maybe fine if the function is private. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-04-16 08:04:31 | vstinner | set | recipients: + vstinner, pitrou, njs, skrah, neologix, josh.r |
| 2014-04-16 08:04:31 | vstinner | link | issue21233 messages |
| 2014-04-16 08:04:31 | vstinner | create | |

