New submission from Chris Lambacher :
I am building OpenEmbedded packages for a number of Python Packages and
therefore using --single-version-externally managed. __init__.py in the tests
directory ends up conflicting with other packages (I'll submit a bug report to
them as well). The tests shoul
Tres Seaver added the comment:
I don't think there are any other repoze.* packages except for repoze.what that
follow the "tests outside the package" pattern.
My preferred fix would be to move the repoze.what tests into a sub-package of
repoze.what.
--
assignedto: -> Gustavo
nosy: +Gu
Chris Lambacher added the comment:
It was specifically repoze.what.plugins.sa that was causing a problem for me,
but there may be other's that I have not run into yet. Moving the tests as a
sub-package would certainly make it more package manager friendly.
For my case, I will probably still ex
Gustavo Narea added the comment:
Even though the test suite was not included anyway thanks to the MANIFEST.in
file, I just added the `exclude' argument to exclude it from the package
metadata and released it to PYPI.
I like not including the tests and the documentation in the final distribution
On 3/10/10 9:59 AM, Andrey Popp wrote:
>> The context of such an "exception view" will be the exception instance
>> itself. If you want a particular exception to be able to use a "real"
>> context, you'll make it available as an attribute of the exception for use
>> by the registered exception vie
