Bugs item #1668032, was opened at 2007-02-24 21:01 Message generated for change (Comment added) made by gbrandl You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1668032&group_id=5470
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Documentation Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Daniel Stutzbach (agthorr) Assigned to: Nobody/Anonymous (nobody) Summary: PyMem_Realloc docs don't specifiy out-of-mem behavior Initial Comment: I suggest adding the following text to the documentation for PyMem_Realloc: "If the request fails, PyMem_Realloc returns NULL and p remains a valid allocated pointer." I dug into obmalloc.c to figure out the behavior. ---------------------------------------------------------------------- >Comment By: Georg Brandl (gbrandl) Date: 2007-03-02 20:30 Message: Logged In: YES user_id=849994 Originator: NO Fixed in rev. 54088, 54089 (2.5). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1668032&group_id=5470 _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
