Remove test files when publishing package

[dosisod]

I was poking around my .venv folder and noticed h11 includes the test/ folder in it's published packages. Is this intentional? The setup.py and MANIFEST.in file seem to indicate that the tests should be added, but I don't see any explanation as to why:

h11/setup.py

Lines 18 to 20 in cdccbef

	# This means, just install *everything* you see under h11/, even if it
	# doesn't look like a source file, so long as it appears in MANIFEST.in:
	include_package_data=True,

and in the manifest file:

h11/MANIFEST.in

Line 3 in cdccbef

recursive-include h11/tests/data *

Normally tests are only for development purposes and have no use to the client, so including the test folder just takes up space. Unless I am missing something, I think we can remove this folder (I wouldn't mind opening a PR for this, just though I would ask before doing so).

[GalaxySnail]

It may not be a good idea to remove tests (and also documentations) from sdists. Here are some reasons:

• https://discuss.python.org/t/should-sdists-include-docs-and-tests/14578/115
• https://discuss.python.org/t/sdists-for-pure-python-projects/25191/10

IMO it should be fine to remove tests from wheels and keep them in sdists, but I don't know how to do it.

[dosisod]

I agree with that tests and docs should stay in the sdists. I haven't double checked this, but I believe the setup.py file dictates what files are included in the wheel files, and the MANIFEST.in file dictates what goes in the sdist (according to this post on stack overflow).

I assume that the include_package_data flag in the setup.py file is needed to include the py.typed file, so perhaps we can configure exclude_package_data to exclude the h11/test folder?