Tim Peters [Mon, 21 Jul 2003 14:25:23 +0000 (14:25 +0000)]
Merge 23c1-branch back into the head. Barry will send email about the
New Plan (releases to be made off the head, ongoing random 2.4 stuff
to be done on a short-lived branch, provided anyone is motivated enough
to create one).
Change \code to \verb, because TeX merges the two dashes into a
hyphen, resulting in the output '-list-classifiers', not the correct
'--list-classifiers'. I've verified that the line is now correct
in the DVI, PDF, HTML, and ASCII versions.
Jeremy Hylton [Fri, 18 Jul 2003 03:19:20 +0000 (03:19 +0000)]
Restore the locale to "C" on exit.
If this doesn't happen, it leaves the locale in a state that can cause
other tests to fail. For example, running test_strptime,
test_logging, and test_time in that order.
Add introductory paragraphs
Remove comment about MacOS changes; I'm not going to have time to figure
out what they are
Move PEP 273 section into numeric order
Jeremy Hylton [Thu, 17 Jul 2003 16:58:48 +0000 (16:58 +0000)]
Get socketmodule compiling on IRIX 6.5.10.
I don't think the fix here is very good, but I'm not sure what would
be better. In particular, we should not be defining _SGIAPI, but lots
of things break if we remove it.
Fred Drake [Thu, 17 Jul 2003 15:22:47 +0000 (15:22 +0000)]
- remove mention of the isprivate flag, since that isn't directly
documented here, and according to Tim, should never have been there
- misc. cleanups for consistency
Fred Drake [Thu, 17 Jul 2003 05:26:53 +0000 (05:26 +0000)]
- improve the description of how user-defined method
objects get made
- improve the description of attribute retrieval from
classes and class instances
- add brief documentation of static method and
class method objects.
expose the C API subsection which was hidden from LaTeX in a comment. In
the info conversion the \comment LaTeX macro mapped to a Texinfo @ignore
macro. Unfortunately, py2texi.el is not smart enough to avoid generating
links to the @ignore'd section, which causes makeinfo to croak.
Exposing this text is probably not the most correct thing to do, as this
documentation really belongs in the C API manual. This does get the info
files generated, however, which is a more practical goal considering the
impending release of 2.3rc1.
Doctest now examines all docstrings by default. Previously, it would
skip over functions with private names (as indicated by the underscore
naming convention). The old default created too much of a risk that
user tests were being skipped inadvertently. Note, this change could
break code in the unlikely case that someone had intentionally put
failing tests in the docstrings of private functions. The breakage
is easily fixable by specifying the old behavior when calling testmod()
or Tester(). The more likely case is that the silent failure was
unintended and that the user needed to be informed so the test could be
fixed.
Fred Drake [Wed, 16 Jul 2003 16:19:08 +0000 (16:19 +0000)]
Remove \versionchanged; the text was too complex for the GNU info
conversion to support. Keep the content as normal content, with a
note that this applies starting in Python 2.3.
Jeremy Hylton [Wed, 16 Jul 2003 16:08:23 +0000 (16:08 +0000)]
Remove unnecessary check in tests for slots allowed.
The !PyType_Check(base) check snuck in as part of rev 2.215, but was
unrelated to the SF patch that is mentioned in the checkin comment.
The test is currently unnecessary because base is set to the return
value of best_bases(), which returns a type or NULL.
Exercise Jim Fulton's new doctest extension for running doctests in a
unittest environment. Since his extension finds docstrings in private
functions, it exposed a bug in the difflib doctests.
Fred Drake [Wed, 16 Jul 2003 03:26:31 +0000 (03:26 +0000)]
In the description of enumerate(), the indexing operators should not
be included in the \var. This produced weird results in general, but
broke the GNU info conversion.
Kurt B. Kaiser [Wed, 16 Jul 2003 03:10:43 +0000 (03:10 +0000)]
Update to reflect the current status of the configuration system.
Extensions must still be configured manually and there is currently one
set of extension key bindings for all platforms.
Bring NEWS.txt up to date.
Update CREDITS.txt and idlever.py for release.
M NEWS.txt
M config-extensions.def
M extend.txt
M help.txt
M idlever.py
Mark Hammond [Tue, 15 Jul 2003 23:03:55 +0000 (23:03 +0000)]
Fix [ 771097 ] frozen programs fail due to implicit import of "warnings".
If the initial import of warnings fails, clear the error. When the module
is actually needed, if the original import failed, see if it has managed
to find its way to sys.modules yet and if so, remember it.
Jeremy Hylton [Tue, 15 Jul 2003 20:23:26 +0000 (20:23 +0000)]
SF patch 763201: handling of SyntaxErrors in symbol table build
Fixes for three related bugs, including errors that caused a script to
be ignored without printing an error message. The key problem was a bad
interaction between syntax warnings and syntax errors. If an
exception was already set when a warning was issued, the warning could
clobber the exception.
The PyErr_Occurred() check in issue_warning() isn't entirely
satisfying (the caller should know whether there was already an
error), but a better solution isn't immediately obvious.
Fred Drake [Mon, 14 Jul 2003 21:46:23 +0000 (21:46 +0000)]
Remove proxy_print(), since that caused an inconsistency between
"print repr(proxy(a))" and "proxy(a)" at an interactive prompt.
Closes SF bug #722763.