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.

Author eric.araujo
Recipients eric.araujo, ezio.melotti, francismb, nadeem.vawda, tshepang
Date 2012-02-22.12:55:14
SpamBayes Score 0.00080153765
Marked as misclassified No
Message-id <1329915315.37.0.173475412033.issue13447@psf.upfronthosting.co.za>
In-reply-to
Content
I went for something even simpler: one new file Lib/test/test_tools.py.  There is no need to have a file there and more files in Tools/tests, everything can go in test_tools (I’m not worried about file size, we already have a few thousand-liners test modules).  I think it’s the simplest thing that works.

My only concern is communication: how do we tell people working on a tool that they should write a test in test_tools?  I’m not sure they would read Tools/README; maybe a note at the top of the Python files would work; a note in the devguide; sending an email to python-dev to tell about the new file + reminders when we see a new tool bug opened.
History
Date User Action Args
2012-02-22 12:55:15eric.araujosetrecipients: + eric.araujo, nadeem.vawda, ezio.melotti, tshepang, francismb
2012-02-22 12:55:15eric.araujosetmessageid: <1329915315.37.0.173475412033.issue13447@psf.upfronthosting.co.za>
2012-02-22 12:55:14eric.araujolinkissue13447 messages
2012-02-22 12:55:14eric.araujocreate