Fred Drake [Thu, 11 Nov 2004 05:04:55 +0000 (05:04 +0000)]
Replace last two uses of the "list" environment with "description"
environments.
Closes SF bug #692442: Konqueror can't render docs because of
malformed HTML. While the generated HTML is still terrible, the cited
cases of <DL COMPACT> have been removed. The general problem of XHTML
conformance has not been solved, but is endemic to LaTeX2HTML output.
Fred Drake [Wed, 10 Nov 2004 15:37:54 +0000 (15:37 +0000)]
move much of the table styling out of the HTML and into the CSS;
this also makes some constructs more XHTML friendly (including adding in
some missing </tr> tags)
Tim Peters [Mon, 8 Nov 2004 22:07:37 +0000 (22:07 +0000)]
test_doctest.py test_pdb_set_trace_nested(): A new test from Jim Fulton
showing that doctest's pdb.set_trace() support was dramatically broken.
doctest.py _OutputRedirectingPdb.trace_dispatch(): Return a local trace
function instead of (implicitly) None. Else interaction with pdb was
bizarre, noticing only 'call' events. Amazingly, the existing set_trace()
tests didn't care.
Tim Peters [Mon, 8 Nov 2004 04:30:21 +0000 (04:30 +0000)]
SF bug 1061968: threads: segfault or Py_FatalError at exit
PyGILState_Ensure(): The fix in 2.4a3 for bug 1010677 reintroduced thread
shutdown race bug 225673. Repaired by (once again) ensuring the GIL is
held whenever deleting a thread state.
Alas, there's no useful test case for this shy bug. Four years ago, only
Guido could provoke it, on his box, and today only Armin can provoke it
on his box. I've never been able to provoke it (but not for lack of
trying!).
This is a critical fix for 2.3.5 too, since the fix for 1010677 got
backported there already and so also reintroduced 225673. I don't intend to
backport this fix. For whoever (if anyone) does, there are other thread
fixes in 2.4 that need backporting too, and I bet they need to happen first
for this patch to apply cleanly.
Patch #1061931 / bug #971872: factor out part of spillproperties, so
properties are also documented if help(Class.<property>) is called
instead of help(Class).
Clarify that it's not necessary to subclass from TestCase to create a
test case. As Jeremy put it: "subclassing is an implementation
technique, not a type declaration".
memset() wrote one past the end of the buffer, which was likely to be unused padding or a yet-to-be-initialized local variable. This routine is already tested by test_socket.
Brett Cannon [Sun, 7 Nov 2004 01:24:12 +0000 (01:24 +0000)]
Move the AC_MSG_RESULT function call for checking for pthread options up into
the 'if' statement that performed the test. Not all platforms run the test and
on those tests configure outputted a rogue 'no' line.
Brett Cannon [Sun, 7 Nov 2004 01:19:00 +0000 (01:19 +0000)]
Add comment about removal of CoreServices/CoreFoundation compilation against
the core on OS X (also specifically mention removal of
PyMac_GetAppletScriptFile() ).
SF patch #1035255: Remove CoreServices / CoreFoundation dependencies in core
(Contributed by Bob Ippolito.)
This patch trims down the Python core on Darwin by making it
independent of CoreFoundation and CoreServices. It does this by:
Changed linker flags in configure/configure.in
Removed the unused PyMac_GetAppletScriptFile
Moved the implementation of PyMac_StrError to the MacOS module
Moved the implementation of PyMac_GetFullPathname to the
Carbon.File module
Armin Rigo [Thu, 4 Nov 2004 11:29:09 +0000 (11:29 +0000)]
Mistakes in the "sequence types" page:
* explanation for example with lists of lists made confusing use of
the word "contains" to mean "is built out of".
* wrong formula for slices with step. Is it ok to use LaTeX formulas
(which become images in the html document)? This version needs one
because it's based on a fraction. Just writing "\code{(j-i)/k}" here would
be ambiguous because it looks like a rounding-down-to-the-previous-integer
division, which is not what we need here. Of course we could write
"\code{float(j-i)/k}" but it just looks confusing.
* Bumped up the sleep() delay to four seconds so this test will run
reliably on WinME with FAT32.
* Native speaker rewrite of the comment block.
* Removed unnecessary backslashes from the multi-line function defintions.
Tim Peters [Mon, 1 Nov 2004 16:39:57 +0000 (16:39 +0000)]
gc_list_move(): Make this truly equivalent to remove+append. While
nothing in gc currently cares, the original coding could screw up if,
e.g., you tried to move a node to the list it's already in, and the node
was already the last in its list.
Barry Warsaw [Mon, 1 Nov 2004 03:52:43 +0000 (03:52 +0000)]
SF patch #1056967, changes the semantics of Template.safe_substitute() to not
raise a ValueError for dangling delimiters (the delimiter itself is returned).
Tim Peters [Mon, 1 Nov 2004 01:39:08 +0000 (01:39 +0000)]
gc list function cleanup.
Introduced gc_list_move(), which captures the common gc_list_remove() +
gc_list_append() sequence. In fact, no uses of gc_list_append() remained
(they were all in a gc_list_move() sequence), so commented that one out.
gc_list_merge(): assert that `from` != `to`; that was an implicit
precondition, now verified in a debug build.