| 1 |
On Mon, Feb 4, 2013 at 1:59 AM, IAN DELANEY <della5@×××××××××.au> wrote: |
| 2 |
> Given that this is a relatively common error, let's get a 'clear |
| 3 |
> picture' of the status of the presence of the relatively common |
| 4 |
> instance test folders and suites in python packages. There are some |
| 5 |
> that install them and some that don't, so we're forced to chase a |
| 6 |
> 'moving target'. Can we decide categorically that test suites need and |
| 7 |
> ought not be installed in python packages, or do we have to water it |
| 8 |
> down with "Oh it depends on these dozens of possibilities and those |
| 9 |
> ones over there"? This creates a myriad of scenarios of uncertainty. |
| 10 |
> |
| 11 |
|
| 12 |
This is not about whether or not installing tests is valid. It is |
| 13 |
about preventing file collisions by slapping developers in the face |
| 14 |
when they forget to check. |
| 15 |
|
| 16 |
If you want to propose some greater policy about installing tests, |
| 17 |
please start a new thread and make your argument. |
Archives