diff options
author | Georg Brandl <georg@python.org> | 2009-07-26 14:19:57 (GMT) |
---|---|---|
committer | Georg Brandl <georg@python.org> | 2009-07-26 14:19:57 (GMT) |
commit | 9fa61bb37d68225c827aa7809382ea701c264db5 (patch) | |
tree | 7a086015c9e4ecbb02ad38895cf7dcc4cb7be605 /Doc/library/cgi.rst | |
parent | 74f8fc0b1bccc971a3055b2e364c4a2db5123d50 (diff) | |
download | cpython-9fa61bb37d68225c827aa7809382ea701c264db5.zip cpython-9fa61bb37d68225c827aa7809382ea701c264db5.tar.gz cpython-9fa61bb37d68225c827aa7809382ea701c264db5.tar.bz2 |
#6577: fix (hopefully) all links to builtin instead of module/class-specific objects.
Diffstat (limited to 'Doc/library/cgi.rst')
-rw-r--r-- | Doc/library/cgi.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/Doc/library/cgi.rst b/Doc/library/cgi.rst index 58222ea..138f808 100644 --- a/Doc/library/cgi.rst +++ b/Doc/library/cgi.rst @@ -136,8 +136,8 @@ commas:: If a field represents an uploaded file, accessing the value via the :attr:`value` attribute or the :func:`getvalue` method reads the entire file in memory as a string. This may not be what you want. You can test for an uploaded -file by testing either the :attr:`filename` attribute or the :attr:`file` -attribute. You can then read the data at leisure from the :attr:`file` +file by testing either the :attr:`filename` attribute or the :attr:`!file` +attribute. You can then read the data at leisure from the :attr:`!file` attribute:: fileitem = form["userfile"] @@ -157,7 +157,7 @@ field will be set to the value -1. The file upload draft standard entertains the possibility of uploading multiple files from one field (using a recursive :mimetype:`multipart/\*` encoding). When this occurs, the item will be a dictionary-like :class:`FieldStorage` item. -This can be determined by testing its :attr:`type` attribute, which should be +This can be determined by testing its :attr:`!type` attribute, which should be :mimetype:`multipart/form-data` (or perhaps another MIME type matching :mimetype:`multipart/\*`). In this case, it can be iterated over recursively just like the top-level form object. @@ -165,7 +165,7 @@ just like the top-level form object. When a form is submitted in the "old" format (as the query string or as a single data part of type :mimetype:`application/x-www-form-urlencoded`), the items will actually be instances of the class :class:`MiniFieldStorage`. In this case, the -:attr:`list`, :attr:`file`, and :attr:`filename` attributes are always ``None``. +:attr:`!list`, :attr:`!file`, and :attr:`filename` attributes are always ``None``. A form submitted via POST that also has a query string will contain both :class:`FieldStorage` and :class:`MiniFieldStorage` items. |