RetroSearch Browse

Fri Jul 23 00:33:59 CEST 2010 · https://mail.python.org/pipermail/python-dev/2010-July/102240.html

On Fri, Jul 23, 2010 at 3:30 AM, Alexander Belopolsky
<alexander.belopolsky at gmail.com> wrote:
> I see three solutions:
>
> 1.  Minimal:  do not rename test_trace in 2.7 and add trace module
> tests to the existing file.  Whether to revert test_trace to
> test_line_tracing renaming in 3.2 can be decided after we have 2.7
> tests written.
> 2. Rename test_trace in 2.7/3.1 and test_line_tracing in 3.2 to
> test_sys_settrace.
> 3. Rename test_trace in 2.7/3.1 to test_line_tracing.
>
> My preference in #2, but I can live with #1  (assuming Eli is the one
> who will write the tests:-).

I'd say just fix it and go with #2 (just update the comment in
test_sys as well!)

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2010-July/102240.html below:

[Python-Dev] Does trace modules have a unit test?