Fix a few scoping issues with versionadded/versionchanged directives.

This commit is contained in:
Georg Brandl 2014-03-24 09:06:18 +01:00
parent 645d3b7655
commit df48b97855
12 changed files with 38 additions and 32 deletions

View file

@ -247,7 +247,7 @@ in various ways. There is a separate error indicator for each thread.
filename object, for raising errors when a function that takes two filenames
fails.
.. versionadded:: 3.4
.. versionadded:: 3.4
.. c:function:: PyObject* PyErr_SetFromErrnoWithFilename(PyObject *type, const char *filename)
@ -295,7 +295,7 @@ in various ways. There is a separate error indicator for each thread.
but accepts a second filename object.
Availability: Windows.
.. versionadded:: 3.4
.. versionadded:: 3.4
.. c:function:: PyObject* PyErr_SetExcFromWindowsErrWithFilename(PyObject *type, int ierr, const char *filename)
@ -321,7 +321,7 @@ in various ways. There is a separate error indicator for each thread.
attributes, which make the exception printing subsystem think the exception
is a :exc:`SyntaxError`.
.. versionadded:: 3.4
.. versionadded:: 3.4
.. c:function:: void PyErr_SyntaxLocationEx(char *filename, int lineno, int col_offset)
@ -329,7 +329,7 @@ in various ways. There is a separate error indicator for each thread.
Like :c:func:`PyErr_SyntaxLocationObject`, but *filename* is a byte string
decoded from the filesystem encoding (:func:`os.fsdecode`).
.. versionadded:: 3.2
.. versionadded:: 3.2
.. c:function:: void PyErr_SyntaxLocation(char *filename, int lineno)

View file

@ -364,6 +364,7 @@ attribute is considered sufficient for this determination.
.. versionadded:: 3.4
.. c:function:: PyObject* PyObject_GetItem(PyObject *o, PyObject *key)
Return element of *o* corresponding to the object *key* or *NULL* on failure.