Showing content from http://mail.python.org/pipermail/python-dev/attachments/20100719/82adb24f/attachment-0001.html below:
<div dir="ltr"><div class="gmail_quote">On Mon, Jul 19, 2010 at 07:02, Terry Reedy <span dir="ltr"><<a href="mailto:tjreedy@udel.edu">tjreedy@udel.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
In reviewing<br>
<a href="http://bugs.python.org/issue9282" target="_blank">http://bugs.python.org/issue9282</a><br>
the issue came up, where is the unit test for trace.py?<br>
<br>
test/test_trace.py is actually a test of the line trace facility of sys.settrace (and should have been called test_linetrace or test_settrace). The only trace import Eli could find in Lib/test is the one in regrtest.py for the -T option. Have we missed something?<br>
<br>
If you say 'make one', what should be its name? Can the existing file be renamed (I gather this can be a bit of a problem)?<font color="#888888"></font><br></blockquote></div><br>I'd like to ask pydev another question on this issue. When thinking about adding unit tests for trace.py, I quickly realized it's not a usual module. Most of its output is either tracing reports to stdout, or even worse, to special files named <modname>.cover<br>
<br>stdout output can be captured, but what about the .cover files? Can a Python unit test create temporary files in tmp/ (or somewhere else) as part of its testing, or is this forbidden?<br><br>Eli<br><br></div>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4