Olivier Grisel nous écrivait précédemment:
Stefan Behnel a écrit :
Right, I always had them in MANIFEST.in, but actually, they are package data.
On the other hand:
These files are really part of the test suite. Maybe the right question here is: why is the test suite part of the eggs at all? Eggs are supposed to be installed into "python/site-packages". No-one needs the test suite there.
So I think we should check if we can't remove the test suite from the eggs.
Yes + the fact that 'package_data' is 2.4 specific and would have broken the 2.3 compat.
So I removed the tests out of the egg (in trunk and the 0.9.x branch). I use that egg on my system and everything seems to work (362 tests ok).
Thanks. I think if people want to run the test suite, they either
1) have the tar ball anyway since they are building binaries
2) are interested in getting bugs fixed and can therefore be expected to accept downloading the tar ball separately to run it.
I just added a note on that on the install page.
BTW: Since this does not have any impact on end-users, I don't think this is already worth a 0.9.1 -- although it may give us the chance to shrink the size of the Linux egg.