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
When doing python3 setup.py install on a local checkout of the code, files from git/test will be installed into the standard site-packages directory.
This mean that theoretically even the requirements from test-requirements.txt are mandatory for the base package and secondly it isn't necessary as the chances that an user is actually using the test code are pretty low.
So overall it doesn't make much sense to me.
Is there any way to avoid having the test files installed via setuptools?
I'm pretty sure that this is possible - I think it requires just some magic in setup.py and the MANIFEST.in.
BTW I think the tests itself should be in the root directory rather than a subdir of the module itself - is there a reason for them being placed where they are right now?
Activity
Byron commentedon Jul 7, 2020
Thanks for bringing this up! I agree with the sentiment and believe it would be preferable not to package and install test files.
Maybe these can be excluded during packaging? Help is greatly appreciated, as I only remember the incredible pain that
setup.pyinflicted on me.priv-kweihmann commentedon Jul 8, 2020
I'm pretty sure that this is possible - I think it requires just some magic in setup.py and the MANIFEST.in.
BTW I think the tests itself should be in the root directory rather than a subdir of the module itself - is there a reason for them being placed where they are right now?
I'll see if I could come up with a PR for it