You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 18, 2018. It is now read-only.
The tests directory currently isn't included in the manifest file and releases. As the tests can be quite useful for distributions packaging your software (testing for regressions), could you include it in the releases? Also, changing setup.py so that the tests are automatically run when you call 'setup.py test' would be a nice addition.
Thanks!
The text was updated successfully, but these errors were encountered:
I'm not too familiar with package distributions but from what I understand, isn't that akin to including the "source" with the package? Don't we typically want to exclude tests/source from a production package? Not saying its a bad idea but I don't know how to include tests/ on the top level without having it create a "tests" module discoverable in PYTHONPATH. Ideas?
I think it's possible to do using setuptools. You include the tests directory, but when setup.py install is called it doesn't install the directory. Anything you add to the manifest doesn't get installed by default as far as I know, but I haven't tried it yet.
Hi,
The tests directory currently isn't included in the manifest file and releases. As the tests can be quite useful for distributions packaging your software (testing for regressions), could you include it in the releases? Also, changing setup.py so that the tests are automatically run when you call 'setup.py test' would be a nice addition.
Thanks!
The text was updated successfully, but these errors were encountered: