This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: trace.py: simple bug in write_results_file
Type: Stage:
Components: Library (Lib) Versions:
process
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: Nosy List: nicoddemus, rhettinger
Priority: normal Keywords: patch

Created on 2004-01-08 18:07 by nicoddemus, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
trace.patch nicoddemus, 2004-01-08 18:07
Messages (2)
msg45208 - (view) Author: Bruno da Silva de Oliveira (nicoddemus) * Date: 2004-01-08 18:07
The callers of write_results_file expect it to return a 
tuple (n_lines, n_hits), but right at the beginning of the 
function there's an attempt to open the results file, and 
if that fails it just "return"s, which causes an exception 
in the callers when they try to unpack the tuple.
msg45209 - (view) Author: Raymond Hettinger (rhettinger) * (Python committer) Date: 2004-03-13 21:08
Logged In: YES 
user_id=80475

The time machine beat you to this one.  Guido already fixed
this on Feb 19, 2004.
History
Date User Action Args
2022-04-11 14:56:02adminsetgithub: 39789
2004-01-08 18:07:10nicoddemuscreate