| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
Python 2.5 added support for explicit relative import statements and
yield expressions, which were missing in the manual.
Also fix grammar productions that used the names from the Grammar file,
markup that broke the generated grammar.txt, and wrap some lines that
broke the pdf output.
(backport from rev. 54559)
|
| |
|
|
|
|
| |
nearly the same place.
They are same, so keep the original one and remove the later-added one.
|
| | |
|
| |
|
|
| |
of all remaining references to context objects that I could find. Without a __context__() method context objects no longer exist. Also get test_with working again, and adopt a suggestion from Neal for decimal.Context.get_manager()
|
| |
|
|
|
|
|
|
| |
discussion.
There are two places of documentation that still mention __context__:
Doc/lib/libstdtypes.tex -- I wasn't quite sure how to rewrite that without
spending a whole lot of time thinking about it; and whatsnew, which Andrew
usually likes to change himself.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
terminology in the alpha 1 documentation.
- "context manager" reverts to its alpha 1 definition
- the term "context specifier" goes away entirely
- contextlib.GeneratorContextManager is renamed GeneratorContext
There are still a number of changes relative to alpha 1:
- the expression in the with statement is explicitly called the
"context expression" in the language reference
- the terms 'with statement context', 'context object' or 'with
statement context' are used in several places instead of a bare
'context'. The aim of this is to avoid ambiguity in relation to the
runtime context set up when the block is executed, and the context
objects that already exist in various application domains (such as
decimal.Context)
- contextlib.contextmanager is renamed to contextfactory
This best reflects the nature of the function resulting from the
use of that decorator
- decimal.ContextManager is renamed to WithStatementContext
Simple dropping the 'Manager' part wasn't possible due to the
fact that decimal.Context already exists and means something
different. WithStatementContext is ugly but workable.
A technically unrelated change snuck into this commit:
contextlib.closing now avoids the overhead of creating a
generator, since it's trivial to implement that particular
context manager directly.
|
| |
|
|
| |
instead of context object
|
| |
|
|
| |
implementation
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This was started by Mike Bland and completed by Guido
(with help from Neal).
This still needs a __future__ statement added;
Thomas is working on Michael's patch for that aspect.
There's a small amount of code cleanup and refactoring
in ast.c, compile.c and ceval.c (I fixed the lltrace
behavior when EXT_POP is used -- however I had to make
lltrace a static global).
|
| | |
|
| |
|
|
|
|
|
| |
[ 1207501 ] Issue in grammar
We didn't define dotted_name in the pseudo-grammar in the reference
docs. Backport candidate.
|
| | |
|
| | |
|
| |
|
|
| |
(SF bug #829073)
|
| |
|
|
| |
(SF bug #798652)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[ 1009560 ] Fix @decorator evaluation order
From the description:
Changes in this patch:
- Change Grammar/Grammar to require
newlines between adjacent decorators.
- Fix order of evaluation of decorators
in the C (compile.c) and python
(Lib/compiler/pycodegen.py) compilers
- Add better order of evaluation check
to test_decorators.py (test_eval_order)
- Update the decorator documentation in
the reference manual (improve description
of evaluation order and update syntax
description)
and the comment:
Used Brett's evaluation order (see
http://mail.python.org/pipermail/python-dev/2004-August/047835.html)
(I'm checking this in for Anthony who was having problems getting SF to
talk to him)
|
| |
|
|
|
| |
"@ seems the syntax that everybody can hate equally"
Implementation by Mark Russell, from SF #979728.
|
| |
|
|
| |
Will backport to 2.3.
|
| |
|
|
|
|
|
|
| |
"classic" class objects
[partially fixes SF bug #453684]
- add note that new-style classes can use descriptors to implement
instance variables in different ways
|
| | |
|
| |
|
|
|
|
|
| |
Closes SF bug #217195.
Make sure section numbers wrap together with the preceeding word
("section").
|
| | |
|
| | |
|
| |
|
|
|
|
| |
level of predictability. This is not really "good" markup, but is arguably
better than we had before.
This closes SF bug #523117.
|
| | |
|
| |
|
|
| |
This should be included in Python 2.2.1.
|
| | |
|
| |
|
|
|
| |
this supports a hyperlinked version of the grammar that can make tracking
down details and definitions a little easier.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
SF patch 102989 by Thomas Wouters
|
| |
|
|
| |
This closes (again!) bug #127098.
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
Dan Wolfe <wolfeman@apple.com>.
|
| | |
|
| | |
|
| |
|
|
| |
an example.
|
| | |
|
| |
|
|
| |
semantic file names in the HTML. No more node#.html files!
|
| | |
|
| | |
|
| | |
|