- Python Home
- About
- News
- Documentation
- Downloads
- Community
- Foundation
- Developer's Guide
- Issue Tracker
- Issues
- Summaries
- User
- Administration
- Help
Message217471
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 | Kim.Gräsman |
|---|---|
| Recipients | Kim.Gräsman, brian.curtin, python-dev, terry.reedy, tim.golden, tim.peters |
| Date | 2014-04-29.05:55:35 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1398750935.74.0.232556577851.issue18314@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
By the way, is PyMem_RawMalloc/PyMem_RawFree preferred for memory allocation across the board? If so, I can just prepare a new patch for you with that changed, zero-initialization in place and the prefix-overrun fixed. I might get to it tonight. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-04-29 05:55:35 | Kim.Gräsman | set | recipients: + Kim.Gräsman, tim.peters, terry.reedy, tim.golden, brian.curtin, python-dev |
| 2014-04-29 05:55:35 | Kim.Gräsman | set | messageid: <1398750935.74.0.232556577851.issue18314@psf.upfronthosting.co.za> |
| 2014-04-29 05:55:35 | Kim.Gräsman | link | issue18314 messages |
| 2014-04-29 05:55:35 | Kim.Gräsman | create | |

