pythonpython-hyper/h11 #158Not a task: already works

Remove test files when publishing package

envgap__python-hyper__h11-158

Original GitHub issue ↗Dated source checkout ↗Opened 2023-04-02

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.

Not a benchmark task.

The project already builds and runs before the fix, so there is nothing to repair.

02 / ENVIRONMENT RECIPE

Base commit: d6f470e144da8df924f0f1cd478207e013c3ad22
Manifest: setup.py
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

python-hyper/h11 #158 · read the original issue

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:



https://github.com/python-hyper/h11/blob/cdccbeff44a39426b58010eb454a75015ec6f8bc/setup.py#L18-L20



and in the manifest file:



https://github.com/python-hyper/h11/blob/cdccbeff44a39426b58010eb454a75015ec6f8bc/MANIFEST.in#L3



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).

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched

[]