summaryrefslogtreecommitdiffstats
path: root/Doc/ref
Commit message (Collapse)AuthorAgeFilesLines
* Implement, test and document "key in dict" and "key not in dict".Guido van Rossum2001-04-202-4/+11
| | | | | | | | | I know some people don't like this -- if it's really controversial, I'll take it out again. (If it's only Alex Martelli who doesn't like it, that doesn't count as "real controversial" though. :-) That's why this is a separate checkin from the iterators stuff I'm about to check in next.
* Work around the conversion of ">>" and "<<" to guillemets. Reported by Ping.Fred Drake2001-04-131-1/+1
|
* Work around the conversion of ">>" and "<<" to guillemets. Reported by Ping.Fred Drake2001-04-131-51/+56
| | | | Wrap some long lines and fix some markup nits.
* Work around the conversion of ">>" and "<<" to guillemets. Reported byFred Drake2001-04-121-1/+1
| | | | Ping on the Doc-SIG mailing list.
* Typo: "ariables" --> "variables"Fred Drake2001-03-281-1/+1
| | | | This fixes SF bug #411118.
* Add nested scopes spec to appendix.Jeremy Hylton2001-03-233-32/+134
| | | | | | | | | | | Add new opcodes LOAD_CLOSURE, LOAD_DEREF, STORE_DEREF, MAKE_CLOSURE to docs for dis module. Add docs for new function and code members in Sec. 3 of ref manual. They're present regardless of whether nested scopes are used. Remove description of default argument hack from Sec. 7 of the ref manual and refer the reader to the appendix.
* No quotes around the "future" in the first use of the term "futureFred Drake2001-03-231-1/+1
| | | | statement".
* Include the futures appendix.Fred Drake2001-03-231-0/+3
|
* Revise the markup so that this formats and uses markup consistently withFred Drake2001-03-231-28/+32
| | | | the rest of the documentation.
* Add some initial text for the appendix on future statements and nested scopes.Jeremy Hylton2001-03-231-0/+149
|
* Note that assignments to __debug__ are illegalJeremy Hylton2001-03-231-0/+2
|
* Revert to ver 1.22, which was the version before the nested scopesJeremy Hylton2001-03-231-91/+106
| | | | | docs were introduced. This loses a few small changes, but Fred says that's okay.
* Do not refer to "sub-modules" since that is not a defined term.Fred Drake2001-03-061-7/+8
|
* Re-word the explanation of the in/not in operators for increased contentFred Drake2001-03-061-6/+14
| | | | | | | and clarity. Add a footnote to the information on the possibility of shadowing builtins with locals & module globals.
* Updates to describe function attributes.Barry Warsaw2001-02-271-4/+12
|
* Sequence indexes are non-negative, not natural (0 is not a natural number).Fred Drake2001-02-221-32/+32
| | | | | | Reported by Daniel May <mayds@ecn.purdue.edu>. De-tabified everywhere.
* Feeble attempt to repair obsolete info about hex escapes.Tim Peters2001-02-141-4/+2
|
* Minor markup adjustments.Fred Drake2001-02-021-15/+13
| | | | | Move some index entries next to what they are referring to for better "targetting".
* Allow 'continue' inside 'try' clauseJeremy Hylton2001-02-011-9/+11
| | | | SF patch 102989 by Thomas Wouters
* Remove spurious "\end{description}" that caused formatting to fail.Fred Drake2001-02-011-2/+0
|
* update section 4.1 to describe nested scopesJeremy Hylton2001-02-011-94/+83
|
* Remove note about the compiler not checking for two kinds of illegalJeremy Hylton2001-01-301-5/+0
| | | | imports. It checks for them now.
* Typo: coplete --> completeFred Drake2001-01-261-1/+1
| | | | This closes SF bug #129759.
* Updated note about collection of cyclic garbage, based on comments fromFred Drake2001-01-221-3/+6
| | | | Chris Ryland.
* Document rich comparisons.Guido van Rossum2001-01-181-5/+42
|
* Fix a variety of minor nits and typos caught by Chris RylandFred Drake2001-01-141-7/+7
| | | | <cpr@emsoftware.com>.
* Steve Holden <sholden@holdenweb.com>:Fred Drake2001-01-091-13/+13
| | | | Clarify the handling of characters following backslashes in raw strings.
* __rcmp__() description: Changed to indicate that this is no longerFred Drake2001-01-041-8/+1
| | | | | | | | supported as of Python 2.1. We still need to have an entry for this since it is reasonable for users to want to understand existing code. This closes SF bug #122715.
* Document the NotImplemented object.Neil Schemenauer2001-01-041-0/+9
|
* Improve description of else clause of the try/except/else statement.Fred Drake2001-01-021-6/+11
| | | | This closes (again!) bug #127098.
* Change documentation of 'else' clause of 'try/except' to make clear that itThomas Wouters2000-12-311-3/+5
| | | | | | | | doesn't get triggered by 'return', 'break' or 'continue'. If the 'try-inside-continue' patch does not get accepted before next release, the 'or continue' should be removed ;P Closes SF patch #103045 and SF bug #127098.
* Fix typoAndrew M. Kuchling2000-12-191-1/+1
|
* Updated string literals description to encompass Unicode literals and theFred Drake2000-12-191-11/+24
| | | | | additional escape sequences defined for Unicode. This closes bug #117158.
* Clarify __repr__ and __str__.Guido van Rossum2000-12-191-7/+10
|
* Additional docs for __iadd__ and family, closing SF bug #117178 and SF patchThomas Wouters2000-12-111-0/+26
| | | | #102169.
* Adjust explanation of operator precedence summary -- exponentiation groupsFred Drake2000-12-111-1/+2
| | | | | | from right to left! Closes bug #125391.
* Fix error noted by Gerrit Holl (old; had been buried in my INBOX):Fred Drake2000-12-071-3/+3
| | | | | sequence repitition works just fine with long integers now, so we should not say that only plain integers are allowed.
* Added a note that objects which emulate built-in types should onlyFred Drake2000-12-071-0/+7
| | | | | implement as many of the relevant methods as make sense for the particular information being modelled.
* Updates to reflect pending changes to the XML conversion process.Fred Drake2000-11-221-1/+1
|
* Note that readframes() returns data in linear format, even if the originalFred Drake2000-11-171-0/+6
| | | | | | | is encoded in u-LAW format. Based on suggestion from Anthony Baxter <anthony_baxter@users.sourceforge.net>. This closes bug #122273.
* Denis S. Otkidach <ods@users.sourceforge.net>:Fred Drake2000-09-211-0/+42
| | | | | | | | | | Show how code can be written to handle __getslice__ & friends in a way that is compatible with pre-2.0 versions of Python while still working with the "new" way of handling slicing. Additional explanation added by Fred Drake. This closes SourceForge patch #101388.
* Lots of minor fixes, many suggested by Detlef LannertFred Drake2000-09-211-7/+8
| | | | <lannert@uni-duesseldorf.de>.
* Note that __getitem__() may receive a slice object as the index;Fred Drake2000-09-211-2/+3
| | | | reported by Detlef Lannert <lannert@uni-duesseldorf.de>.
* Moshe Zadka <mzadka@geocities.com>:Fred Drake2000-09-191-0/+10
| | | | | | | Document the __contains__() method. (Patch slightly modified by FLD.) This closes SourceForge patch #101387.
* Many small clarifications, including many suggested by email.Fred Drake2000-09-191-17/+18
|
* Thomas Wouters <thomas@xs4all.net>:Fred Drake2000-09-121-0/+39
| | | | | | Reference manual docs for augmented assignment. This closes SourceForge patch #101418.
* add index entries for list comprehensionsSkip Montanaro2000-09-111-0/+2
|
* Document "print >> None"Barry Warsaw2000-08-291-3/+4
|
* Rough and incomplete documentation on augmented assignment, which followsThomas Wouters2000-08-242-4/+11
| | | | shortly. Markup also needs checking.
* fix list comprehension discussion to use \keyword macro instead of simplySkip Montanaro2000-08-231-3/+4
| | | | quoting keywords.