adding initial MANIFEST.in

[mahmoud]

Adding a MANIFEST.in to include a few files (LICENSE, README, docs). Not sure if there's a python-hyper standard approach to this, so feedback is welcome!

[codecov-io]

Codecov Report

Merging #33 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #33   +/-   ##
======================================
  Coverage    97.6%   97.6%           
======================================
  Files           6       6           
  Lines        1044    1044           
  Branches      120     120           
======================================
  Hits         1019    1019           
  Misses         13      13           
  Partials       12      12

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a510e8d...eea7687. Read the comment docs.

[alexwlchan]

python-hyper “standard”, insofar as there is one, is to include everything from the repo in the sdist that might be useful – see python-hyper/h2#501

(On a phone, so can’t double-check the proposed MANIFEST.in against the repo contents right now.)

[Lukasa]

Yeah, so my strong recommendation would be to add the testing from python-hyper/h2#501 to validate that the Manifest just basically contains the entire git repo. This seems to be what's most popular with downstream repackagers.

However, if you don't want to do that, that's fine. Just let me know and I'll review with that in mind.

[mahmoud]

Alright, python-hyper/h2#501 is fully implemented. Added more files, plus the check-manifest in a packaging tox env. Thanks for the advice and review!

[alexwlchan]

Don’t forget to add the new test to CI.

[Lukasa]

Yup, per @alexwlchan's note we should add the new test env to the CI. 😁

[Lukasa]

Cool, assuming we get a green test run we can go ahead and merge this.

[alexwlchan]

🎉