summaryrefslogtreecommitdiffstats
path: root/Doc/c-api
Commit message (Collapse)AuthorAgeFilesLines
* #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
|
* Since I edited this file, reformat for future edits.Jeroen Ruigrok van der Werven2009-04-251-68/+72
|
* Reference to an int type, whereas it's a Py_ssize_t as the synopsis states.Jeroen Ruigrok van der Werven2009-04-251-3/+3
|
* Reformat prior to editing.Jeroen Ruigrok van der Werven2009-04-251-41/+47
|
* Issue #4129: Document more int -> Py_ssize_t changes.Jeroen Ruigrok van der Werven2009-04-251-0/+11
|
* Reformat prior to editing.Jeroen Ruigrok van der Werven2009-04-251-17/+18
|
* Issue #4129: Belatedly document which C API functions had their argument(s) orJeroen Ruigrok van der Werven2009-04-2513-5/+171
| | | | | return type changed from int or int * to Py_ssize_t or Py_ssize_t * as this might cause problems on 64-bit platforms.
* Reformat paragraph.Jeroen Ruigrok van der Werven2009-04-251-10/+10
|
* The type for ppos has been Py_ssize_t since 2.5, reflect this in theJeroen Ruigrok van der Werven2009-04-251-1/+1
| | | | documentation.
* Reformat prior to editing.Jeroen Ruigrok van der Werven2009-04-251-50/+55
|
* Reformat file prior to editing.Jeroen Ruigrok van der Werven2009-04-251-239/+252
|
* Rewrite a sentence to be more in line with the rest of the documentation withJeroen Ruigrok van der Werven2009-04-251-7/+7
| | | | regard to person and audience.
* First attempt to document PyObject_HEAD_INIT and PyVarObject_HEAD_INIT.Jeroen Ruigrok van der Werven2009-04-251-1/+18
|
* Reformat prior to expanding.Jeroen Ruigrok van der Werven2009-04-251-57/+63
|
* Remove redundant backtick.Georg Brandl2009-04-081-1/+1
|
* #5298: clarify docs about GIL by using more consistent wording.Georg Brandl2009-04-051-78/+79
|
* Fix 'the the' duplicationAndrew M. Kuchling2009-04-031-1/+1
|
generated by cgit v0.12 at 2024-10-24 09:23:53 (GMT)