| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
"innermost last" --> "most recent call last"
|
| |
|
|
|
|
| |
Switch from octal escapes to hex escapes for other nonprintable characters.
|
|
|
|
|
|
| |
this is not hard to explain!
Closes SF bug #129345.
|
| |
|
|
|
|
| |
This closes bug #123730.
|
| |
|
| |
|
| |
|
|
|
|
| |
This closes bug #117706.
|
|
|
|
|
|
|
|
|
| |
to reflect current behavior.
This closes SourceForge bug #117305.
Made a reference to the library reference a hyperlink.
Fixed some minor markup nits.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixed displays of the interactive prompt in running text.
These close SourceForge bug #115658.
Also:
Updated discussion of tuple unpacking to reflect the general ability
to unpack any sequence type. Explained that it is possible to create
tuples which contain mutable values, and noted in the dictionary
section that such tuples cannot be used as keys.
Noted that .pyc and .pyo files can be run directly when provided as
the script parameter to the interpreter, and slightly clarified
comments about using modules with only the byte compiled code.
Removed some XXX comments that are no longer relevant.
Removed commented-out paragraph about __private names being experimental.
Adjusted markup for consistency in some places.
|
|
|
|
|
|
|
|
|
|
| |
<file>.readlines() does not call <file>.readline() internally anymore,
and the sizehint parameter should be mentioned briefly.
Some displays of floating point numbers needed to be updated due to the
change in the repr() of floats (from 1.6).
Both issues were noted by Aahz <aahz@panix.com>.
|
|
|
|
|
|
| |
"name spaces".
Inconsistency noted by Keith Briggs <keith.briggs@bt.com>.
|
| |
|
|
|
|
| |
Further examples of list comprehensions.
|
| |
|
|
|
|
|
|
| |
http://sourceforge.net/patch/?func=detailpatch&patch_id=100654&group_id=5470
for details.
|
|
|
|
|
|
|
|
|
|
| |
certain.
Update the information about the mailing list, using the python.org
address instead of cwi.nl, and point to the pipermail archives. Also
update the daily average message count (at the risk of scaring people
off), using the mail archive at http://www.egroups.com/group/python-list
for the first half of 2000 for statistical information.
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Clarify some of the details of readline-related configuration.
|
| |
|
|
|
|
|
|
| |
explanation of why you'd want to use it.
Based on a question from Michael Simcich <msimcich@accesstools.com>.
|
|
|
|
|
| |
Tutorial information about Unicode strings in Python, with some markup
adjustments from FLD.
|
|
|
|
| |
<lipman@sphere.niddk.nih.gov>.
|
| |
|
| |
|
|
|
|
|
| |
module functions, to clarify that the import is not automatic.
Suggested by Koray Oner <Koray.Oner@Eng.Sun.COM>.
|
|
|
|
| |
pass can be used if needed. By Dan Wolfe <wolfeman@apple.com>.
|
|
|
|
|
|
|
|
| |
Barcla <danielb@digitalfocus.com>.
Also added example of what happens when a parameter is set both
positionally and by a keyword (one of Daniels suggestions related to
that paragraph).
|
|
|
|
| |
<BennettBenson@mn.mediaone.net>.
|
|
|
|
|
|
| |
appear in the examples without any further explanation, and the
tutorial doesn't have this information explicit anywhere else.
Omission reported by Jon Black <jblack@Ridgeway-Sys.com>.
|
| |
|
|
|
|
| |
by Mirko Liss <n89553@hrz.uni-paderborn.de>.
|
| |
|
|
|
|
| |
<dwr2@ix.netcom.com>.
|
| |
|
|
|
|
| |
Marc-Andre Lemburg.
|
|
|
|
|
| |
- add example of string literal concatenation
- add clarifying comment to the example of the if statement
|
|
|
|
| |
and what it doesn't apply to.
|
| |
|
|
|
|
| |
Blake Winton <BlakeW@pcdocs.com>.
|
| |
|
|
|
|
| |
values (4.7.1) should return l, not a. Reported by Axel Boldt.
|
|
|
|
|
|
| |
the KOE docs).
Some markup nits.
|
|
|
|
|
|
|
|
|
| |
with examples and workaround. This keeps coming up, and I believe
that this section in the tutorial may have been (in part) the source
of the confusion. While it didn't show examples with [] for a default,
it also didn't emphasize enough why that would be a bad idea, and
while it did say that defaults are evaluated at the point of function
definition, the example was not relevant for this issue.
|
| |
|
|
|
|
| |
change it to iterate over sys.argv[1:]. Suggestion by Gerry Wiener.
|
|
|
|
|
|
|
|
| |
The text is almost completely from GvR's essay on packages; some
introductory paragraphs have been removed, and everything after the
'Details' section in the HTML has been dropped (seems too technical). A
paragraph has been added after the sample package layout stating that there
must be a file called__init__.py in a directory to make it a package.
|
| |
|