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 vstinner
Date 2008-09-24.00:29:15
SpamBayes Score 6.6059075e-10
Marked as misclassified No
Message-id <1222216158.64.0.600054741786.issue3951@psf.upfronthosting.co.za>
In-reply-to
Content
In rev 56476, martin.v.loewis enabled Py_USING_MEMORY_DEBUGGER by 
default in an huge commit:
   PEP 3123: Provide forward compatibility with Python 3.0, 
   while keeping backwards compatibility. Add Py_Refcnt, 
   Py_Type, Py_Size, and PyVarObject_HEAD_INIT.

I guess that's an error, and that Py_USING_MEMORY_DEBUGGER should be 
disabled by default.

Proposition to avoid such bug in future: create a configure option, 
like --with-memory-debugger. See for example my patch to configure.in 
(you will need to run autoconf && autoheader).
History
Date User Action Args
2008-09-24 00:29:19vstinnersetrecipients: + vstinner
2008-09-24 00:29:18vstinnersetmessageid: <1222216158.64.0.600054741786.issue3951@psf.upfronthosting.co.za>
2008-09-24 00:29:17vstinnerlinkissue3951 messages
2008-09-24 00:29:17vstinnercreate