|
1 .. _glossary: |
|
2 |
|
3 ******** |
|
4 Glossary |
|
5 ******** |
|
6 |
|
7 .. if you add new entries, keep the alphabetical sorting! |
|
8 |
|
9 .. glossary:: |
|
10 |
|
11 ``>>>`` |
|
12 The default Python prompt of the interactive shell. Often seen for code |
|
13 examples which can be executed interactively in the interpreter. |
|
14 |
|
15 ``...`` |
|
16 The default Python prompt of the interactive shell when entering code for |
|
17 an indented code block or within a pair of matching left and right |
|
18 delimiters (parentheses, square brackets or curly braces). |
|
19 |
|
20 2to3 |
|
21 A tool that tries to convert Python 2.x code to Python 3.x code by |
|
22 handling most of the incompatibilites which can be detected by parsing the |
|
23 source and traversing the parse tree. |
|
24 |
|
25 2to3 is available in the standard library as :mod:`lib2to3`; a standalone |
|
26 entry point is provided as :file:`Tools/scripts/2to3`. See |
|
27 :ref:`2to3-reference`. |
|
28 |
|
29 abstract base class |
|
30 Abstract Base Classes (abbreviated ABCs) complement :term:`duck-typing` by |
|
31 providing a way to define interfaces when other techniques like :func:`hasattr` |
|
32 would be clumsy. Python comes with many builtin ABCs for data structures |
|
33 (in the :mod:`collections` module), numbers (in the :mod:`numbers` |
|
34 module), and streams (in the :mod:`io` module). You can create your own |
|
35 ABC with the :mod:`abc` module. |
|
36 |
|
37 argument |
|
38 A value passed to a function or method, assigned to a named local |
|
39 variable in the function body. A function or method may have both |
|
40 positional arguments and keyword arguments in its definition. |
|
41 Positional and keyword arguments may be variable-length: ``*`` accepts |
|
42 or passes (if in the function definition or call) several positional |
|
43 arguments in a list, while ``**`` does the same for keyword arguments |
|
44 in a dictionary. |
|
45 |
|
46 Any expression may be used within the argument list, and the evaluated |
|
47 value is passed to the local variable. |
|
48 |
|
49 attribute |
|
50 A value associated with an object which is referenced by name using |
|
51 dotted expressions. For example, if an object *o* has an attribute |
|
52 *a* it would be referenced as *o.a*. |
|
53 |
|
54 BDFL |
|
55 Benevolent Dictator For Life, a.k.a. `Guido van Rossum |
|
56 <http://www.python.org/~guido/>`_, Python's creator. |
|
57 |
|
58 bytecode |
|
59 Python source code is compiled into bytecode, the internal representation |
|
60 of a Python program in the interpreter. The bytecode is also cached in |
|
61 ``.pyc`` and ``.pyo`` files so that executing the same file is faster the |
|
62 second time (recompilation from source to bytecode can be avoided). This |
|
63 "intermediate language" is said to run on a :term:`virtual machine` |
|
64 that executes the machine code corresponding to each bytecode. |
|
65 |
|
66 class |
|
67 A template for creating user-defined objects. Class definitions |
|
68 normally contain method definitions which operate on instances of the |
|
69 class. |
|
70 |
|
71 classic class |
|
72 Any class which does not inherit from :class:`object`. See |
|
73 :term:`new-style class`. Classic classes will be removed in Python 3.0. |
|
74 |
|
75 coercion |
|
76 The implicit conversion of an instance of one type to another during an |
|
77 operation which involves two arguments of the same type. For example, |
|
78 ``int(3.15)`` converts the floating point number to the integer ``3``, but |
|
79 in ``3+4.5``, each argument is of a different type (one int, one float), |
|
80 and both must be converted to the same type before they can be added or it |
|
81 will raise a ``TypeError``. Coercion between two operands can be |
|
82 performed with the ``coerce`` builtin function; thus, ``3+4.5`` is |
|
83 equivalent to calling ``operator.add(*coerce(3, 4.5))`` and results in |
|
84 ``operator.add(3.0, 4.5)``. Without coercion, all arguments of even |
|
85 compatible types would have to be normalized to the same value by the |
|
86 programmer, e.g., ``float(3)+4.5`` rather than just ``3+4.5``. |
|
87 |
|
88 complex number |
|
89 An extension of the familiar real number system in which all numbers are |
|
90 expressed as a sum of a real part and an imaginary part. Imaginary |
|
91 numbers are real multiples of the imaginary unit (the square root of |
|
92 ``-1``), often written ``i`` in mathematics or ``j`` in |
|
93 engineering. Python has builtin support for complex numbers, which are |
|
94 written with this latter notation; the imaginary part is written with a |
|
95 ``j`` suffix, e.g., ``3+1j``. To get access to complex equivalents of the |
|
96 :mod:`math` module, use :mod:`cmath`. Use of complex numbers is a fairly |
|
97 advanced mathematical feature. If you're not aware of a need for them, |
|
98 it's almost certain you can safely ignore them. |
|
99 |
|
100 context manager |
|
101 An object which controls the environment seen in a :keyword:`with` |
|
102 statement by defining :meth:`__enter__` and :meth:`__exit__` methods. |
|
103 See :pep:`343`. |
|
104 |
|
105 CPython |
|
106 The canonical implementation of the Python programming language. The |
|
107 term "CPython" is used in contexts when necessary to distinguish this |
|
108 implementation from others such as Jython or IronPython. |
|
109 |
|
110 decorator |
|
111 A function returning another function, usually applied as a function |
|
112 transformation using the ``@wrapper`` syntax. Common examples for |
|
113 decorators are :func:`classmethod` and :func:`staticmethod`. |
|
114 |
|
115 The decorator syntax is merely syntactic sugar, the following two |
|
116 function definitions are semantically equivalent:: |
|
117 |
|
118 def f(...): |
|
119 ... |
|
120 f = staticmethod(f) |
|
121 |
|
122 @staticmethod |
|
123 def f(...): |
|
124 ... |
|
125 |
|
126 descriptor |
|
127 Any *new-style* object which defines the methods :meth:`__get__`, |
|
128 :meth:`__set__`, or :meth:`__delete__`. When a class attribute is a |
|
129 descriptor, its special binding behavior is triggered upon attribute |
|
130 lookup. Normally, using *a.b* to get, set or delete an attribute looks up |
|
131 the object named *b* in the class dictionary for *a*, but if *b* is a |
|
132 descriptor, the respective descriptor method gets called. Understanding |
|
133 descriptors is a key to a deep understanding of Python because they are |
|
134 the basis for many features including functions, methods, properties, |
|
135 class methods, static methods, and reference to super classes. |
|
136 |
|
137 For more information about descriptors' methods, see :ref:`descriptors`. |
|
138 |
|
139 dictionary |
|
140 An associative array, where arbitrary keys are mapped to values. The use |
|
141 of :class:`dict` closely resembles that for :class:`list`, but the keys can |
|
142 be any object with a :meth:`__hash__` function, not just integers. |
|
143 Called a hash in Perl. |
|
144 |
|
145 docstring |
|
146 A string literal which appears as the first expression in a class, |
|
147 function or module. While ignored when the suite is executed, it is |
|
148 recognized by the compiler and put into the :attr:`__doc__` attribute |
|
149 of the enclosing class, function or module. Since it is available via |
|
150 introspection, it is the canonical place for documentation of the |
|
151 object. |
|
152 |
|
153 duck-typing |
|
154 A pythonic programming style which determines an object's type by inspection |
|
155 of its method or attribute signature rather than by explicit relationship |
|
156 to some type object ("If it looks like a duck and quacks like a duck, it |
|
157 must be a duck.") By emphasizing interfaces rather than specific types, |
|
158 well-designed code improves its flexibility by allowing polymorphic |
|
159 substitution. Duck-typing avoids tests using :func:`type` or |
|
160 :func:`isinstance`. (Note, however, that duck-typing can be complemented |
|
161 with abstract base classes.) Instead, it typically employs :func:`hasattr` |
|
162 tests or :term:`EAFP` programming. |
|
163 |
|
164 EAFP |
|
165 Easier to ask for forgiveness than permission. This common Python coding |
|
166 style assumes the existence of valid keys or attributes and catches |
|
167 exceptions if the assumption proves false. This clean and fast style is |
|
168 characterized by the presence of many :keyword:`try` and :keyword:`except` |
|
169 statements. The technique contrasts with the :term:`LBYL` style |
|
170 common to many other languages such as C. |
|
171 |
|
172 expression |
|
173 A piece of syntax which can be evaluated to some value. In other words, |
|
174 an expression is an accumulation of expression elements like literals, names, |
|
175 attribute access, operators or function calls which all return a value. |
|
176 In contrast to many other languages, not all language constructs are expressions. |
|
177 There are also :term:`statement`\s which cannot be used as expressions, |
|
178 such as :keyword:`print` or :keyword:`if`. Assignments are also statements, |
|
179 not expressions. |
|
180 |
|
181 extension module |
|
182 A module written in C or C++, using Python's C API to interact with the core and |
|
183 with user code. |
|
184 |
|
185 function |
|
186 A series of statements which returns some value to a caller. It can also |
|
187 be passed zero or more arguments which may be used in the execution of |
|
188 the body. See also :term:`argument` and :term:`method`. |
|
189 |
|
190 __future__ |
|
191 A pseudo module which programmers can use to enable new language features |
|
192 which are not compatible with the current interpreter. For example, the |
|
193 expression ``11/4`` currently evaluates to ``2``. If the module in which |
|
194 it is executed had enabled *true division* by executing:: |
|
195 |
|
196 from __future__ import division |
|
197 |
|
198 the expression ``11/4`` would evaluate to ``2.75``. By importing the |
|
199 :mod:`__future__` module and evaluating its variables, you can see when a |
|
200 new feature was first added to the language and when it will become the |
|
201 default:: |
|
202 |
|
203 >>> import __future__ |
|
204 >>> __future__.division |
|
205 _Feature((2, 2, 0, 'alpha', 2), (3, 0, 0, 'alpha', 0), 8192) |
|
206 |
|
207 garbage collection |
|
208 The process of freeing memory when it is not used anymore. Python |
|
209 performs garbage collection via reference counting and a cyclic garbage |
|
210 collector that is able to detect and break reference cycles. |
|
211 |
|
212 generator |
|
213 A function which returns an iterator. It looks like a normal function |
|
214 except that values are returned to the caller using a :keyword:`yield` |
|
215 statement instead of a :keyword:`return` statement. Generator functions |
|
216 often contain one or more :keyword:`for` or :keyword:`while` loops which |
|
217 :keyword:`yield` elements back to the caller. The function execution is |
|
218 stopped at the :keyword:`yield` keyword (returning the result) and is |
|
219 resumed there when the next element is requested by calling the |
|
220 :meth:`next` method of the returned iterator. |
|
221 |
|
222 .. index:: single: generator expression |
|
223 |
|
224 generator expression |
|
225 An expression that returns a generator. It looks like a normal expression |
|
226 followed by a :keyword:`for` expression defining a loop variable, range, |
|
227 and an optional :keyword:`if` expression. The combined expression |
|
228 generates values for an enclosing function:: |
|
229 |
|
230 >>> sum(i*i for i in range(10)) # sum of squares 0, 1, 4, ... 81 |
|
231 285 |
|
232 |
|
233 GIL |
|
234 See :term:`global interpreter lock`. |
|
235 |
|
236 global interpreter lock |
|
237 The lock used by Python threads to assure that only one thread |
|
238 executes in the :term:`CPython` :term:`virtual machine` at a time. |
|
239 This simplifies the CPython implementation by assuring that no two |
|
240 processes can access the same memory at the same time. Locking the |
|
241 entire interpreter makes it easier for the interpreter to be |
|
242 multi-threaded, at the expense of much of the parallelism afforded by |
|
243 multi-processor machines. Efforts have been made in the past to |
|
244 create a "free-threaded" interpreter (one which locks shared data at a |
|
245 much finer granularity), but so far none have been successful because |
|
246 performance suffered in the common single-processor case. |
|
247 |
|
248 hashable |
|
249 An object is *hashable* if it has a hash value which never changes during |
|
250 its lifetime (it needs a :meth:`__hash__` method), and can be compared to |
|
251 other objects (it needs an :meth:`__eq__` or :meth:`__cmp__` method). |
|
252 Hashable objects which compare equal must have the same hash value. |
|
253 |
|
254 Hashability makes an object usable as a dictionary key and a set member, |
|
255 because these data structures use the hash value internally. |
|
256 |
|
257 All of Python's immutable built-in objects are hashable, while no mutable |
|
258 containers (such as lists or dictionaries) are. Objects which are |
|
259 instances of user-defined classes are hashable by default; they all |
|
260 compare unequal, and their hash value is their :func:`id`. |
|
261 |
|
262 IDLE |
|
263 An Integrated Development Environment for Python. IDLE is a basic editor |
|
264 and interpreter environment which ships with the standard distribution of |
|
265 Python. Good for beginners, it also serves as clear example code for |
|
266 those wanting to implement a moderately sophisticated, multi-platform GUI |
|
267 application. |
|
268 |
|
269 immutable |
|
270 An object with a fixed value. Immutable objects include numbers, strings and |
|
271 tuples. Such an object cannot be altered. A new object has to |
|
272 be created if a different value has to be stored. They play an important |
|
273 role in places where a constant hash value is needed, for example as a key |
|
274 in a dictionary. |
|
275 |
|
276 integer division |
|
277 Mathematical division discarding any remainder. For example, the |
|
278 expression ``11/4`` currently evaluates to ``2`` in contrast to the |
|
279 ``2.75`` returned by float division. Also called *floor division*. |
|
280 When dividing two integers the outcome will always be another integer |
|
281 (having the floor function applied to it). However, if one of the operands |
|
282 is another numeric type (such as a :class:`float`), the result will be |
|
283 coerced (see :term:`coercion`) to a common type. For example, an integer |
|
284 divided by a float will result in a float value, possibly with a decimal |
|
285 fraction. Integer division can be forced by using the ``//`` operator |
|
286 instead of the ``/`` operator. See also :term:`__future__`. |
|
287 |
|
288 interactive |
|
289 Python has an interactive interpreter which means you can enter |
|
290 statements and expressions at the interpreter prompt, immediately |
|
291 execute them and see their results. Just launch ``python`` with no |
|
292 arguments (possibly by selecting it from your computer's main |
|
293 menu). It is a very powerful way to test out new ideas or inspect |
|
294 modules and packages (remember ``help(x)``). |
|
295 |
|
296 interpreted |
|
297 Python is an interpreted language, as opposed to a compiled one, |
|
298 though the distinction can be blurry because of the presence of the |
|
299 bytecode compiler. This means that source files can be run directly |
|
300 without explicitly creating an executable which is then run. |
|
301 Interpreted languages typically have a shorter development/debug cycle |
|
302 than compiled ones, though their programs generally also run more |
|
303 slowly. See also :term:`interactive`. |
|
304 |
|
305 iterable |
|
306 A container object capable of returning its members one at a |
|
307 time. Examples of iterables include all sequence types (such as |
|
308 :class:`list`, :class:`str`, and :class:`tuple`) and some non-sequence |
|
309 types like :class:`dict` and :class:`file` and objects of any classes you |
|
310 define with an :meth:`__iter__` or :meth:`__getitem__` method. Iterables |
|
311 can be used in a :keyword:`for` loop and in many other places where a |
|
312 sequence is needed (:func:`zip`, :func:`map`, ...). When an iterable |
|
313 object is passed as an argument to the builtin function :func:`iter`, it |
|
314 returns an iterator for the object. This iterator is good for one pass |
|
315 over the set of values. When using iterables, it is usually not necessary |
|
316 to call :func:`iter` or deal with iterator objects yourself. The ``for`` |
|
317 statement does that automatically for you, creating a temporary unnamed |
|
318 variable to hold the iterator for the duration of the loop. See also |
|
319 :term:`iterator`, :term:`sequence`, and :term:`generator`. |
|
320 |
|
321 iterator |
|
322 An object representing a stream of data. Repeated calls to the iterator's |
|
323 :meth:`next` method return successive items in the stream. When no more |
|
324 data are available a :exc:`StopIteration` exception is raised instead. At |
|
325 this point, the iterator object is exhausted and any further calls to its |
|
326 :meth:`next` method just raise :exc:`StopIteration` again. Iterators are |
|
327 required to have an :meth:`__iter__` method that returns the iterator |
|
328 object itself so every iterator is also iterable and may be used in most |
|
329 places where other iterables are accepted. One notable exception is code |
|
330 which attempts multiple iteration passes. A container object (such as a |
|
331 :class:`list`) produces a fresh new iterator each time you pass it to the |
|
332 :func:`iter` function or use it in a :keyword:`for` loop. Attempting this |
|
333 with an iterator will just return the same exhausted iterator object used |
|
334 in the previous iteration pass, making it appear like an empty container. |
|
335 |
|
336 More information can be found in :ref:`typeiter`. |
|
337 |
|
338 keyword argument |
|
339 Arguments which are preceded with a ``variable_name=`` in the call. |
|
340 The variable name designates the local name in the function to which the |
|
341 value is assigned. ``**`` is used to accept or pass a dictionary of |
|
342 keyword arguments. See :term:`argument`. |
|
343 |
|
344 lambda |
|
345 An anonymous inline function consisting of a single :term:`expression` |
|
346 which is evaluated when the function is called. The syntax to create |
|
347 a lambda function is ``lambda [arguments]: expression`` |
|
348 |
|
349 LBYL |
|
350 Look before you leap. This coding style explicitly tests for |
|
351 pre-conditions before making calls or lookups. This style contrasts with |
|
352 the :term:`EAFP` approach and is characterized by the presence of many |
|
353 :keyword:`if` statements. |
|
354 |
|
355 list |
|
356 A built-in Python :term:`sequence`. Despite its name it is more akin |
|
357 to an array in other languages than to a linked list since access to |
|
358 elements are O(1). |
|
359 |
|
360 list comprehension |
|
361 A compact way to process all or part of the elements in a sequence and |
|
362 return a list with the results. ``result = ["0x%02x" % x for x in |
|
363 range(256) if x % 2 == 0]`` generates a list of strings containing |
|
364 even hex numbers (0x..) in the range from 0 to 255. The :keyword:`if` |
|
365 clause is optional. If omitted, all elements in ``range(256)`` are |
|
366 processed. |
|
367 |
|
368 mapping |
|
369 A container object (such as :class:`dict`) which supports arbitrary key |
|
370 lookups using the special method :meth:`__getitem__`. |
|
371 |
|
372 metaclass |
|
373 The class of a class. Class definitions create a class name, a class |
|
374 dictionary, and a list of base classes. The metaclass is responsible for |
|
375 taking those three arguments and creating the class. Most object oriented |
|
376 programming languages provide a default implementation. What makes Python |
|
377 special is that it is possible to create custom metaclasses. Most users |
|
378 never need this tool, but when the need arises, metaclasses can provide |
|
379 powerful, elegant solutions. They have been used for logging attribute |
|
380 access, adding thread-safety, tracking object creation, implementing |
|
381 singletons, and many other tasks. |
|
382 |
|
383 More information can be found in :ref:`metaclasses`. |
|
384 |
|
385 method |
|
386 A function which is defined inside a class body. If called as an attribute |
|
387 of an instance of that class, the method will get the instance object as |
|
388 its first :term:`argument` (which is usually called ``self``). |
|
389 See :term:`function` and :term:`nested scope`. |
|
390 |
|
391 mutable |
|
392 Mutable objects can change their value but keep their :func:`id`. See |
|
393 also :term:`immutable`. |
|
394 |
|
395 named tuple |
|
396 Any tuple subclass whose indexable elements are also accessible using |
|
397 named attributes (for example, :func:`time.localtime` returns a |
|
398 tuple-like object where the *year* is accessible either with an |
|
399 index such as ``t[0]`` or with a named attribute like ``t.tm_year``). |
|
400 |
|
401 A named tuple can be a built-in type such as :class:`time.struct_time`, |
|
402 or it can be created with a regular class definition. A full featured |
|
403 named tuple can also be created with the factory function |
|
404 :func:`collections.namedtuple`. The latter approach automatically |
|
405 provides extra features such as a self-documenting representation like |
|
406 ``Employee(name='jones', title='programmer')``. |
|
407 |
|
408 namespace |
|
409 The place where a variable is stored. Namespaces are implemented as |
|
410 dictionaries. There are the local, global and builtin namespaces as well |
|
411 as nested namespaces in objects (in methods). Namespaces support |
|
412 modularity by preventing naming conflicts. For instance, the functions |
|
413 :func:`__builtin__.open` and :func:`os.open` are distinguished by their |
|
414 namespaces. Namespaces also aid readability and maintainability by making |
|
415 it clear which module implements a function. For instance, writing |
|
416 :func:`random.seed` or :func:`itertools.izip` makes it clear that those |
|
417 functions are implemented by the :mod:`random` and :mod:`itertools` |
|
418 modules, respectively. |
|
419 |
|
420 nested scope |
|
421 The ability to refer to a variable in an enclosing definition. For |
|
422 instance, a function defined inside another function can refer to |
|
423 variables in the outer function. Note that nested scopes work only for |
|
424 reference and not for assignment which will always write to the innermost |
|
425 scope. In contrast, local variables both read and write in the innermost |
|
426 scope. Likewise, global variables read and write to the global namespace. |
|
427 |
|
428 new-style class |
|
429 Any class which inherits from :class:`object`. This includes all built-in |
|
430 types like :class:`list` and :class:`dict`. Only new-style classes can |
|
431 use Python's newer, versatile features like :attr:`__slots__`, |
|
432 descriptors, properties, and :meth:`__getattribute__`. |
|
433 |
|
434 More information can be found in :ref:`newstyle`. |
|
435 |
|
436 object |
|
437 Any data with state (attributes or value) and defined behavior |
|
438 (methods). Also the ultimate base class of any :term:`new-style |
|
439 class`. |
|
440 |
|
441 positional argument |
|
442 The arguments assigned to local names inside a function or method, |
|
443 determined by the order in which they were given in the call. ``*`` is |
|
444 used to either accept multiple positional arguments (when in the |
|
445 definition), or pass several arguments as a list to a function. See |
|
446 :term:`argument`. |
|
447 |
|
448 Python 3000 |
|
449 Nickname for the next major Python version, 3.0 (coined long ago |
|
450 when the release of version 3 was something in the distant future.) This |
|
451 is also abbreviated "Py3k". |
|
452 |
|
453 Pythonic |
|
454 An idea or piece of code which closely follows the most common idioms |
|
455 of the Python language, rather than implementing code using concepts |
|
456 common to other languages. For example, a common idiom in Python is |
|
457 to loop over all elements of an iterable using a :keyword:`for` |
|
458 statement. Many other languages don't have this type of construct, so |
|
459 people unfamiliar with Python sometimes use a numerical counter instead:: |
|
460 |
|
461 for i in range(len(food)): |
|
462 print food[i] |
|
463 |
|
464 As opposed to the cleaner, Pythonic method:: |
|
465 |
|
466 for piece in food: |
|
467 print piece |
|
468 |
|
469 reference count |
|
470 The number of references to an object. When the reference count of an |
|
471 object drops to zero, it is deallocated. Reference counting is |
|
472 generally not visible to Python code, but it is a key element of the |
|
473 :term:`CPython` implementation. The :mod:`sys` module defines a |
|
474 :func:`getrefcount` function that programmers can call to return the |
|
475 reference count for a particular object. |
|
476 |
|
477 __slots__ |
|
478 A declaration inside a :term:`new-style class` that saves memory by |
|
479 pre-declaring space for instance attributes and eliminating instance |
|
480 dictionaries. Though popular, the technique is somewhat tricky to get |
|
481 right and is best reserved for rare cases where there are large numbers of |
|
482 instances in a memory-critical application. |
|
483 |
|
484 sequence |
|
485 An :term:`iterable` which supports efficient element access using integer |
|
486 indices via the :meth:`__getitem__` special method and defines a |
|
487 :meth:`len` method that returns the length of the sequence. |
|
488 Some built-in sequence types are :class:`list`, :class:`str`, |
|
489 :class:`tuple`, and :class:`unicode`. Note that :class:`dict` also |
|
490 supports :meth:`__getitem__` and :meth:`__len__`, but is considered a |
|
491 mapping rather than a sequence because the lookups use arbitrary |
|
492 :term:`immutable` keys rather than integers. |
|
493 |
|
494 slice |
|
495 An object usually containing a portion of a :term:`sequence`. A slice is |
|
496 created using the subscript notation, ``[]`` with colons between numbers |
|
497 when several are given, such as in ``variable_name[1:3:5]``. The bracket |
|
498 (subscript) notation uses :class:`slice` objects internally (or in older |
|
499 versions, :meth:`__getslice__` and :meth:`__setslice__`). |
|
500 |
|
501 statement |
|
502 A statement is part of a suite (a "block" of code). A statement is either |
|
503 an :term:`expression` or a one of several constructs with a keyword, such |
|
504 as :keyword:`if`, :keyword:`while` or :keyword:`print`. |
|
505 |
|
506 triple-quoted string |
|
507 A string which is bound by three instances of either a quotation mark |
|
508 (") or an apostrophe ('). While they don't provide any functionality |
|
509 not available with single-quoted strings, they are useful for a number |
|
510 of reasons. They allow you to include unescaped single and double |
|
511 quotes within a string and they can span multiple lines without the |
|
512 use of the continuation character, making them especially useful when |
|
513 writing docstrings. |
|
514 |
|
515 type |
|
516 The type of a Python object determines what kind of object it is; every |
|
517 object has a type. An object's type is accessible as its |
|
518 :attr:`__class__` attribute or can be retrieved with ``type(obj)``. |
|
519 |
|
520 virtual machine |
|
521 A computer defined entirely in software. Python's virtual machine |
|
522 executes the :term:`bytecode` emitted by the bytecode compiler. |
|
523 |
|
524 Zen of Python |
|
525 Listing of Python design principles and philosophies that are helpful in |
|
526 understanding and using the language. The listing can be found by typing |
|
527 "``import this``" at the interactive prompt. |