Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey there,
While setting up a Scrapy-based project, I noticed the source tarball for Protego on PyPI is 3.2 megabytes, due to including all of the test case robots.txt files too. This is, based on the MANIFEST.in file, on purpose:
protego/MANIFEST.in
Line 7 in 26a5b11
Some distros (e.g. Debian) do like their upstream source tarballs to include test material, so that's fine.
Those test files don't get included in wheel packages though, bringing the package size to a more reasonable 8 kilobytes. Pip will generally prefer wheels over source distributions so this is an easy way to bring the download size down for everyone.
This PR adds the required
universal = 1
configuration tosetup.cfg
so the wheel is marked compatible with both Python 2 and Python 3.However, I'm not sure what the release process here entails; I see some deployment bits in the Travis configuration file, but I don't know what to add there to have the CI pipeline run
python setup.py bdist_wheel
.