ea7120c7c1
Py_SetPythonHome uses static storage #6913
2009-09-15 03:36:26 +00:00
eb4781c279
#6821 : fix signature of PyBuffer_Release().
2009-09-02 20:37:16 +00:00
4a46e1c4b3
#6658 : fix two typos.
2009-08-06 17:43:55 +00:00
019e8dd7fc
#6336 : Add nb_divide.
2009-07-29 16:32:30 +00:00
d7d4fd7336
builtin -> built-in.
2009-07-26 14:37:28 +00:00
36b30b5a4b
Dont put "void" in signature for nullary functions.
2009-07-24 16:46:38 +00:00
f0b1733574
Fix arg types of et#.
2009-07-24 16:28:38 +00:00
3405cbcf06
Fix style.
2009-07-11 10:12:36 +00:00
476849c185
#6255 : document PyInt_FromSize_t.
2009-06-17 09:43:31 +00:00
3a5971c237
#5967 : note that the C slicing APIs do not support negative indices.
2009-06-04 10:15:57 +00:00
d7ead0c23f
fix signature
2009-05-31 00:42:42 +00:00
6a4689887c
Fix some more small markup problems.
2009-05-30 10:33:23 +00:00
f7f858d141
Issue 5954, PyFrame_GetLineNumber:
...
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.
2009-05-08 22:23:21 +00:00
1aa4700234
PyCode_NewEmpty:
...
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.
2009-05-08 21:51:06 +00:00
a985a3aee4
Issue #5920 : Changed format.__float__ and complex.__float__ to use a 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.
2009-05-05 18:26:08 +00:00
2622b549d7
#5840 : dont claim we dont support TLS.
2009-04-27 17:09:53 +00:00
16a57f6a34
Demote warnings to notices where appropriate, following the goal that as few "red box" warnings
...
should clutter the docs as possible. Part 1: stuff that gets merged to Py3k.
2009-04-27 15:29:09 +00:00
f254aab098
Note that the caller is resposible for freeing the result of PyOS_double_to_string.
2009-04-26 10:05:11 +00:00
afb0d6ef39
Mostly formatting nits, and "and-ed together" -> "or-ed together" flags.
2009-04-26 06:01:04 +00:00
068f06568b
Issue #5835 , deprecate PyOS_ascii_formatd.
...
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.
2009-04-25 21:40:15 +00:00
dfcffd4044
Issue #4129 : document int -> Py_ssize_t changes.
2009-04-25 21:16:05 +00:00
436f1a2e0d
Issue #4129 : field changed from int to Py_ssize_t.
2009-04-25 21:02:34 +00:00
acc73b74b8
Issue #4129 : more int -> Py_ssize_t documentation.
2009-04-25 20:58:35 +00:00
7b3750c8d8
Issue #4129 : more int -> Py_ssize_t documentation.
2009-04-25 20:55:39 +00:00
36378711b7
Issue #4129 : int -> Py_ssize_t documentation.
2009-04-25 20:50:27 +00:00
9594c2c5aa
Issue #4129 : int -> Py_ssize_t documentation.
2009-04-25 20:44:58 +00:00
27d51f1a51
Reformat prior to editing.
2009-04-25 20:43:30 +00:00
be82d2f16f
Issue #4129 : int -> Py_ssize_t documentation.
2009-04-25 20:41:40 +00:00
a4c03abb9e
Reformat prior to editing.
2009-04-25 20:40:10 +00:00
9e03cee97c
Since it's a macro, actually refer to it as such instead of function.
2009-04-25 20:37:39 +00:00
af15b41547
Issue #4129 : Add a versionchanged notice for a few forgotten entries.
2009-04-25 19:54:34 +00:00
de0fed10c8
Reformat, since I've been busy here anyway.
2009-04-25 19:49:05 +00:00
2aa7840f54
Issue #4129 : Documentation notes for int -> Py_ssize_t changes.
2009-04-25 19:46:19 +00:00
691f5f17ee
Issue #4129 : More documentation pointers about int -> Py_ssize_t.
...
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().
2009-04-25 19:44:55 +00:00
3537124058
Reformat prior to editing.
2009-04-25 19:10:52 +00:00
1ae8c88030
Since I edited this file, reformat for future edits.
2009-04-25 19:04:15 +00:00
c2aa7b8a0a
Reference to an int type, whereas it's a Py_ssize_t as the synopsis states.
2009-04-25 18:57:32 +00:00
28c81e0bb5
Reformat prior to editing.
2009-04-25 18:53:48 +00:00
2391918f3e
Issue #4129 : Document more int -> Py_ssize_t changes.
2009-04-25 18:46:03 +00:00
84441cc3d5
Reformat prior to editing.
2009-04-25 18:31:20 +00:00
089c5cdd09
Issue #4129 : Belatedly document which C API functions had their argument(s) or
...
return type changed from int or int * to Py_ssize_t or Py_ssize_t * as this
might cause problems on 64-bit platforms.
2009-04-25 17:59:03 +00:00
6f1d543133
Reformat paragraph.
2009-04-25 14:28:02 +00:00
325a997efb
The type for ppos has been Py_ssize_t since 2.5, reflect this in the
...
documentation.
2009-04-25 14:27:00 +00:00
c42c099436
Reformat prior to editing.
2009-04-25 14:24:30 +00:00
140d9d673e
Reformat file prior to editing.
2009-04-25 13:58:58 +00:00
2dcf46ee2c
Rewrite a sentence to be more in line with the rest of the documentation with
...
regard to person and audience.
2009-04-25 13:07:40 +00:00
162641a24c
First attempt to document PyObject_HEAD_INIT and PyVarObject_HEAD_INIT.
2009-04-25 11:59:09 +00:00
bc25bf9d3e
Reformat prior to expanding.
2009-04-25 11:15:06 +00:00
6cb1ff32c2
Remove redundant backtick.
2009-04-08 16:36:39 +00:00
1ede0d670f
#5298 : clarify docs about GIL by using more consistent wording.
2009-04-05 17:17:42 +00:00
Benjamin Peterson
Georg Brandl
Jeffrey Yasskin
Eric Smith
Jeroen Ruigrok van der Werven