➜

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 christian.heimes
Recipients christian.heimes, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2016-09-13.17:19:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473787178.2.0.0635964275837.issue28126@psf.upfronthosting.co.za>
In-reply-to
Content 
Perfect, thanks! Should we keep the Py_MEMCPY() macro for now and define it to memcpy()? Or should I get rid of it and just define it for b/w compatibility?
History
Date User Action Args
2016-09-13 17:19:38christian.heimessetrecipients: + christian.heimes, paul.moore, vstinner, tim.golden, zach.ware, steve.dower
2016-09-13 17:19:38christian.heimessetmessageid: <1473787178.2.0.0635964275837.issue28126@psf.upfronthosting.co.za>
2016-09-13 17:19:38christian.heimeslinkissue28126 messages
2016-09-13 17:19:38christian.heimescreate