Gecko [ v99win.today ]

Name	Size	Permission
abstract.html	7.8 KB	-rw-r--r--
allocation.html	24.04 KB	-rw-r--r--
arg.html	64.25 KB	-rw-r--r--
bool.html	11.44 KB	-rw-r--r--
buffer.html	58.49 KB	-rw-r--r--
bytearray.html	18.39 KB	-rw-r--r--
capsule.html	26.78 KB	-rw-r--r--
cell.html	13.74 KB	-rw-r--r--
class.html	14.3 KB	-rw-r--r--
cobject.html	15.67 KB	-rw-r--r--
code.html	15.57 KB	-rw-r--r--
codec.html	29.28 KB	-rw-r--r--
complex.html	25.03 KB	-rw-r--r--
concrete.html	15.93 KB	-rw-r--r--
conversion.html	29.24 KB	-rw-r--r--
datetime.html	35.92 KB	-rw-r--r--
descriptor.html	15.74 KB	-rw-r--r--
dict.html	42.03 KB	-rw-r--r--
exceptions.html	112.66 KB	-rw-r--r--
file.html	28.8 KB	-rw-r--r--
float.html	21.5 KB	-rw-r--r--
function.html	17.69 KB	-rw-r--r--
gcsupport.html	29.5 KB	-rw-r--r--
gen.html	9.84 KB	-rw-r--r--
import.html	43.14 KB	-rw-r--r--
index.html	13.69 KB	-rw-r--r--
init.html	122.91 KB	-rw-r--r--
int.html	24.28 KB	-rw-r--r--
intro.html	57.73 KB	-rw-r--r--
iter.html	11.38 KB	-rw-r--r--
iterator.html	13.32 KB	-rw-r--r--
list.html	31.45 KB	-rw-r--r--
long.html	39.54 KB	-rw-r--r--
mapping.html	20.85 KB	-rw-r--r--
marshal.html	18.82 KB	-rw-r--r--
memory.html	37.51 KB	-rw-r--r--
method.html	16.77 KB	-rw-r--r--
module.html	21.95 KB	-rw-r--r--
none.html	8.76 KB	-rw-r--r--
number.html	64.95 KB	-rw-r--r--
objbuffer.html	14.62 KB	-rw-r--r--
object.html	74.9 KB	-rw-r--r--
objimpl.html	7.59 KB	-rw-r--r--
refcounting.html	14.46 KB	-rw-r--r--
reflection.html	12.81 KB	-rw-r--r--
sequence.html	41.73 KB	-rw-r--r--
set.html	35.44 KB	-rw-r--r--
slice.html	16.89 KB	-rw-r--r--
string.html	46.73 KB	-rw-r--r--
structures.html	41.96 KB	-rw-r--r--
sys.html	26.72 KB	-rw-r--r--
tuple.html	27.17 KB	-rw-r--r--
type.html	19.18 KB	-rw-r--r--
typeobj.html	209.91 KB	-rw-r--r--
unicode.html	160.87 KB	-rw-r--r--
utilities.html	7.88 KB	-rw-r--r--
veryhigh.html	66.91 KB	-rw-r--r--
weakref.html	15.68 KB	-rw-r--r--

Code Editor : memory.html

<!DOCTYPE html>

<title>Memory Management &#8212; Python 2.7.18 documentation</title>
 <link rel="stylesheet" type="text/css" href="../_static/pygments.css" />
 <link rel="stylesheet" type="text/css" href="../_static/classic.css" />
 
 <script data-url_root="../" id="documentation_options" src="../_static/documentation_options.js"></script>
 <script src="../_static/jquery.js"></script>
 <script src="../_static/underscore.js"></script>
 <script src="../_static/doctools.js"></script>
 
 <script src="../_static/sidebar.js"></script>
 
 <link rel="search" type="application/opensearchdescription+xml"
 title="Search within Python 2.7.18 documentation"
 href="../_static/opensearch.xml"/>
 <link rel="author" title="About these documents" href="../about.html" />
 <link rel="index" title="Index" href="../genindex.html" />
 <link rel="search" title="Search" href="../search.html" />
 <link rel="copyright" title="Copyright" href="../copyright.html" />
 <link rel="next" title="Object Implementation Support" href="objimpl.html" />
 <link rel="prev" title="Initialization, Finalization, and Threads" href="init.html" />
 <link rel="shortcut icon" type="image/png" href="../_static/py.png" />
 <link rel="canonical" href="file:///usr/share/doc/python2.7/html/c-api/memory.html" />
 <script type="text/javascript" src="../_static/copybutton.js"></script>

</head><body>
<div id="outdated-warning" style="padding: .5em; text-align: center; background-color: #FFBABA; color: #6A0E0E;">
 This document is for an old version of Python that is <a href="https://devguide.python.org/devcycle/#end-of-life-branches">no longer supported</a>.
 You should install the python3 and python3-doc packages and read the 
 <a href="file:///usr/share/doc/python3-doc/html/c-api/memory.html"> Python documentation for the Python3 version packaged in this release</a>.
</div>
 
 <div class="related" role="navigation" aria-label="related navigation">
 <h3>Navigation</h3>
 <ul>
 <li class="right" style="margin-right: 10px">
 <a href="../genindex.html" title="General Index"
 accesskey="I">index</a></li>
 <li class="right" >
 <a href="../py-modindex.html" title="Python Module Index"
 >modules</a> |</li>
 <li class="right" >
 <a href="objimpl.html" title="Object Implementation Support"
 accesskey="N">next</a> |</li>
 <li class="right" >
 <a href="init.html" title="Initialization, Finalization, and Threads"
 accesskey="P">previous</a> |</li>
 <li><img src="../_static/py.png" alt=""
 style="vertical-align: middle; margin-top: -1px"/></li>
 <li><a href="https://www.python.org/">Python</a> &#187;</li>
 <li>
 <a href="../index.html">Python 2.7.18 documentation</a> &#187;
 </li>

<li class="nav-item nav-item-1"><a href="index.html" accesskey="U">Python/C API Reference Manual</a> &#187;</li>
 <li class="nav-item nav-item-this"><a href="">Memory Management</a></li> 
 </ul>
 </div>

<div class="document">
 <div class="documentwrapper">
 <div class="bodywrapper">
 <div class="body" role="main">
 
 <section id="memory-management">
<h1>Memory Management<a class="headerlink" href="#memory-management" title="Permalink to this headline">¶</a></h1>
<section id="overview">
<h2>Overview<a class="headerlink" href="#overview" title="Permalink to this headline">¶</a></h2>
Memory management in Python involves a private heap containing all Python
objects and data structures. The management of this private heap is ensured
internally by the Python memory manager. The Python memory manager has
different components which deal with various dynamic storage management aspects,
like sharing, segmentation, preallocation or caching.
At the lowest level, a raw memory allocator ensures that there is enough room in
the private heap for storing all Python-related data by interacting with the
memory manager of the operating system. On top of the raw memory allocator,
several object-specific allocators operate on the same heap and implement
distinct memory management policies adapted to the peculiarities of every object
type. For example, integer objects are managed differently within the heap than
strings, tuples or dictionaries because integers imply different storage
requirements and speed/space tradeoffs. The Python memory manager thus delegates
some of the work to the object-specific allocators, but ensures that the latter
operate within the bounds of the private heap.
It is important to understand that the management of the Python heap is
performed by the interpreter itself and that the user has no control over it,
even if they regularly manipulate object pointers to memory blocks inside that
heap. The allocation of heap space for Python objects and other internal
buffers is performed on demand by the Python memory manager through the Python/C
API functions listed in this document.
To avoid memory corruption, extension writers should never try to operate on
Python objects with the functions exported by the C library: <code class="xref c c-func docutils literal notranslate">malloc()</code>,
<code class="xref c c-func docutils literal notranslate">calloc()</code>, <code class="xref c c-func docutils literal notranslate">realloc()</code> and <code class="xref c c-func docutils literal notranslate">free()</code>. This will result in mixed
calls between the C allocator and the Python memory manager with fatal
consequences, because they implement different algorithms and operate on
different heaps. However, one may safely allocate and release memory blocks
with the C library allocator for individual purposes, as shown in the following
example:
<div class="highlight-default notranslate"><div class="highlight"><pre>PyObject *res;
char *buf = (char *) malloc(BUFSIZ); /* for I/O */

if (buf == NULL)
 return PyErr_NoMemory();
...Do some I/O operation involving buf...
res = PyString_FromString(buf);
free(buf); /* malloc&#39;ed */
return res;
</pre></div>
</div>
In this example, the memory request for the I/O buffer is handled by the C
library allocator. The Python memory manager is involved only in the allocation
of the string object returned as a result.
In most situations, however, it is recommended to allocate memory from the
Python heap specifically because the latter is under control of the Python
memory manager. For example, this is required when the interpreter is extended
with new object types written in C. Another reason for using the Python heap is
the desire to inform the Python memory manager about the memory needs of the
extension module. Even when the requested memory is used exclusively for
internal, highly-specific purposes, delegating all memory requests to the Python
memory manager causes the interpreter to have a more accurate image of its
memory footprint as a whole. Consequently, under certain circumstances, the
Python memory manager may or may not trigger appropriate actions, like garbage
collection, memory compaction or other preventive procedures. Note that by using
the C library allocator as shown in the previous example, the allocated memory
for the I/O buffer escapes completely the Python memory manager.
</section>
<section id="memory-interface">
<h2>Memory Interface<a class="headerlink" href="#memory-interface" title="Permalink to this headline">¶</a></h2>
The following function sets, modeled after the ANSI C standard, but specifying
behavior when requesting zero bytes, are available for allocating and releasing
memory from the Python heap:
<dl class="c function">
<dt class="sig sig-object c" id="c.PyMem_Malloc">
void *PyMem_Malloc(size_t n)<a class="headerlink" href="#c.PyMem_Malloc" title="Permalink to this definition">¶</a> </dt>
<dd>Allocates n bytes and returns a pointer of type <code class="xref c c-type docutils literal notranslate">void*</code> to the
allocated memory, or NULL if the request fails. Requesting zero bytes returns
a distinct non-NULL pointer if possible, as if <code class="docutils literal notranslate">PyMem_Malloc(1)</code> had
been called instead. The memory will not have been initialized in any way.
</dd></dl>

<dl class="c function">
<dt class="sig sig-object c" id="c.PyMem_Realloc">
void *PyMem_Realloc(void *p, size_t n)<a class="headerlink" href="#c.PyMem_Realloc" title="Permalink to this definition">¶</a> </dt>
<dd>Resizes the memory block pointed to by p to n bytes. The contents will be
unchanged to the minimum of the old and the new sizes. If p is NULL, the
call is equivalent to <code class="docutils literal notranslate">PyMem_Malloc(n)</code>; else if n is equal to zero,
the memory block is resized but is not freed, and the returned pointer is
non-NULL. Unless p is NULL, it must have been returned by a previous call
to <a class="reference internal" href="#c.PyMem_Malloc" title="PyMem_Malloc"><code class="xref c c-func docutils literal notranslate">PyMem_Malloc()</code></a> or <a class="reference internal" href="#c.PyMem_Realloc" title="PyMem_Realloc"><code class="xref c c-func docutils literal notranslate">PyMem_Realloc()</code></a>. If the request fails,
<a class="reference internal" href="#c.PyMem_Realloc" title="PyMem_Realloc"><code class="xref c c-func docutils literal notranslate">PyMem_Realloc()</code></a> returns NULL and p remains a valid pointer to the
previous memory area.
</dd></dl>

<dl class="c function">
<dt class="sig sig-object c" id="c.PyMem_Free">
void PyMem_Free(void *p)<a class="headerlink" href="#c.PyMem_Free" title="Permalink to this definition">¶</a> </dt>
<dd>Frees the memory block pointed to by p, which must have been returned by a
previous call to <a class="reference internal" href="#c.PyMem_Malloc" title="PyMem_Malloc"><code class="xref c c-func docutils literal notranslate">PyMem_Malloc()</code></a> or <a class="reference internal" href="#c.PyMem_Realloc" title="PyMem_Realloc"><code class="xref c c-func docutils literal notranslate">PyMem_Realloc()</code></a>. Otherwise, or
if <code class="docutils literal notranslate">PyMem_Free(p)</code> has been called before, undefined behavior occurs. If
p is NULL, no operation is performed.
</dd></dl>

The following type-oriented macros are provided for convenience. Note that
TYPE refers to any C type.
<dl class="c function">
<dt class="sig sig-object c" id="c.PyMem_New">
TYPE *PyMem_New(TYPE, size_t n)<a class="headerlink" href="#c.PyMem_New" title="Permalink to this definition">¶</a> </dt>
<dd>Same as <a class="reference internal" href="#c.PyMem_Malloc" title="PyMem_Malloc"><code class="xref c c-func docutils literal notranslate">PyMem_Malloc()</code></a>, but allocates <code class="docutils literal notranslate">(n * sizeof(TYPE))</code> bytes of
memory. Returns a pointer cast to <code class="xref c c-type docutils literal notranslate">TYPE*</code>. The memory will not have
been initialized in any way.
</dd></dl>

<dl class="c function">
<dt class="sig sig-object c" id="c.PyMem_Resize">
TYPE *PyMem_Resize(void *p, TYPE, size_t n)<a class="headerlink" href="#c.PyMem_Resize" title="Permalink to this definition">¶</a> </dt>
<dd>Same as <a class="reference internal" href="#c.PyMem_Realloc" title="PyMem_Realloc"><code class="xref c c-func docutils literal notranslate">PyMem_Realloc()</code></a>, but the memory block is resized to <code class="docutils literal notranslate">(n *
sizeof(TYPE))</code> bytes. Returns a pointer cast to <code class="xref c c-type docutils literal notranslate">TYPE*</code>. On return,
p will be a pointer to the new memory area, or NULL in the event of
failure. This is a C preprocessor macro; p is always reassigned. Save
the original value of p to avoid losing memory when handling errors.
</dd></dl>

<dl class="c function">
<dt class="sig sig-object c" id="c.PyMem_Del">
void PyMem_Del(void *p)<a class="headerlink" href="#c.PyMem_Del" title="Permalink to this definition">¶</a> </dt>
<dd>Same as <a class="reference internal" href="#c.PyMem_Free" title="PyMem_Free"><code class="xref c c-func docutils literal notranslate">PyMem_Free()</code></a>.
</dd></dl>

In addition, the following macro sets are provided for calling the Python memory
allocator directly, without involving the C API functions listed above. However,
note that their use does not preserve binary compatibility across Python
versions and is therefore deprecated in extension modules.
<code class="xref c c-func docutils literal notranslate">PyMem_MALLOC()</code>, <code class="xref c c-func docutils literal notranslate">PyMem_REALLOC()</code>, <code class="xref c c-func docutils literal notranslate">PyMem_FREE()</code>.
<code class="xref c c-func docutils literal notranslate">PyMem_NEW()</code>, <code class="xref c c-func docutils literal notranslate">PyMem_RESIZE()</code>, <code class="xref c c-func docutils literal notranslate">PyMem_DEL()</code>.
</section>
<section id="object-allocators">
<h2>Object allocators<a class="headerlink" href="#object-allocators" title="Permalink to this headline">¶</a></h2>
The following function sets, modeled after the ANSI C standard, but specifying
behavior when requesting zero bytes, are available for allocating and releasing
memory from the Python heap.
By default, these functions use <a class="reference internal" href="#pymalloc">pymalloc memory allocator</a>.
<div class="admonition warning">
Warning
The <a class="reference internal" href="../glossary.html#term-global-interpreter-lock">GIL</a> must be held when using these
functions.
</div>
<dl class="c function">
<dt class="sig sig-object c" id="c.PyObject_Malloc">
void *PyObject_Malloc(size_t n)<a class="headerlink" href="#c.PyObject_Malloc" title="Permalink to this definition">¶</a> </dt>
<dd>Allocates n bytes and returns a pointer of type <code class="xref c c-type docutils literal notranslate">void*</code> to the
allocated memory, or NULL if the request fails.
Requesting zero bytes returns a distinct non-NULL pointer if possible, as
if <code class="docutils literal notranslate">PyObject_Malloc(1)</code> had been called instead. The memory will not have
been initialized in any way.
</dd></dl>

<dl class="c function">
<dt class="sig sig-object c" id="c.PyObject_Realloc">
void *PyObject_Realloc(void *p, size_t n)<a class="headerlink" href="#c.PyObject_Realloc" title="Permalink to this definition">¶</a> </dt>
<dd>Resizes the memory block pointed to by p to n bytes. The contents will be
unchanged to the minimum of the old and the new sizes.
If p is NULL, the call is equivalent to <code class="docutils literal notranslate">PyObject_Malloc(n)</code>; else if n
is equal to zero, the memory block is resized but is not freed, and the
returned pointer is non-NULL.
Unless p is NULL, it must have been returned by a previous call to
<a class="reference internal" href="#c.PyObject_Malloc" title="PyObject_Malloc"><code class="xref c c-func docutils literal notranslate">PyObject_Malloc()</code></a>, <a class="reference internal" href="#c.PyObject_Realloc" title="PyObject_Realloc"><code class="xref c c-func docutils literal notranslate">PyObject_Realloc()</code></a> or <code class="xref c c-func docutils literal notranslate">PyObject_Calloc()</code>.
If the request fails, <a class="reference internal" href="#c.PyObject_Realloc" title="PyObject_Realloc"><code class="xref c c-func docutils literal notranslate">PyObject_Realloc()</code></a> returns NULL and p remains
a valid pointer to the previous memory area.
</dd></dl>

<dl class="c function">
<dt class="sig sig-object c" id="c.PyObject_Free">
void PyObject_Free(void *p)<a class="headerlink" href="#c.PyObject_Free" title="Permalink to this definition">¶</a> </dt>
<dd>Frees the memory block pointed to by p, which must have been returned by a
previous call to <a class="reference internal" href="#c.PyObject_Malloc" title="PyObject_Malloc"><code class="xref c c-func docutils literal notranslate">PyObject_Malloc()</code></a>, <a class="reference internal" href="#c.PyObject_Realloc" title="PyObject_Realloc"><code class="xref c c-func docutils literal notranslate">PyObject_Realloc()</code></a> or
<code class="xref c c-func docutils literal notranslate">PyObject_Calloc()</code>. Otherwise, or if <code class="docutils literal notranslate">PyObject_Free(p)</code> has been called
before, undefined behavior occurs.
If p is NULL, no operation is performed.
</dd></dl>

In addition, the following macro sets are provided:
<ul class="simple">
<li><code class="xref c c-func docutils literal notranslate">PyObject_MALLOC()</code>: alias to <a class="reference internal" href="#c.PyObject_Malloc" title="PyObject_Malloc"><code class="xref c c-func docutils literal notranslate">PyObject_Malloc()</code></a></li>
<li><code class="xref c c-func docutils literal notranslate">PyObject_REALLOC()</code>: alias to <a class="reference internal" href="#c.PyObject_Realloc" title="PyObject_Realloc"><code class="xref c c-func docutils literal notranslate">PyObject_Realloc()</code></a></li>
<li><code class="xref c c-func docutils literal notranslate">PyObject_FREE()</code>: alias to <a class="reference internal" href="#c.PyObject_Free" title="PyObject_Free"><code class="xref c c-func docutils literal notranslate">PyObject_Free()</code></a></li>
<li><a class="reference internal" href="allocation.html#c.PyObject_Del" title="PyObject_Del"><code class="xref c c-func docutils literal notranslate">PyObject_Del()</code></a>: alias to <a class="reference internal" href="#c.PyObject_Free" title="PyObject_Free"><code class="xref c c-func docutils literal notranslate">PyObject_Free()</code></a></li>
<li><code class="xref c c-func docutils literal notranslate">PyObject_DEL()</code>: alias to <code class="xref c c-func docutils literal notranslate">PyObject_FREE()</code> (so finally an alias
to <a class="reference internal" href="#c.PyObject_Free" title="PyObject_Free"><code class="xref c c-func docutils literal notranslate">PyObject_Free()</code></a>)</li>
</ul>
</section>
<section id="the-pymalloc-allocator">
<h2>The pymalloc allocator<a class="headerlink" href="#the-pymalloc-allocator" title="Permalink to this headline">¶</a></h2>
Python has a pymalloc allocator optimized for small objects (smaller or equal
to 512 bytes) with a short lifetime. It uses memory mappings called “arenas”
with a fixed size of 256 KiB. It falls back to <code class="xref c c-func docutils literal notranslate">malloc()</code> and
<code class="xref c c-func docutils literal notranslate">realloc()</code> for allocations larger than 512 bytes.
pymalloc is the default allocator of <a class="reference internal" href="#c.PyObject_Malloc" title="PyObject_Malloc"><code class="xref c c-func docutils literal notranslate">PyObject_Malloc()</code></a>.
The arena allocator uses the following functions:
<ul class="simple">
<li><code class="xref c c-func docutils literal notranslate">mmap()</code> and <code class="xref c c-func docutils literal notranslate">munmap()</code> if available,</li>
<li><code class="xref c c-func docutils literal notranslate">malloc()</code> and <code class="xref c c-func docutils literal notranslate">free()</code> otherwise.</li>
</ul>
<div class="versionchanged">
Changed in version 2.7.7: The threshold changed from 256 to 512 bytes. The arena allocator now
uses <code class="xref c c-func docutils literal notranslate">mmap()</code> if available.
</div>
</section>
<section id="examples">
<h2>Examples<a class="headerlink" href="#examples" title="Permalink to this headline">¶</a></h2>
Here is the example from section <a class="reference internal" href="#memoryoverview">Overview</a>, rewritten so that the
I/O buffer is allocated from the Python heap by using the first function set:
<div class="highlight-default notranslate"><div class="highlight"><pre>PyObject *res;
char *buf = (char *) PyMem_Malloc(BUFSIZ); /* for I/O */

if (buf == NULL)
 return PyErr_NoMemory();
/* ...Do some I/O operation involving buf... */
res = PyString_FromString(buf);
PyMem_Del(buf); /* allocated with PyMem_New */
return res;
</pre></div>
</div>
Note that in the two examples above, the buffer is always manipulated via
functions belonging to the same set. Indeed, it is required to use the same
memory API family for a given memory block, so that the risk of mixing different
allocators is reduced to a minimum. The following code sequence contains two
errors, one of which is labeled as fatal because it mixes two different
allocators operating on different heaps.
<div class="highlight-default notranslate"><div class="highlight"><pre>char *buf1 = PyMem_New(char, BUFSIZ);
char *buf2 = (char *) malloc(BUFSIZ);
char *buf3 = (char *) PyMem_Malloc(BUFSIZ);
...
PyMem_Del(buf3); /* Wrong -- should be PyMem_Free() */
free(buf2); /* Right -- allocated via malloc() */
free(buf1); /* Fatal -- should be PyMem_Del() */
</pre></div>
</div>
In addition to the functions aimed at handling raw memory blocks from the Python
heap, objects in Python are allocated and released with <a class="reference internal" href="allocation.html#c.PyObject_New" title="PyObject_New"><code class="xref c c-func docutils literal notranslate">PyObject_New()</code></a>,
<a class="reference internal" href="allocation.html#c.PyObject_NewVar" title="PyObject_NewVar"><code class="xref c c-func docutils literal notranslate">PyObject_NewVar()</code></a> and <a class="reference internal" href="allocation.html#c.PyObject_Del" title="PyObject_Del"><code class="xref c c-func docutils literal notranslate">PyObject_Del()</code></a>.
These will be explained in the next chapter on defining and implementing new
object types in C.
</section>
</section>

<div class="clearer"></div>
 </div>
 </div>
 </div>
 <div class="sphinxsidebar" role="navigation" aria-label="main navigation">
 <div class="sphinxsidebarwrapper">
 <h3><a href="../contents.html">Table of Contents</a></h3>
 <ul>
<li><a class="reference internal" href="#">Memory Management</a><ul>
<li><a class="reference internal" href="#overview">Overview</a></li>
<li><a class="reference internal" href="#memory-interface">Memory Interface</a></li>
<li><a class="reference internal" href="#object-allocators">Object allocators</a></li>
<li><a class="reference internal" href="#the-pymalloc-allocator">The pymalloc allocator</a></li>
<li><a class="reference internal" href="#examples">Examples</a></li>
</ul>
</li>
</ul>

<h4>Previous topic</h4>
 <a href="init.html"
 title="previous chapter">Initialization, Finalization, and Threads</a>
 <h4>Next topic</h4>
 <a href="objimpl.html"
 title="next chapter">Object Implementation Support</a>
 <div role="note" aria-label="source link">
 <h3>This Page</h3>
 <ul class="this-page-menu">
 <li><a href="../_sources/c-api/memory.rst.txt"
 rel="nofollow">Show Source</a></li>
 </ul>
 </div>
<div id="searchbox" style="display: none" role="search">
 <h3 id="searchlabel">Quick search</h3>
 <div class="searchformwrapper">
 <form class="search" action="../search.html" method="get">
 <input type="text" name="q" aria-labelledby="searchlabel" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false"/>
 <input type="submit" value="Go" />
 </form>
 </div>
</div>
<script>$('#searchbox').show(0);</script>
 </div>
 </div>
 <div class="clearer"></div>
 </div> 
 <div class="related" role="navigation" aria-label="related navigation">
 <h3>Navigation</h3>
 <ul>
 <li class="right" style="margin-right: 10px">
 <a href="../genindex.html" title="General Index"
 >index</a></li>
 <li class="right" >
 <a href="../py-modindex.html" title="Python Module Index"
 >modules</a> |</li>
 <li class="right" >
 <a href="objimpl.html" title="Object Implementation Support"
 >next</a> |</li>
 <li class="right" >
 <a href="init.html" title="Initialization, Finalization, and Threads"
 >previous</a> |</li>
 <li><img src="../_static/py.png" alt=""
 style="vertical-align: middle; margin-top: -1px"/></li>
 <li><a href="https://www.python.org/">Python</a> &#187;</li>
 <li>
 <a href="../index.html">Python 2.7.18 documentation</a> &#187;
 </li>

<li class="nav-item nav-item-1"><a href="index.html" >Python/C API Reference Manual</a> &#187;</li>
 <li class="nav-item nav-item-this"><a href="">Memory Management</a></li> 
 </ul>
 </div> 
 <div class="footer">
 &copy; <a href="../copyright.html">Copyright</a> 1990-2024, Python Software Foundation.
 
 The Python Software Foundation is a non-profit corporation.
 <a href="https://www.python.org/psf/donations/">Please donate.</a>
 
 Last updated on December 09, 2024.
 <a href="../bugs.html">Found a bug</a>?
 
 Created using <a href="http://sphinx.pocoo.org/">Sphinx</a> 4.3.2.
 </div>

</body>
</html>

${this.title}

Code Editor : memory.html