Jack Jansen [Fri, 25 Oct 2002 20:06:29 +0000 (20:06 +0000)]
Under Jaguar it seems that 'errn' return value keyword parameters don't
(or don't always?) show up with missed(). I think this is a bug in
Jaguar, but as it is a potential dangerous problem (the OSA event has
failed, but the Python code isn't told about this and happily continues)
this is a quick workaround.
Bugfix candidate, I'll add it to 2.2.2 as a last second fix.
Fred Drake [Fri, 25 Oct 2002 18:08:18 +0000 (18:08 +0000)]
Re-factor: Use a RawConfigParser base class and make ConfigParser a
derived class that adds the ugly string interpolation code. In the
process, changed all "__" methods and instance variables to "_".
Fred Drake [Thu, 24 Oct 2002 19:36:04 +0000 (19:36 +0000)]
Update an example to use the DOM implementation object. Explain that
the parse() and parseString() functions use a separate parser, not
actually implement a parser. (This is a common question.)
Kurt B. Kaiser [Wed, 23 Oct 2002 04:48:08 +0000 (04:48 +0000)]
Implement Restoring Breakpoints in Subprocess Debugger
M Debugger.py
M EditorWindow.py
M PyShell.py
0. Polish PyShell.linecache_checkcache()
1. Move break clearing code to PyShell.PyShellEditorWindow from
EditorWindow.
2. Add PyShellEditorWindow.breakpoints attribute to __init__, a list of
line numbers which are breakpoints for that edit window.
3. Remove the code in Debugger which removes all module breakpoints when
debugger is closed. Want to be able to reload into debugger when
restarted.
4. Moved the code which sets EditorWindow.text breakpoints from Debugger
to PyShell.PyShellEditorWindow and refactored.
5. Implement reloading subprocess debugger with breakpoints from all open
PyShellEditorWindows when debugger is opened or subprocess restarted.
6. Eliminate the break_set attribute, use the breakpoint list instead.
Replaces the _center function in the calendar
module with the center method for strings.
For situations with uneven padding, the behavior is
slightly different in that the center method puts the
extra space on the right instead of the left.
Barry Warsaw [Mon, 21 Oct 2002 15:58:29 +0000 (15:58 +0000)]
(py-parse-state-re): Remove the "if" from the regular expression.
This fixes an indentation bug reported by Jeremy when seeing multiple
list comprehensions like so:
[x for x in seq
if blah(x)]
# ...
[y for y in seq
if blah(y)]
The reason this broke is because this regexp caused the "find a safe
parsing start location higher up in the file" test to erroneously find
the if in the listcomp. I think the other keywords in this regexp are
fine and good enough.
After a weekend of testing, I can't find any adverse effects.
Barry Warsaw [Mon, 21 Oct 2002 05:29:53 +0000 (05:29 +0000)]
body_encode(): Fixed typo reported by Chris Lawrence, closing SF bug
#625509. This isn't a huge problem because at the moment there are no
built-in charsets for which header_encoding is QP but body_encoding is
not.
Neal Norwitz [Fri, 18 Oct 2002 02:05:47 +0000 (02:05 +0000)]
Try to fix the broken links caused by multiple \ref on the same line.
SF bug #217195.
Not sure if chomp() is correct, but chop() definitely has problems.
This change seems to have no ill effects.
Fred Drake [Thu, 17 Oct 2002 22:09:03 +0000 (22:09 +0000)]
Don't call warnings.resetwarnings(); that does bad things that cause
other tests to generate warning when they didn't before. In
particular, this cancels not only filters set by -W, but also from
test.regrtest.
Guido van Rossum [Wed, 16 Oct 2002 16:52:11 +0000 (16:52 +0000)]
posix_execve(): add missing argument for "et" format in PyArg_Parse()
call. This caused mysterious crashes (hard to debug because it was
happening in a child process).
Guido van Rossum [Tue, 15 Oct 2002 01:01:53 +0000 (01:01 +0000)]
For some reason (probably cut and paste), __ipow__ for new-style
classes was called with three arguments. This makes no sense, there's
no way to pass in the "modulo" 3rd argument as for __pow__, and
classic classes don't do this. [SF bug 620179]
I don't want to backport this to 2.2.2, because it could break
existing code that has developed a work-around. Code in 2.2.2 that
wants to use __ipow__ and wants to be forward compatible with 2.3
should be written like this: