You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

505 lines
19 KiB

14 years ago
15 years ago
15 years ago
Merged revisions 74074,74077,74111,74188,74192-74193,74200,74252-74253,74258-74261 via svnmerge from svn+ssh://pythondev@svn.python.org/python/trunk ........ r74074 | georg.brandl | 2009-07-18 05:03:10 -0400 (Sat, 18 Jul 2009) | 1 line #6513: fix example code: warning categories are classes, not instances. ........ r74077 | georg.brandl | 2009-07-18 05:43:40 -0400 (Sat, 18 Jul 2009) | 1 line #6489: fix an ambiguity in getiterator() documentation. ........ r74111 | benjamin.peterson | 2009-07-20 09:30:10 -0400 (Mon, 20 Jul 2009) | 1 line remove docs for deprecated -p option ........ r74188 | benjamin.peterson | 2009-07-23 10:25:31 -0400 (Thu, 23 Jul 2009) | 1 line use bools ........ r74192 | georg.brandl | 2009-07-24 12:28:38 -0400 (Fri, 24 Jul 2009) | 1 line Fix arg types of et#. ........ r74193 | georg.brandl | 2009-07-24 12:46:38 -0400 (Fri, 24 Jul 2009) | 1 line Dont put "void" in signature for nullary functions. ........ r74200 | georg.brandl | 2009-07-25 09:02:15 -0400 (Sat, 25 Jul 2009) | 1 line #6571: add index entries for more operators. ........ r74252 | georg.brandl | 2009-07-29 12:06:31 -0400 (Wed, 29 Jul 2009) | 1 line #6593: fix link targets. ........ r74253 | georg.brandl | 2009-07-29 12:09:17 -0400 (Wed, 29 Jul 2009) | 1 line #6591: add reference to ioctl in fcntl module for platforms other than Windows. ........ r74258 | georg.brandl | 2009-07-29 12:57:05 -0400 (Wed, 29 Jul 2009) | 1 line Add a link to readline, and mention IPython and bpython. ........ r74259 | georg.brandl | 2009-07-29 13:07:21 -0400 (Wed, 29 Jul 2009) | 1 line Fix some markup and small factual glitches found by M. Markert. ........ r74260 | georg.brandl | 2009-07-29 13:15:20 -0400 (Wed, 29 Jul 2009) | 1 line Fix a few markup glitches. ........ r74261 | georg.brandl | 2009-07-29 13:50:25 -0400 (Wed, 29 Jul 2009) | 1 line Rewrite the section about classes a bit; mostly tidbits, and a larger update to the section about "private" variables to reflect the Pythonic consensus better. ........
17 years ago
Merged revisions 74074,74077,74111,74188,74192-74193,74200,74252-74253,74258-74261 via svnmerge from svn+ssh://pythondev@svn.python.org/python/trunk ........ r74074 | georg.brandl | 2009-07-18 05:03:10 -0400 (Sat, 18 Jul 2009) | 1 line #6513: fix example code: warning categories are classes, not instances. ........ r74077 | georg.brandl | 2009-07-18 05:43:40 -0400 (Sat, 18 Jul 2009) | 1 line #6489: fix an ambiguity in getiterator() documentation. ........ r74111 | benjamin.peterson | 2009-07-20 09:30:10 -0400 (Mon, 20 Jul 2009) | 1 line remove docs for deprecated -p option ........ r74188 | benjamin.peterson | 2009-07-23 10:25:31 -0400 (Thu, 23 Jul 2009) | 1 line use bools ........ r74192 | georg.brandl | 2009-07-24 12:28:38 -0400 (Fri, 24 Jul 2009) | 1 line Fix arg types of et#. ........ r74193 | georg.brandl | 2009-07-24 12:46:38 -0400 (Fri, 24 Jul 2009) | 1 line Dont put "void" in signature for nullary functions. ........ r74200 | georg.brandl | 2009-07-25 09:02:15 -0400 (Sat, 25 Jul 2009) | 1 line #6571: add index entries for more operators. ........ r74252 | georg.brandl | 2009-07-29 12:06:31 -0400 (Wed, 29 Jul 2009) | 1 line #6593: fix link targets. ........ r74253 | georg.brandl | 2009-07-29 12:09:17 -0400 (Wed, 29 Jul 2009) | 1 line #6591: add reference to ioctl in fcntl module for platforms other than Windows. ........ r74258 | georg.brandl | 2009-07-29 12:57:05 -0400 (Wed, 29 Jul 2009) | 1 line Add a link to readline, and mention IPython and bpython. ........ r74259 | georg.brandl | 2009-07-29 13:07:21 -0400 (Wed, 29 Jul 2009) | 1 line Fix some markup and small factual glitches found by M. Markert. ........ r74260 | georg.brandl | 2009-07-29 13:15:20 -0400 (Wed, 29 Jul 2009) | 1 line Fix a few markup glitches. ........ r74261 | georg.brandl | 2009-07-29 13:50:25 -0400 (Wed, 29 Jul 2009) | 1 line Rewrite the section about classes a bit; mostly tidbits, and a larger update to the section about "private" variables to reflect the Pythonic consensus better. ........
17 years ago
Merged revisions 74074,74077,74111,74188,74192-74193,74200,74252-74253,74258-74261 via svnmerge from svn+ssh://pythondev@svn.python.org/python/trunk ........ r74074 | georg.brandl | 2009-07-18 05:03:10 -0400 (Sat, 18 Jul 2009) | 1 line #6513: fix example code: warning categories are classes, not instances. ........ r74077 | georg.brandl | 2009-07-18 05:43:40 -0400 (Sat, 18 Jul 2009) | 1 line #6489: fix an ambiguity in getiterator() documentation. ........ r74111 | benjamin.peterson | 2009-07-20 09:30:10 -0400 (Mon, 20 Jul 2009) | 1 line remove docs for deprecated -p option ........ r74188 | benjamin.peterson | 2009-07-23 10:25:31 -0400 (Thu, 23 Jul 2009) | 1 line use bools ........ r74192 | georg.brandl | 2009-07-24 12:28:38 -0400 (Fri, 24 Jul 2009) | 1 line Fix arg types of et#. ........ r74193 | georg.brandl | 2009-07-24 12:46:38 -0400 (Fri, 24 Jul 2009) | 1 line Dont put "void" in signature for nullary functions. ........ r74200 | georg.brandl | 2009-07-25 09:02:15 -0400 (Sat, 25 Jul 2009) | 1 line #6571: add index entries for more operators. ........ r74252 | georg.brandl | 2009-07-29 12:06:31 -0400 (Wed, 29 Jul 2009) | 1 line #6593: fix link targets. ........ r74253 | georg.brandl | 2009-07-29 12:09:17 -0400 (Wed, 29 Jul 2009) | 1 line #6591: add reference to ioctl in fcntl module for platforms other than Windows. ........ r74258 | georg.brandl | 2009-07-29 12:57:05 -0400 (Wed, 29 Jul 2009) | 1 line Add a link to readline, and mention IPython and bpython. ........ r74259 | georg.brandl | 2009-07-29 13:07:21 -0400 (Wed, 29 Jul 2009) | 1 line Fix some markup and small factual glitches found by M. Markert. ........ r74260 | georg.brandl | 2009-07-29 13:15:20 -0400 (Wed, 29 Jul 2009) | 1 line Fix a few markup glitches. ........ r74261 | georg.brandl | 2009-07-29 13:50:25 -0400 (Wed, 29 Jul 2009) | 1 line Rewrite the section about classes a bit; mostly tidbits, and a larger update to the section about "private" variables to reflect the Pythonic consensus better. ........
17 years ago
  1. .. _tut-io:
  2. ****************
  3. Input and Output
  4. ****************
  5. There are several ways to present the output of a program; data can be printed
  6. in a human-readable form, or written to a file for future use. This chapter will
  7. discuss some of the possibilities.
  8. .. _tut-formatting:
  9. Fancier Output Formatting
  10. =========================
  11. So far we've encountered two ways of writing values: *expression statements* and
  12. the :func:`print` function. (A third way is using the :meth:`write` method
  13. of file objects; the standard output file can be referenced as ``sys.stdout``.
  14. See the Library Reference for more information on this.)
  15. Often you'll want more control over the formatting of your output than simply
  16. printing space-separated values. There are several ways to format output.
  17. * To use :ref:`formatted string literals <tut-f-strings>`, begin a string
  18. with ``f`` or ``F`` before the opening quotation mark or triple quotation mark.
  19. Inside this string, you can write a Python expression between ``{`` and ``}``
  20. characters that can refer to variables or literal values.
  21. ::
  22. >>> year = 2016
  23. >>> event = 'Referendum'
  24. >>> f'Results of the {year} {event}'
  25. 'Results of the 2016 Referendum'
  26. * The :meth:`str.format` method of strings requires more manual
  27. effort. You'll still use ``{`` and ``}`` to mark where a variable
  28. will be substituted and can provide detailed formatting directives,
  29. but you'll also need to provide the information to be formatted.
  30. ::
  31. >>> yes_votes = 42_572_654
  32. >>> no_votes = 43_132_495
  33. >>> percentage = yes_votes / (yes_votes + no_votes)
  34. >>> '{:-9} YES votes {:2.2%}'.format(yes_votes, percentage)
  35. ' 42572654 YES votes 49.67%'
  36. * Finally, you can do all the string handling yourself by using string slicing and
  37. concatenation operations to create any layout you can imagine. The
  38. string type has some methods that perform useful operations for padding
  39. strings to a given column width.
  40. When you don't need fancy output but just want a quick display of some
  41. variables for debugging purposes, you can convert any value to a string with
  42. the :func:`repr` or :func:`str` functions.
  43. The :func:`str` function is meant to return representations of values which are
  44. fairly human-readable, while :func:`repr` is meant to generate representations
  45. which can be read by the interpreter (or will force a :exc:`SyntaxError` if
  46. there is no equivalent syntax). For objects which don't have a particular
  47. representation for human consumption, :func:`str` will return the same value as
  48. :func:`repr`. Many values, such as numbers or structures like lists and
  49. dictionaries, have the same representation using either function. Strings, in
  50. particular, have two distinct representations.
  51. Some examples::
  52. >>> s = 'Hello, world.'
  53. >>> str(s)
  54. 'Hello, world.'
  55. >>> repr(s)
  56. "'Hello, world.'"
  57. >>> str(1/7)
  58. '0.14285714285714285'
  59. >>> x = 10 * 3.25
  60. >>> y = 200 * 200
  61. >>> s = 'The value of x is ' + repr(x) + ', and y is ' + repr(y) + '...'
  62. >>> print(s)
  63. The value of x is 32.5, and y is 40000...
  64. >>> # The repr() of a string adds string quotes and backslashes:
  65. ... hello = 'hello, world\n'
  66. >>> hellos = repr(hello)
  67. >>> print(hellos)
  68. 'hello, world\n'
  69. >>> # The argument to repr() may be any Python object:
  70. ... repr((x, y, ('spam', 'eggs')))
  71. "(32.5, 40000, ('spam', 'eggs'))"
  72. The :mod:`string` module contains a :class:`~string.Template` class that offers
  73. yet another way to substitute values into strings, using placeholders like
  74. ``$x`` and replacing them with values from a dictionary, but offers much less
  75. control of the formatting.
  76. .. _tut-f-strings:
  77. Formatted String Literals
  78. -------------------------
  79. :ref:`Formatted string literals <f-strings>` (also called f-strings for
  80. short) let you include the value of Python expressions inside a string by
  81. prefixing the string with ``f`` or ``F`` and writing expressions as
  82. ``{expression}``.
  83. An optional format specifier can follow the expression. This allows greater
  84. control over how the value is formatted. The following example rounds pi to
  85. three places after the decimal::
  86. >>> import math
  87. >>> print(f'The value of pi is approximately {math.pi:.3f}.')
  88. The value of pi is approximately 3.142.
  89. Passing an integer after the ``':'`` will cause that field to be a minimum
  90. number of characters wide. This is useful for making columns line up. ::
  91. >>> table = {'Sjoerd': 4127, 'Jack': 4098, 'Dcab': 7678}
  92. >>> for name, phone in table.items():
  93. ... print(f'{name:10} ==> {phone:10d}')
  94. ...
  95. Sjoerd ==> 4127
  96. Jack ==> 4098
  97. Dcab ==> 7678
  98. Other modifiers can be used to convert the value before it is formatted.
  99. ``'!a'`` applies :func:`ascii`, ``'!s'`` applies :func:`str`, and ``'!r'``
  100. applies :func:`repr`::
  101. >>> animals = 'eels'
  102. >>> print(f'My hovercraft is full of {animals}.')
  103. My hovercraft is full of eels.
  104. >>> print(f'My hovercraft is full of {animals!r}.')
  105. My hovercraft is full of 'eels'.
  106. For a reference on these format specifications, see
  107. the reference guide for the :ref:`formatspec`.
  108. .. _tut-string-format:
  109. The String format() Method
  110. --------------------------
  111. Basic usage of the :meth:`str.format` method looks like this::
  112. >>> print('We are the {} who say "{}!"'.format('knights', 'Ni'))
  113. We are the knights who say "Ni!"
  114. The brackets and characters within them (called format fields) are replaced with
  115. the objects passed into the :meth:`str.format` method. A number in the
  116. brackets can be used to refer to the position of the object passed into the
  117. :meth:`str.format` method. ::
  118. >>> print('{0} and {1}'.format('spam', 'eggs'))
  119. spam and eggs
  120. >>> print('{1} and {0}'.format('spam', 'eggs'))
  121. eggs and spam
  122. If keyword arguments are used in the :meth:`str.format` method, their values
  123. are referred to by using the name of the argument. ::
  124. >>> print('This {food} is {adjective}.'.format(
  125. ... food='spam', adjective='absolutely horrible'))
  126. This spam is absolutely horrible.
  127. Positional and keyword arguments can be arbitrarily combined::
  128. >>> print('The story of {0}, {1}, and {other}.'.format('Bill', 'Manfred',
  129. other='Georg'))
  130. The story of Bill, Manfred, and Georg.
  131. If you have a really long format string that you don't want to split up, it
  132. would be nice if you could reference the variables to be formatted by name
  133. instead of by position. This can be done by simply passing the dict and using
  134. square brackets ``'[]'`` to access the keys ::
  135. >>> table = {'Sjoerd': 4127, 'Jack': 4098, 'Dcab': 8637678}
  136. >>> print('Jack: {0[Jack]:d}; Sjoerd: {0[Sjoerd]:d}; '
  137. ... 'Dcab: {0[Dcab]:d}'.format(table))
  138. Jack: 4098; Sjoerd: 4127; Dcab: 8637678
  139. This could also be done by passing the table as keyword arguments with the '**'
  140. notation. ::
  141. >>> table = {'Sjoerd': 4127, 'Jack': 4098, 'Dcab': 8637678}
  142. >>> print('Jack: {Jack:d}; Sjoerd: {Sjoerd:d}; Dcab: {Dcab:d}'.format(**table))
  143. Jack: 4098; Sjoerd: 4127; Dcab: 8637678
  144. This is particularly useful in combination with the built-in function
  145. :func:`vars`, which returns a dictionary containing all local variables.
  146. As an example, the following lines produce a tidily-aligned
  147. set of columns giving integers and their squares and cubes::
  148. >>> for x in range(1, 11):
  149. ... print('{0:2d} {1:3d} {2:4d}'.format(x, x*x, x*x*x))
  150. ...
  151. 1 1 1
  152. 2 4 8
  153. 3 9 27
  154. 4 16 64
  155. 5 25 125
  156. 6 36 216
  157. 7 49 343
  158. 8 64 512
  159. 9 81 729
  160. 10 100 1000
  161. For a complete overview of string formatting with :meth:`str.format`, see
  162. :ref:`formatstrings`.
  163. Manual String Formatting
  164. ------------------------
  165. Here's the same table of squares and cubes, formatted manually::
  166. >>> for x in range(1, 11):
  167. ... print(repr(x).rjust(2), repr(x*x).rjust(3), end=' ')
  168. ... # Note use of 'end' on previous line
  169. ... print(repr(x*x*x).rjust(4))
  170. ...
  171. 1 1 1
  172. 2 4 8
  173. 3 9 27
  174. 4 16 64
  175. 5 25 125
  176. 6 36 216
  177. 7 49 343
  178. 8 64 512
  179. 9 81 729
  180. 10 100 1000
  181. (Note that the one space between each column was added by the
  182. way :func:`print` works: it always adds spaces between its arguments.)
  183. The :meth:`str.rjust` method of string objects right-justifies a string in a
  184. field of a given width by padding it with spaces on the left. There are
  185. similar methods :meth:`str.ljust` and :meth:`str.center`. These methods do
  186. not write anything, they just return a new string. If the input string is too
  187. long, they don't truncate it, but return it unchanged; this will mess up your
  188. column lay-out but that's usually better than the alternative, which would be
  189. lying about a value. (If you really want truncation you can always add a
  190. slice operation, as in ``x.ljust(n)[:n]``.)
  191. There is another method, :meth:`str.zfill`, which pads a numeric string on the
  192. left with zeros. It understands about plus and minus signs::
  193. >>> '12'.zfill(5)
  194. '00012'
  195. >>> '-3.14'.zfill(7)
  196. '-003.14'
  197. >>> '3.14159265359'.zfill(5)
  198. '3.14159265359'
  199. Old string formatting
  200. ---------------------
  201. The ``%`` operator can also be used for string formatting. It interprets the
  202. left argument much like a :c:func:`sprintf`\ -style format string to be applied
  203. to the right argument, and returns the string resulting from this formatting
  204. operation. For example::
  205. >>> import math
  206. >>> print('The value of pi is approximately %5.3f.' % math.pi)
  207. The value of pi is approximately 3.142.
  208. More information can be found in the :ref:`old-string-formatting` section.
  209. .. _tut-files:
  210. Reading and Writing Files
  211. =========================
  212. .. index::
  213. builtin: open
  214. object: file
  215. :func:`open` returns a :term:`file object`, and is most commonly used with
  216. two arguments: ``open(filename, mode)``.
  217. ::
  218. >>> f = open('workfile', 'w')
  219. .. XXX str(f) is <io.TextIOWrapper object at 0x82e8dc4>
  220. >>> print(f)
  221. <open file 'workfile', mode 'w' at 80a0960>
  222. The first argument is a string containing the filename. The second argument is
  223. another string containing a few characters describing the way in which the file
  224. will be used. *mode* can be ``'r'`` when the file will only be read, ``'w'``
  225. for only writing (an existing file with the same name will be erased), and
  226. ``'a'`` opens the file for appending; any data written to the file is
  227. automatically added to the end. ``'r+'`` opens the file for both reading and
  228. writing. The *mode* argument is optional; ``'r'`` will be assumed if it's
  229. omitted.
  230. Normally, files are opened in :dfn:`text mode`, that means, you read and write
  231. strings from and to the file, which are encoded in a specific encoding. If
  232. encoding is not specified, the default is platform dependent (see
  233. :func:`open`). ``'b'`` appended to the mode opens the file in
  234. :dfn:`binary mode`: now the data is read and written in the form of bytes
  235. objects. This mode should be used for all files that don't contain text.
  236. In text mode, the default when reading is to convert platform-specific line
  237. endings (``\n`` on Unix, ``\r\n`` on Windows) to just ``\n``. When writing in
  238. text mode, the default is to convert occurrences of ``\n`` back to
  239. platform-specific line endings. This behind-the-scenes modification
  240. to file data is fine for text files, but will corrupt binary data like that in
  241. :file:`JPEG` or :file:`EXE` files. Be very careful to use binary mode when
  242. reading and writing such files.
  243. It is good practice to use the :keyword:`with` keyword when dealing
  244. with file objects. The advantage is that the file is properly closed
  245. after its suite finishes, even if an exception is raised at some
  246. point. Using :keyword:`!with` is also much shorter than writing
  247. equivalent :keyword:`try`\ -\ :keyword:`finally` blocks::
  248. >>> with open('workfile') as f:
  249. ... read_data = f.read()
  250. >>> # We can check that the file has been automatically closed.
  251. >>> f.closed
  252. True
  253. If you're not using the :keyword:`with` keyword, then you should call
  254. ``f.close()`` to close the file and immediately free up any system
  255. resources used by it. If you don't explicitly close a file, Python's
  256. garbage collector will eventually destroy the object and close the
  257. open file for you, but the file may stay open for a while. Another
  258. risk is that different Python implementations will do this clean-up at
  259. different times.
  260. After a file object is closed, either by a :keyword:`with` statement
  261. or by calling ``f.close()``, attempts to use the file object will
  262. automatically fail. ::
  263. >>> f.close()
  264. >>> f.read()
  265. Traceback (most recent call last):
  266. File "<stdin>", line 1, in <module>
  267. ValueError: I/O operation on closed file.
  268. .. _tut-filemethods:
  269. Methods of File Objects
  270. -----------------------
  271. The rest of the examples in this section will assume that a file object called
  272. ``f`` has already been created.
  273. To read a file's contents, call ``f.read(size)``, which reads some quantity of
  274. data and returns it as a string (in text mode) or bytes object (in binary mode).
  275. *size* is an optional numeric argument. When *size* is omitted or negative, the
  276. entire contents of the file will be read and returned; it's your problem if the
  277. file is twice as large as your machine's memory. Otherwise, at most *size*
  278. characters (in text mode) or *size* bytes (in binary mode) are read and returned.
  279. If the end of the file has been reached, ``f.read()`` will return an empty
  280. string (``''``). ::
  281. >>> f.read()
  282. 'This is the entire file.\n'
  283. >>> f.read()
  284. ''
  285. ``f.readline()`` reads a single line from the file; a newline character (``\n``)
  286. is left at the end of the string, and is only omitted on the last line of the
  287. file if the file doesn't end in a newline. This makes the return value
  288. unambiguous; if ``f.readline()`` returns an empty string, the end of the file
  289. has been reached, while a blank line is represented by ``'\n'``, a string
  290. containing only a single newline. ::
  291. >>> f.readline()
  292. 'This is the first line of the file.\n'
  293. >>> f.readline()
  294. 'Second line of the file\n'
  295. >>> f.readline()
  296. ''
  297. For reading lines from a file, you can loop over the file object. This is memory
  298. efficient, fast, and leads to simple code::
  299. >>> for line in f:
  300. ... print(line, end='')
  301. ...
  302. This is the first line of the file.
  303. Second line of the file
  304. If you want to read all the lines of a file in a list you can also use
  305. ``list(f)`` or ``f.readlines()``.
  306. ``f.write(string)`` writes the contents of *string* to the file, returning
  307. the number of characters written. ::
  308. >>> f.write('This is a test\n')
  309. 15
  310. Other types of objects need to be converted -- either to a string (in text mode)
  311. or a bytes object (in binary mode) -- before writing them::
  312. >>> value = ('the answer', 42)
  313. >>> s = str(value) # convert the tuple to string
  314. >>> f.write(s)
  315. 18
  316. ``f.tell()`` returns an integer giving the file object's current position in the file
  317. represented as number of bytes from the beginning of the file when in binary mode and
  318. an opaque number when in text mode.
  319. To change the file object's position, use ``f.seek(offset, whence)``. The position is computed
  320. from adding *offset* to a reference point; the reference point is selected by
  321. the *whence* argument. A *whence* value of 0 measures from the beginning
  322. of the file, 1 uses the current file position, and 2 uses the end of the file as
  323. the reference point. *whence* can be omitted and defaults to 0, using the
  324. beginning of the file as the reference point. ::
  325. >>> f = open('workfile', 'rb+')
  326. >>> f.write(b'0123456789abcdef')
  327. 16
  328. >>> f.seek(5) # Go to the 6th byte in the file
  329. 5
  330. >>> f.read(1)
  331. b'5'
  332. >>> f.seek(-3, 2) # Go to the 3rd byte before the end
  333. 13
  334. >>> f.read(1)
  335. b'd'
  336. In text files (those opened without a ``b`` in the mode string), only seeks
  337. relative to the beginning of the file are allowed (the exception being seeking
  338. to the very file end with ``seek(0, 2)``) and the only valid *offset* values are
  339. those returned from the ``f.tell()``, or zero. Any other *offset* value produces
  340. undefined behaviour.
  341. File objects have some additional methods, such as :meth:`~file.isatty` and
  342. :meth:`~file.truncate` which are less frequently used; consult the Library
  343. Reference for a complete guide to file objects.
  344. .. _tut-json:
  345. Saving structured data with :mod:`json`
  346. ---------------------------------------
  347. .. index:: module: json
  348. Strings can easily be written to and read from a file. Numbers take a bit more
  349. effort, since the :meth:`read` method only returns strings, which will have to
  350. be passed to a function like :func:`int`, which takes a string like ``'123'``
  351. and returns its numeric value 123. When you want to save more complex data
  352. types like nested lists and dictionaries, parsing and serializing by hand
  353. becomes complicated.
  354. Rather than having users constantly writing and debugging code to save
  355. complicated data types to files, Python allows you to use the popular data
  356. interchange format called `JSON (JavaScript Object Notation)
  357. <http://json.org>`_. The standard module called :mod:`json` can take Python
  358. data hierarchies, and convert them to string representations; this process is
  359. called :dfn:`serializing`. Reconstructing the data from the string representation
  360. is called :dfn:`deserializing`. Between serializing and deserializing, the
  361. string representing the object may have been stored in a file or data, or
  362. sent over a network connection to some distant machine.
  363. .. note::
  364. The JSON format is commonly used by modern applications to allow for data
  365. exchange. Many programmers are already familiar with it, which makes
  366. it a good choice for interoperability.
  367. If you have an object ``x``, you can view its JSON string representation with a
  368. simple line of code::
  369. >>> import json
  370. >>> json.dumps([1, 'simple', 'list'])
  371. '[1, "simple", "list"]'
  372. Another variant of the :func:`~json.dumps` function, called :func:`~json.dump`,
  373. simply serializes the object to a :term:`text file`. So if ``f`` is a
  374. :term:`text file` object opened for writing, we can do this::
  375. json.dump(x, f)
  376. To decode the object again, if ``f`` is a :term:`text file` object which has
  377. been opened for reading::
  378. x = json.load(f)
  379. This simple serialization technique can handle lists and dictionaries, but
  380. serializing arbitrary class instances in JSON requires a bit of extra effort.
  381. The reference for the :mod:`json` module contains an explanation of this.
  382. .. seealso::
  383. :mod:`pickle` - the pickle module
  384. Contrary to :ref:`JSON <tut-json>`, *pickle* is a protocol which allows
  385. the serialization of arbitrarily complex Python objects. As such, it is
  386. specific to Python and cannot be used to communicate with applications
  387. written in other languages. It is also insecure by default:
  388. deserializing pickle data coming from an untrusted source can execute
  389. arbitrary code, if the data was crafted by a skilled attacker.