- Python Home
- About
- News
- Documentation
- Downloads
- Community
- Foundation
- Developer's Guide
- Issue Tracker
- Issues
- Summaries
- User
- Administration
- Help
Message216404
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 | josh.r |
|---|---|
| Recipients | josh.r, neologix, njs, pitrou, skrah, vstinner |
| Date | 2014-04-15.22:20:09 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1397600409.13.0.112677372422.issue21233@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Sorry for breaking it up, but the same comment on consistent prototypes mirroring the C standard lib calloc would apply to all the API functions as well, e.g. PyMem_RawCalloc, PyMem_Calloc, PyObject_Calloc and _PyObject_GC_Calloc, not just the structure function pointer. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-04-15 22:20:09 | josh.r | set | recipients: + josh.r, pitrou, vstinner, njs, skrah, neologix |
| 2014-04-15 22:20:09 | josh.r | set | messageid: <1397600409.13.0.112677372422.issue21233@psf.upfronthosting.co.za> |
| 2014-04-15 22:20:09 | josh.r | link | issue21233 messages |
| 2014-04-15 22:20:09 | josh.r | create | |

