| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
index entry. Suggested to python-docs.
|
| |
|
|
| |
- use a TeX "tie" to prevent word-wrapping in "section x.y"-like text
|
| | |
|
| |
|
|
|
| |
Clarified that the footnote applies to versions 1.5 and after instead of
just version 1.5. Closes SF bug 577793.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Addressed SF bug 421973 (finally).
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.
FLD: My modifications to Guido's markup are included from revision 1.90.
|
| |
|
|
| |
Closes SF bug 548874 and patch 552468.
|
| |
|
|
| |
Closes SF bug #518985.
|
| |
|
|
|
|
|
| |
This partially fixes SF bug #492619.
Fix a typo & use the new notice environment instead of (ab)using the \note
and \warning macros.
|
| | |
|
| |
|
|
| |
with Python 2.2.
|
| |
|
|
| |
Should this be labeled as changed? How?)
|
| |
|
|
|
|
| |
of references that now state that these attributes have been removed,
directing the reader to the dir() function.
This closes SF bug #456420.
|
| |
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
in one place.
|
| |
|
|
| |
implementing numeric objects in Python.
|
| |
|
|
| |
as the callable, so use more flexible language.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
__hash__() up to date (re: use of objects which define these methods
as dictionary keys).
This closes SF bug #427698.
|
| |
|
|
|
|
| |
description, so that the introduction of complex is not a surprise.
This closes SF bug #423429.
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
Wrap some long lines and fix some markup nits.
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
| |
Reported by Daniel May <mayds@ecn.purdue.edu>.
De-tabified everywhere.
|
| |
|
|
| |
Chris Ryland.
|
| | |
|
| |
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
#102169.
|
| |
|
|
|
| |
implement as many of the relevant methods as make sense for the particular
information being modelled.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
reported by Detlef Lannert <lannert@uni-duesseldorf.de>.
|
| |
|
|
|
|
|
| |
Document the __contains__() method.
(Patch slightly modified by FLD.)
This closes SourceForge patch #101387.
|
| |
|
|
| |
shortly. Markup also needs checking.
|
| |
|
|
| |
stand out more.
|
| |
|
|
|
|
|
|
| |
is no __getslice__ available. Also does the same for C extension types.
Includes rudimentary documentation (it could use a cross reference to the
section on slice objects, I couldn't figure out how to do that) and a test
suite for all Python __hooks__ I could think of, including the new
behaviour.
|
| |
|
|
|
|
|
|
|
|
|
| |
distutils patches, which I'll leave to the distutils maintainers.
Tip: review the patch like this:
grep "^[\!+-] " <patchfile>
To get a quick and easy way to review the actual changes. Most of the
changes are single-line ones, anyway.
|
| |
|
|
|
| |
__setitem__(), and __delitem__(). Based on related comments from
Barry Warsaw.
|
| |
|
|
|
|
|
|
|
| |
are and are not turned into bound methods; some confusion was noted by
Andrew Dalke.
In particular, it has to be noted that functions located on the class
instance are not turned into any sort of method, only those which are
found via the underlying class.
|
| |
|
|
| |
Carl Feynman <carlf@abinitio.com>.
|
| |
|
|
| |
those markups! <with-mixed-feelings>
|