summaryrefslogtreecommitdiffstats
path: root/Doc/ref/ref3.tex
Commit message (Collapse)AuthorAgeFilesLines
* SF doc patch #692001, properties and __getattribute__. I added someGuido van Rossum2003-02-281-8/+54
| | | | stuff, and changed 'property' to 'descriptor'.
* Document __module__.Jeremy Hylton2003-01-311-3/+11
|
* Fix typoRaymond Hettinger2003-01-191-1/+1
|
* SF patch #634866: Alex Martelli's corrections to the ref manual.Raymond Hettinger2003-01-191-37/+75
| | | | | Backport candidate. All but one or two of these changes are applicable to 2.2.2.
* This is Richie Hindle's patchMichael W. Hudson2002-12-171-5/+7
| | | | | | | | [ 643835 ] Set Next Statement for Python debuggers with a few tweaks by me: adding an unsigned or two, mentioning that not all jumps are allowed in the doc for pdb, adding a NEWS item and a note to whatsnew, and AuCTeX doing something cosmetic to libpdb.tex.
* Another try at clarifying what goes into and comes out of Unicode objects.Fred Drake2002-09-241-12/+20
| | | | Document the indices() method of slice objects.
* Clarified that the footnote applies to versions 1.5 and after instead ofRaymond Hettinger2002-09-081-4/+4
| | | | just version 1.5. Closes SF bug 577793.
* A few days ago, Guido said (in the thread "[Python-Dev] PythonMichael W. Hudson2002-07-191-0/+9
| | | | | | | | version of PySlice_GetIndicesEx"): > OK. Michael, if you want to check in indices(), go ahead. Then I did what was needed, but didn't check it in. Here it is.
* SF 563530 added missing methods for emulating numeric typesRaymond Hettinger2002-06-201-1/+5
|
* This is my nearly two year old patchMichael W. Hudson2002-06-111-0/+7
| | | | | | | | | [ 400998 ] experimental support for extended slicing on lists somewhat spruced up and better tested than it was when I wrote it. Includes docs & tests. The whatsnew section needs expanding, and arrays should support extended slices -- later.
* Fix up Guido's markup.Fred Drake2002-06-041-24/+24
|
* Addressed SF bug 421973 (finally).Guido van Rossum2002-06-031-46/+88
| | | | | | | | | | | | | | | | | Rewrote the subsection on coercion rules (and made it a proper subsection, with a label). The new section is much less precise, because precise rules would be too hard to give (== I don't know what they are any more :-). OTOH, the new section gives much more up-to-date information. Also noted that __coerce__ may return NotImplemented, with the same meaning as None. I beg Fred forgiveness: my use of \code{} is probably naive. Please fix this and other markup nits. An index entry would be nice. This could be a 2.2 bugfix candidate, if we bother about old docs (Fred?)
* Closes SF patch: 552468.Raymond Hettinger2002-05-121-4/+2
| | | | Type class unification invalidated the statement: x.__getitem__[i] is not equivalent to x[i].
* 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
|
* 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.
* 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.
* 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.
* Document generators and the yield statement, avoiding implementation details.Fred Drake2001-12-111-1/+13
|
* 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?)
* 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-281-3/+3
| | | | | | | | 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.
* Use the \note and \warning macros where appropriate.Fred Drake2001-10-201-4/+4
|
* 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.
* Add information about __floordiv__() and __truediv__() methods forFred Drake2001-08-141-5/+17
| | | | implementing numeric objects in Python.
* User-defined methods *can* contain things other than user-defined functionsFred Drake2001-08-021-1/+2
| | | | as the callable, so use more flexible language.
* Explain that __init__() methods do not get to return values.Fred Drake2001-08-021-8/+9
|
* Minor change to match the style guide.Fred Drake2001-07-141-1/+1
|
* Fix a very minor (but annoying when looking for things!) markup nit.Fred Drake2001-06-231-0/+2
|
* Bring the notes on the relationship between __cmp__(), __eq__(), andFred Drake2001-05-291-10/+15
| | | | | | | __hash__() up to date (re: use of objects which define these methods as dictionary keys). This closes SF bug #427698.
* Make sure we include all of Python's numeric types in the data modelFred Drake2001-05-141-1/+2
| | | | | | description, so that the introduction of complex is not a surprise. This closes SF bug #423429.
* Implement, test and document "key in dict" and "key not in dict".Guido van Rossum2001-04-201-3/+8
| | | | | | | | | 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-51/+56
| | | | Wrap some long lines and fix some markup nits.
* Add nested scopes spec to appendix.Jeremy Hylton2001-03-231-12/+29
| | | | | | | | | | | 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.
* 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.
* 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
|
* __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
|
* Fix typoAndrew M. Kuchling2000-12-191-1/+1
|
* 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.
* 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.
* 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.
* 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>.
generated by cgit v0.12 at 2024-09-23 20:30:28 (GMT)