From 304500cd10272501a2f612bc6a7b079eca52e56f Mon Sep 17 00:00:00 2001 From: "Andrew M. Kuchling" Date: Sat, 8 May 2010 13:29:46 +0000 Subject: [PATCH] Markup fixes --- Doc/whatsnew/2.7.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Doc/whatsnew/2.7.rst b/Doc/whatsnew/2.7.rst index 1d294476282..67c02185a88 100644 --- a/Doc/whatsnew/2.7.rst +++ b/Doc/whatsnew/2.7.rst @@ -1346,7 +1346,7 @@ changes, or look through the Subversion logs for all the details. will execute the code at a provided *path* argument. *path* can be the path of a Python source file (:file:`example.py`), a compiled bytecode file (:file:`example.pyc`), a directory - (:file:`./package/'), or a zip archive (:file:`example.zip`). If a + (:file:`./package/`), or a zip archive (:file:`example.zip`). If a directory or zip path is provided, it will be added to the front of ``sys.path`` and the module :mod:`__main__` will be imported. It's expected that the directory or zip contains a :file:`__main__.py`; @@ -2132,7 +2132,7 @@ Capsules Python 3.1 adds a new C datatype, :ctype:`PyCapsule`, for providing a C API to an extension module. A capsule is essentially the holder for a C ``void *`` pointer, and is bound to a module attribute; for -example, the :mod:`socket` module's API is exposed as ``socket.CAPI`, +example, the :mod:`socket` module's API is exposed as ``socket.CAPI``, and :mod:`unicodedata` calls it ``ucnhash_CAPI``. Other extensions can import the module, access its dictionary to get the capsule object, and then get the ``void *`` pointer, which will usually point