summaryrefslogtreecommitdiffstats
path: root/Doc/ref
Commit message (Collapse)AuthorAgeFilesLines
* Added a missing "|" in the grammar productions used in the reference manualFred Drake2002-04-301-7/+9
| | | | | | | (reported by François Pinard). Added some missing "_" characters in the same cluster of productions. Added missing floor division operator in m_expr production, and mention floor division in the relevant portion of the text.
* Minor change to an index entry.Fred Drake2002-04-231-1/+1
|
* Adjust markup to worm around tool limitations; the "m" in "model" was beingFred Drake2002-04-171-1/+1
| | | | | dropped in the HTML formatted version. Reported by Mike Coleman.
* Remove repeated index entry; adds nothing different.Fred Drake2002-04-161-2/+1
| | | | Closes SF bug #518985.
* Document __unicode__. Fixes #541245.Martin v. Löwis2002-04-111-0/+7
|
* Fix typo: coverted --> converted. Reported by Francois Pinard.Fred Drake2002-04-091-1/+1
|
* Add the 'bool' type and its values 'False' and 'True', as described inGuido van Rossum2002-04-031-3/+17
| | | | | | | | | | | | | PEP 285. Everything described in the PEP is here, and there is even some documentation. I had to fix 12 unit tests; all but one of these were printing Boolean outcomes that changed from 0/1 to False/True. (The exception is test_unicode.py, which did a type(x) == type(y) style comparison. I could've fixed that with a single line using issubtype(x, type(y)), but instead chose to be explicit about those places where a bool is expected. Still to do: perhaps more documentation; change standard library modules to return False/True from predicates.
* Change reference to execframes to naming.Jeremy Hylton2002-04-011-1/+1
|
* Restore a minimal definition of execution frame, since other parts ofJeremy Hylton2002-04-011-0/+6
| | | | | | | | the manual refer to it. XXX Not sure that it belongs in this section, or that the concept is particularly important for writing documentation. Perhaps references to the frame should be removed entirely.
* Update programmer's note on nested functions.Jeremy Hylton2002-04-011-5/+5
|
* Reword explanation of global statement since an undeclared global is aJeremy Hylton2002-04-011-3/+3
| | | | free variable and is subject to those rules.
* Note the sole case in which the ban on "from ... import *" within aJeremy Hylton2002-04-011-1/+5
| | | | function is enforced.
* Remove the following restriction:Jeremy Hylton2002-04-011-4/+0
| | | | | | | Names bound by import statements may not occur in global statements in the same scope. Why not?
* Note that it is illegal to delete a cell variable.Jeremy Hylton2002-04-011-2/+6
| | | | Note that deleteing an unbound local will raise a NameError.
* Given lambda its own section, instead of burying it in boolean operators.Jeremy Hylton2002-04-011-30/+7
|
* Update / simplify Identifiers section for nested scopes.Jeremy Hylton2002-04-011-18/+2
| | | | How do I create a cross reference to section 4.1?
* Update docs for nested scopes.Jeremy Hylton2002-04-012-257/+134
| | | | | | | | | | | | | Replace section 4.1 with section A.3. The new section 4.1 is titled "Naming and binding." It includes the text of section A.3 augmented with some of the detailed text from the old section 4.1. The \dfn, \index stuff is probably wrong, but I tried. Also update other parts of appendix A to mention that nested scopes and generators are standard features.
* Update documentation of code objects.Jeremy Hylton2002-04-011-10/+15
| | | | | | | | Split the description of co_flags into two paragraphs. The first describes the flags that are used for non-future purposes, where CO_GENERATOR was added. The second describes __future__'s use of co_flags and mentions the only one currently meaningful, CO_FUTURE_DIVISION.
* Small fixes for description of function attributes.Jeremy Hylton2002-04-011-5/+3
| | | | | | func_closure is a readonly attribute. Add \ttindex{} for func_closure. Remove discussion of func_closure specific to 2.1.
* Fix up unescaped tilde; reported by several people.Fred Drake2002-03-181-1/+1
|
* Markup error: braces not properly marked in dictionary displayFred Drake2002-03-161-1/+1
| | | | | grammer productions. Fixes SF bug #520959.
* Revise the markup related to the grammar productions to increase theFred Drake2002-03-155-82/+76
| | | | | | level of predictability. This is not really "good" markup, but is arguably better than we had before. This closes SF bug #523117.
* Typo: thsi -> this. Closes SF bug #521450.Fred Drake2002-02-221-1/+1
|
* Fix typo reported by François Pinard.Fred Drake2002-01-211-1/+1
|
* Added some missing index entries, noted by L. Peter Deutsch.Fred Drake2001-12-271-0/+2
| | | | This should be included in Python 2.2.1.
* Update to use the notice environment so a multi-paragraph note can beFred Drake2001-12-141-2/+4
| | | | appropriately marked.
* Update information about __del__() & reference cycles for CPython.Fred Drake2001-12-141-7/+18
| | | | | | | This partially fixes SF bug #492619. Fix a typo & use the new notice environment instead of (ab)using the \note and \warning macros.
* Work around the problem of spaces after a "}" being dropped by LaTeX2HTML ifFred Drake2001-12-141-5/+5
| | | | | they were represented by newlines in the document source. Partially fixes SF bug #493243.
* Fix forMichael W. Hudson2001-12-121-2/+45
| | | | [ #429329 ] actual-parameters *arg, **kws not doc'd
* Add a note about yield requiring a __future__ directive.Fred Drake2001-12-121-0/+10
|
* Clean up a sad sentence in the yield description.Fred Drake2001-12-111-5/+5
|
* Document generators and the yield statement, avoiding implementation details.Fred Drake2001-12-112-1/+65
|
* Fix whitespace in example of bad indentation: a comment indicated that oneFred Drake2001-12-111-8/+8
| | | | | | | line was not indented at all, so the example is no longer indented at all. All of the errors being shown remain. Typo: characteru --> character
* Add change notes where im_class is discussed, since the exact meaning changesFred Drake2001-12-071-0/+2
| | | | with Python 2.2.
* Correct the description of im_class. (Fred, this is changed in 2.2.Guido van Rossum2001-12-071-6/+5
| | | | Should this be labeled as changed? How?)
* Add a note to the description of the interaction between the softspaceFred Drake2001-12-051-9/+12
| | | | | | | attribute of file objects, the print statement, and other file operations. This closes SF bug #484857. Fix minor markup nits.
* Import the keyword module instead of relying on our own list ofGuido van Rossum2001-12-041-11/+2
| | | | reserved words. No longer need to import string.
* Put the keywords back in alphabetical order. Apparently somebodyGuido van Rossum2001-12-041-2/+2
| | | | didn't use reswords.py, as the comment clearly states. :-(
* Remove most references to __members__ and __methods__, leaving only one pairFred Drake2001-12-031-8/+1
| | | | | | of references that now state that these attributes have been removed, directing the reader to the dir() function. This closes SF bug #456420.
* Clean up some markup cruft. A number of the macros that take noFred Drake2001-11-283-11/+11
| | | | | | | | parameters (like \UNIX) are commonly entered using an empty group to separate the markup from a following inter-word space; this is not needed when the next character is punctuation, or the markup is the last thing in the enclosing group. These cases were marked inconsistently; the empty group is now *only* used when needed.
* Fred observes that the typo was not the only problem with this sentence.Jeremy Hylton2001-11-141-1/+1
|
* typoJeremy Hylton2001-11-141-2/+2
|
* When describing "import *", add a level of indirection between "*" and theFred Drake2001-10-241-3/+17
| | | | | | | | set of names imported (the "public names"), adding a definition of "public names" that describes the use of __all__. This closes SF bug #473986. Flesh out the vague reference to __import__().
* Use the \note and \warning macros where appropriate.Fred Drake2001-10-202-6/+6
|
* Fix typo reported by Michael Soulier.Fred Drake2001-10-181-1/+1
|
* Removed stray backslash (a typo -- my fault).Tim Peters2001-10-011-1/+1
|
* The description of dictionary comparison was out of date. Rather thanTim Peters2001-10-011-9/+12
| | | | | | try to explain the complex general scheme we actually use now, I decided to spell out only what equality means (which is easy to explain and intuitive), leaving the other outcomes unspecified beyond consistency.
* Refer to the objects which define __len__(), __*item__(), and __iter__()Fred Drake2001-10-011-17/+35
| | | | | | as container objects rather than as mapping objects (in the index entries). Change the section heading and intro sentence to be a little more general, since that's how things have actually evolved.
* Fix minor usage and consistency nits.Fred Drake2001-09-181-4/+5
|
* Work around a LaTeX2HTML bug that caused the "m" in "mutable" to be droppedFred Drake2001-09-101-1/+1
| | | | in one place.
generated by cgit v0.12 at 2024-12-04 10:06:01 (GMT)