summaryrefslogtreecommitdiffstats
path: root/Doc/c-api
Commit message (Collapse)AuthorAgeFilesLines
...
* | Merge for issue #26760Brett Cannon2016-04-151-1/+7
|\ \ | |/
| * Issue #26760: Minimally document PyFrameObjectBrett Cannon2016-04-151-1/+7
| |
* | Issue #15984: Merge PyUnicode doc from 3.5Martin Panter2016-04-155-12/+14
|\ \ | |/
| * Issue #15984: Correct PyUnicode_FromObject() and _FromEncodedObject() docsMartin Panter2016-04-151-5/+7
| |
| * Correct “an” → “a” with “Unicode”, “user”, “UTF”, etcMartin Panter2016-04-155-8/+8
| | | | | | | | This affects documentation, code comments, and a debugging messages.
* | Fix typo in doc: avoid the french "& cie" :-)Victor Stinner2016-03-231-1/+1
| |
* | On ResourceWarning, log traceback where the object was allocatedVictor Stinner2016-03-191-0/+8
| | | | | | | | | | | | | | | | | | | | Issue #26567: * Add a new function PyErr_ResourceWarning() function to pass the destroyed object * Add a source attribute to warnings.WarningMessage * Add warnings._showwarnmsg() which uses tracemalloc to get the traceback where source object was allocated.
* | Doc: fix typos, patch written by Stefan BehnelVictor Stinner2016-03-181-1/+1
| |
* | Enhance documentation on malloc debug hooksVictor Stinner2016-03-181-3/+6
| | | | | | | | Issue #26564, #26516, #26563.
* | On memory error, dump the memory block tracebackVictor Stinner2016-03-151-0/+7
| | | | | | | | | | | | Issue #26564: _PyObject_DebugDumpAddress() now dumps the traceback where a memory block was allocated on memory block. Use the tracemalloc module to get the traceback.
* | Check the GIL in PyObject_Malloc()Victor Stinner2016-03-141-3/+6
| | | | | | | | | | Issue #26558: The debug hook of PyObject_Malloc() now checks that the GIL is held when the function is called.
* | Add PYTHONMALLOC env varVictor Stinner2016-03-141-12/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | Issue #26516: * Add PYTHONMALLOC environment variable to set the Python memory allocators and/or install debug hooks. * PyMem_SetupDebugHooks() can now also be used on Python compiled in release mode. * The PYTHONMALLOCSTATS environment variable can now also be used on Python compiled in release mode. It now has no effect if set to an empty string. * In debug mode, debug hooks are now also installed on Python memory allocators when Python is configured without pymalloc.
* | Merge 3.5 (malloc doc)Victor Stinner2016-03-091-43/+77
|\ \ | |/
| * Issue #26516: Enhance Python mem allocators docVictor Stinner2016-03-091-43/+77
| | | | | | | | | | | | | | * add link to PYTHONMALLOCSTATS env var * add parameters to PyMem macros like PyMem_MALLOC() * fix PyMem_SetupDebugHooks(): add Calloc functions * add some newlines for readability
* | Issue #22836: Merge exception reporting from 3.5Martin Panter2016-02-281-2/+2
|\ \ | |/
| * Issue #22836: Keep exception reports sensible despite errorsMartin Panter2016-02-281-2/+2
| |
* | Issue #25985: sys.version_info is now used instead of sys.versionSerhiy Storchaka2016-02-111-3/+4
| | | | | | | | to format short Python version.
* | Issue #26304: Merge doc wording from 3.5Martin Panter2016-02-102-2/+2
|\ \ | |/
| * Issue #26304: Change "allows to <verb>" to "allows <verb>ing" or similarMartin Panter2016-02-102-2/+2
| | | | | | | | | | The original form is incorrect grammar and feels awkward, even though the meaning is clear.
| * Issue #26198: Fixed error messages for some argument parsing errors.Serhiy Storchaka2016-02-071-1/+2
| | | | | | | | | | Fixed the documented about buffer overflow error for "es#" and "et#" format units.
* | Add a link to PEP 384 in stable.rstBerker Peksag2016-01-281-1/+1
|\ \ | |/
| * Add a link to PEP 384 in stable.rstBerker Peksag2016-01-281-1/+1
| |
* | merge from 3.5Senthil Kumaran2016-01-211-7/+7
|\ \ | |/ | | | | | | | | | | issue25909 - Correct the documentation of PyMapping_Items, PyMapping_Keys and PyMapping_Values in Include/abstract.h and Doc/c-api/mapping.rst. Patch contributed by Sonali Gupta.
| * issue25909 - Correct the documentation of PyMapping_Items, PyMapping_Keys andSenthil Kumaran2016-01-211-7/+7
| | | | | | | | | | | | PyMapping_Values in Include/abstract.h and Doc/c-api/mapping.rst. Patch contributed by Sonali Gupta.
* | Merge for issue #12484Brett Cannon2015-12-271-5/+0
|\ \ | |/
| * Issue #12484: Remove a mention of Py_InitModule() and ↵Brett Cannon2015-12-271-5/+0
| | | | | | | | | | | | | | _PyImport_FixupExtension(). Thanks to Alejandro Santos for the bug report and Anish Shah for the patch.
* | Issue #25701: Merge set and delete documentation from 3.5Martin Panter2015-12-083-19/+40
|\ \ | |/
| * Issue #25701: Document C API functions that both set and delete objectsMartin Panter2015-12-083-19/+40
| | | | | | | | | | | | Also document that the separate functions that delete objects are preferred; using PyObject_SetAttr(), _SetAttrString(), and PySequence_SetItem() to delete is deprecated.
* | Issue #5319: New Py_FinalizeEx() API to exit with status 120 on failureMartin Panter2015-11-303-19/+32
|/
* Issue #25706: Fixed markup in the documentation.Serhiy Storchaka2015-11-231-1/+1
|\
| * Issue #25706: Fixed markup in the documentation.Serhiy Storchaka2015-11-231-1/+1
| |
* | Issue #25523: Merge "a" to "an" fixes from 3.4 into 3.5Martin Panter2015-11-021-1/+1
|\ \ | |/
| * Issue #25523: Correct "a" article to "an" articleMartin Panter2015-11-021-1/+1
| | | | | | | | | | | | This changes the main documentation, doc strings, source code comments, and a couple error messages in the test suite. In some cases the word was removed or edited some other way to fix the grammar.
* | Issue #25161: Merge full stops from 3.4 into 3.5Martin Panter2015-10-103-3/+3
|\ \ | |/
| * Issue #25161: Add full stops in documentation; patch by Takase ArihiroMartin Panter2015-10-103-3/+3
| |
* | Issue #24808: Merge 3.4 into 3.5; adjust new tp_as_async fieldMartin Panter2015-08-251-5/+5
|\ \ | |/
| * Issue #24808: Update the documentation of some PyTypeObject fieldsMartin Panter2015-08-251-5/+5
| | | | | | | | Patch by Joseph Weston.
* | merge 3.4 (#24883)Benjamin Peterson2015-08-181-4/+4
|\ \ | |/
| * 'Py_Buffer' should be 'Py_buffer' (closes #24883)Benjamin Peterson2015-08-181-4/+4
| |
* | Issue #23756: Clarify the terms "contiguous" and "bytes-like object".Stefan Krah2015-08-082-7/+10
| | | | | | | | Patch by Martin Panter.
* | Merge 3.4Zachary Ware2015-07-071-3/+4
|\ \ | |/
| * Fix usage of the default role.Zachary Ware2015-07-071-3/+4
| | | | | | | | | | The changes to Doc/library/unittest.mock.rst are almost entirely a selective backport of the 3.5 page.
| * Fix suspicious markupZachary Ware2015-07-071-1/+1
| |
* | Close #24458: PEP 489 documentationNick Coghlan2015-07-032-77/+245
| | | | | | | | Patch by Petr Viktorin.
* | Issue #19235: Add new RecursionError exception. Patch by Georg Brandl.Yury Selivanov2015-07-031-3/+9
| |
* | docs.capi: Fix tp_as_async docYury Selivanov2015-06-231-1/+1
| |
* | Issue #24400: Introduce a distinct type for 'async def' coroutines.Yury Selivanov2015-06-223-7/+48
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Summary of changes: 1. Coroutines now have a distinct, separate from generators type at the C level: PyGen_Type, and a new typedef PyCoroObject. PyCoroObject shares the initial segment of struct layout with PyGenObject, making it possible to reuse existing generators machinery. The new type is exposed as 'types.CoroutineType'. As a consequence of having a new type, CO_GENERATOR flag is no longer applied to coroutines. 2. Having a separate type for coroutines made it possible to add an __await__ method to the type. Although it is not used by the interpreter (see details on that below), it makes coroutines naturally (without using __instancecheck__) conform to collections.abc.Coroutine and collections.abc.Awaitable ABCs. [The __instancecheck__ is still used for generator-based coroutines, as we don't want to add __await__ for generators.] 3. Add new opcode: GET_YIELD_FROM_ITER. The opcode is needed to allow passing native coroutines to the YIELD_FROM opcode. Before this change, 'yield from o' expression was compiled to: (o) GET_ITER LOAD_CONST YIELD_FROM Now, we use GET_YIELD_FROM_ITER instead of GET_ITER. The reason for adding a new opcode is that GET_ITER is used in some contexts (such as 'for .. in' loops) where passing a coroutine object is invalid. 4. Add two new introspection functions to the inspec module: getcoroutinestate(c) and getcoroutinelocals(c). 5. inspect.iscoroutine(o) is updated to test if 'o' is a native coroutine object. Before this commit it used abc.Coroutine, and it was requested to update inspect.isgenerator(o) to use abc.Generator; it was decided, however, that inspect functions should really be tailored for checking for native types. 6. sys.set_coroutine_wrapper(w) API is updated to work with only native coroutines. Since types.coroutine decorator supports any type of callables now, it would be confusing that it does not work for all types of coroutines. 7. Exceptions logic in generators C implementation was updated to raise clearer messages for coroutines: Before: TypeError("generator raised StopIteration") After: TypeError("coroutine raised StopIteration")
* | Fixed documentation of functions with const char* arguments.Serhiy Storchaka2015-06-218-14/+14
|\ \ | |/
| * Fixed documentation of functions with const char* arguments.Serhiy Storchaka2015-06-218-14/+14
| |
* | Added the const qualifier for char* argument of Py_EnterRecursiveCall().Serhiy Storchaka2015-06-211-1/+1
|\ \ | |/
generated by cgit v0.12 at 2025-04-11 05:08:54 (GMT)