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 steve.dower
Recipients Alexander Riccio, loewis, paul.moore, serhiy.storchaka, skrah, steve.dower, tim.golden, zach.ware
Date 2016-01-16.22:06:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
libmpdec/memory.c keeps pointers to customisable memory functions (malloc/free) and initialises them to &malloc and &free. These functions are dllimport'd from the CRT, and so they trigger a warning letting you know that "&malloc == &malloc" may not always be true.

(That trivial comparison should always be true, but if you indirect one of the values through a few other modules it may be an address of a different stub function that calls the real malloc, and hence the addresses may not match.)
Date User Action Args
2016-01-16 22:06:15steve.dowersetrecipients: + steve.dower, loewis, paul.moore, tim.golden, skrah, zach.ware, serhiy.storchaka, Alexander Riccio
2016-01-16 22:06:15steve.dowersetmessageid: <>
2016-01-16 22:06:15steve.dowerlinkissue25878 messages
2016-01-16 22:06:15steve.dowercreate