summaryrefslogtreecommitdiffstats
path: root/Doc/c-api
Commit message (Collapse)AuthorAgeFilesLines
* Fix description for Py_GetPath(); it sounded like it always returned sys.path.Georg Brandl2010-01-071-8/+9
|
* :stmt: -> :keyword:Ezio Melotti2010-01-031-1/+1
|
* Correct documentation for s* z* and w*, the argument that should be passedGregory P. Smith2010-01-021-3/+3
| | | | is the address of a Py_buffer, not a Py_buffer *.
* check if the attribute is set before deleting it with T_OBJECT_EX (fixes #7604)Benjamin Peterson2009-12-301-1/+4
| | | | | Also, add a note to the docs about the better behavior of T_OBJECT_EX as compared to T_OBJECT.
* #7033: add new API function PyErr_NewExceptionWithDoc, for easily giving new ↵Georg Brandl2009-12-281-0/+9
| | | | exceptions a docstring.
* #7577: fix signature of PyBuffer_FillInfo().Georg Brandl2009-12-281-1/+1
|
* Issue #7528: Backport PyLong_AsLongAndOverflow from py3k to trunk.Mark Dickinson2009-12-211-0/+13
| | | | Thanks Case Van Horsen for the patch.
* #7388: "python".capitalize() in the DocEzio Melotti2009-12-191-2/+2
|
* #7521: remove Py_GetBuildNumber(), which was removed in favor of ↵Georg Brandl2009-12-191-9/+0
| | | | Py_GetBuildInfo().
* Issue #7228: Add '%lld' and '%llu' support to PyFormat_FromString,Mark Dickinson2009-11-152-0/+32
| | | | PyFormat_FromStringV and PyErr_Format.
* Deprecate PyOS_ascii_strtod and PyOS_ascii_atof, and document the ↵Mark Dickinson2009-10-311-2/+43
| | | | replacement function PyOS_string_to_double.
* Issue #7169: Document PyFloat_AsString and PyFloat_AsReprString, and note ↵Eric Smith2009-10-191-0/+24
| | | | that they are unsafe and deprecated.
* #6881 - fixed wrong return type; improved the formattingEzio Melotti2009-09-201-10/+19
|
* #6930: clarify description about byteorder handling in UTF decoder routines.Georg Brandl2009-09-181-12/+17
|
* Fix issue #1590864, multiple threads and fork() can cause deadlocks, byThomas Wouters2009-09-161-0/+16
| | | | | | | | | | | | | | | | | | | | | | acquiring the import lock around fork() calls. This prevents other threads from having that lock while the fork happens, and is the recommended way of dealing with such issues. There are two other locks we care about, the GIL and the Thread Local Storage lock. The GIL is obviously held when calling Python functions like os.fork(), and the TLS lock is explicitly reallocated instead, while also deleting now-orphaned TLS data. This only fixes calls to os.fork(), not extension modules or embedding programs calling C's fork() directly. Solving that requires a new set of API functions, and possibly a rewrite of the Python/thread_*.c mess. Add a warning explaining the problem to the documentation in the mean time. This also changes behaviour a little on AIX. Before, AIX (but only AIX) was getting the import lock reallocated, seemingly to avoid this very same problem. This is not the right approach, because the import lock is a re-entrant one, and reallocating would do the wrong thing when forking while holding the import lock. Will backport to 2.6, minus the tiny AIX behaviour change.
* Py_SetPythonHome uses static storage #6913Benjamin Peterson2009-09-151-0/+4
|
* #6821: fix signature of PyBuffer_Release().Georg Brandl2009-09-021-2/+2
|
* #6658: fix two typos.Georg Brandl2009-08-061-2/+2
|
* #6336: Add nb_divide.Georg Brandl2009-07-291-0/+1
|
* builtin -> built-in.Georg Brandl2009-07-263-6/+6
|
* Dont put "void" in signature for nullary functions.Georg Brandl2009-07-247-9/+10
|
* Fix arg types of et#.Georg Brandl2009-07-241-1/+1
|
* Fix style.Georg Brandl2009-07-111-4/+4
|
* #6255: document PyInt_FromSize_t.Georg Brandl2009-06-171-0/+9
|
* #5967: note that the C slicing APIs do not support negative indices.Georg Brandl2009-06-041-4/+6
|
* fix signatureBenjamin Peterson2009-05-311-1/+1
|
* Fix some more small markup problems.Georg Brandl2009-05-301-5/+5
|
* Issue 5954, PyFrame_GetLineNumber:Jeffrey Yasskin2009-05-081-0/+5
| | | | | | | | | | | | | | Most uses of PyCode_Addr2Line (http://www.google.com/codesearch?q=PyCode_Addr2Line) are just trying to get the line number of a specified frame, but there's no way to do that directly. Forcing people to go through the code object makes them know more about the guts of the interpreter than they should need. The remaining uses of PyCode_Addr2Line seem to be getting the line from a traceback (for example, http://www.google.com/codesearch/p?hl=en#u_9_nDrchrw/pygame-1.7.1release/src/base.c&q=PyCode_Addr2Line), which is replaced by the tb_lineno field. So we may be able to deprecate PyCode_Addr2Line entirely for external use.
* PyCode_NewEmpty:Jeffrey Yasskin2009-05-082-0/+51
| | | | | | | | Most uses of PyCode_New found by http://www.google.com/codesearch?q=PyCode_New are trying to build an empty code object, usually to put it in a dummy frame object. This patch adds a PyCode_NewEmpty wrapper which lets the user specify just the filename, function name, and first line number, instead of also requiring lots of code internals.
* Issue #5920: Changed format.__float__ and complex.__float__ to use a ↵Eric Smith2009-05-051-4/+4
| | | | precision of 12 when using the empty presentation type. This more closely matches str()'s behavior and reduces surprises when adding alignment flags to an empty format string. Patch by Mark Dickinson.
* #5840: dont claim we dont support TLS.Georg Brandl2009-04-271-4/+3
|
* Demote warnings to notices where appropriate, following the goal that as few ↵Georg Brandl2009-04-271-1/+1
| | | | | | "red box" warnings should clutter the docs as possible. Part 1: stuff that gets merged to Py3k.
* Note that the caller is resposible for freeing the result of ↵Eric Smith2009-04-261-1/+2
| | | | PyOS_double_to_string.
* Mostly formatting nits, and "and-ed together" -> "or-ed together" flags.Georg Brandl2009-04-261-22/+23
|
* Issue #5835, deprecate PyOS_ascii_formatd.Eric Smith2009-04-251-0/+35
| | | | | | If anyone wants to clean up the documentation, feel free. It's my first documentation foray, and it's not that great. Will port to py3k with a different strategy.
* Issue #4129: document int -> Py_ssize_t changes.Jeroen Ruigrok van der Werven2009-04-251-0/+133
|
* Issue #4129: field changed from int to Py_ssize_t.Jeroen Ruigrok van der Werven2009-04-251-0/+4
|
* Issue #4129: more int -> Py_ssize_t documentation.Jeroen Ruigrok van der Werven2009-04-251-0/+12
|
* Issue #4129: more int -> Py_ssize_t documentation.Jeroen Ruigrok van der Werven2009-04-251-0/+16
|
* Issue #4129: int -> Py_ssize_t documentation.Jeroen Ruigrok van der Werven2009-04-251-0/+8
|
* Issue #4129: int -> Py_ssize_t documentation.Jeroen Ruigrok van der Werven2009-04-251-0/+12
|
* Reformat prior to editing.Jeroen Ruigrok van der Werven2009-04-251-12/+13
|
* Issue #4129: int -> Py_ssize_t documentation.Jeroen Ruigrok van der Werven2009-04-251-0/+4
|
* Reformat prior to editing.Jeroen Ruigrok van der Werven2009-04-251-32/+34
|
* Since it's a macro, actually refer to it as such instead of function.Jeroen Ruigrok van der Werven2009-04-251-6/+6
|
* Issue #4129: Add a versionchanged notice for a few forgotten entries.Jeroen Ruigrok van der Werven2009-04-251-0/+12
|
* Reformat, since I've been busy here anyway.Jeroen Ruigrok van der Werven2009-04-251-34/+37
|
* Issue #4129: Documentation notes for int -> Py_ssize_t changes.Jeroen Ruigrok van der Werven2009-04-251-0/+8
|
* Issue #4129: More documentation pointers about int -> Py_ssize_t.Jeroen Ruigrok van der Werven2009-04-251-1/+9
| | | | | | Also fix up the documentation for PyObject_GC_Resize(). It seems that since it first got documented, the documentation was actually for _PyObject_GC_Resize().
* Reformat prior to editing.Jeroen Ruigrok van der Werven2009-04-251-35/+39
|
generated by cgit v0.12 at 2025-12-27 13:11:38 (GMT)