Message153978
| Author | francismb |
|---|---|
| Recipients | eric.araujo, eric.snow, ezio.melotti, francismb, nadeem.vawda, tshepang |
| Date | 2012-02-22.18:01:02 |
| SpamBayes Score | 0.00011287805 |
| Marked as misclassified | No |
| Message-id | <4F452DB3.60301@email.de> |
| In-reply-to | <1329915315.37.0.173475412033.issue13447@psf.upfronthosting.co.za> |
| Content | |
|---|---|
> 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. Patch patchcheck to "check" ;-) if some file in Tool/** has been touched and give a message accordingly (that happens already for NEWS and ACKS) … |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012-02-22 18:01:03 | francismb | set | recipients: + francismb, nadeem.vawda, ezio.melotti, eric.araujo, tshepang, eric.snow |
| 2012-02-22 18:01:03 | francismb | link | issue13447 messages |
| 2012-02-22 18:01:02 | francismb | create | |