| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
[ 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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[#448679] Left to right
* Python/compile.c
(com_dictmaker): Reordered evaluation of dictionaries to follow strict
LTR evaluation.
* Lib/compiler/pycodegen.py
(CodeGenerator.visitDict): Reordered evaluation of dictionaries to
follow strict LTR evaluation.
* Doc/ref/ref5.tex
Documented the general LTR evaluation order idea.
* Misc/NEWS
Documented change in evaluation order of dictionaries.
|
| |
|
|
|
|
| |
Closes SF 643227.
|
|
|
|
| |
Fixed minor bug preventing documentation compilation.
|
|
|
|
|
|
|
| |
guarantee abs(x%y) < abs(y) in all cases when a float is involved.
math.fmod() should, though, so noted that too.
Bugfix candidate. Someone should check the LaTeX here first, though.
|
|
|
|
|
|
| |
(including the implied call using back-ticks) of a recursive object,
but this is no longer the case.
Reported by Manus Hand via email.
|
|
|
|
| |
of date and did not reflect the current CPython implementation.
|
|
|
|
| |
Closes SF bug #546579.
|
|
|
|
|
|
|
| |
Closes SF bug #217195.
Make sure section numbers wrap together with the preceeding word
("section").
|
|
|
|
| |
Closes SF bug #217195.
|
|
|
|
| |
("section").
|
|
|
|
|
|
| |
and divmod() function for complex numbers.
Closes SF Bug 621708: Unclear deprecation.
|
| |
|
|
|
|
|
| |
for both HTML and typeset renderings. Corresponds to revision
1.53.4.8 on the r22-maint branch.
|
|
|
|
| |
Document the indices() method of slice objects.
|
| |
|
|
|
|
| |
just version 1.5. Closes SF bug 577793.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
are interpreted.
This closes SF bug #532467.
|
|
|
|
|
|
| |
actually allows all the legal syntax, and nothing else. Previously,
it did not allow a call like func(arg, **dictionary).
This closes (again!) SF bug #493243.
|
| |
|
|
|
|
|
|
|
|
| |
when used as part of the import statement.
Note that both "as" and "None" becoming keywords in the future.
Closes SF bug #553262.
|
|
|
|
|
| |
might be easier to understand.
This relates to SF bug #493243, which will be closed.
|
| |
|
|
|
|
|
|
|
|
|
| |
[ 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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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?)
|
| |
|
|
|
|
| |
Type class unification invalidated the statement: x.__getitem__[i] is not equivalent to x[i].
|
|
|
|
|
|
|
| |
(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.
|
| |
|
|
|
|
|
| |
dropped in the HTML formatted version.
Reported by Mike Coleman.
|
|
|
|
| |
Closes SF bug #518985.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|