Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow the readme to be included implicitly #99

Merged
merged 5 commits into from
Jan 8, 2021
Merged

Conversation

PeterJCLaw
Copy link
Contributor

@PeterJCLaw PeterJCLaw commented Apr 15, 2020

I'm hoping that this will get PyPI to use the README data from the metadata rather than from the README.md, which will mean it will pick up that it's markdown and so (hopefully) render it correctly.

The README files still get included in the sdist, so at worst I think this removes a redundant mention of it in the MANIFEST.in.

The plugins have READMEs in reStructuredText anyway, so the mention of a README.md in their MANIFEST.in was likely causing weirdness anyway.

I'm hoping that this will get PyPI to use the README data from the
metadata rather than from the README.md, which will mean it will
pick up that it's markdown and so (hopefully) render it correctly.

The README files still get included in the sdist, so at worst I
think this removes a redundant mention of it in the MANIFEST.in.

The plugins have READMEs in reStructuredText anyway, so the mention
of a README.md in their MANIFEST.in was likely causing weirdness
anyway.
@coveralls
Copy link

coveralls commented Apr 15, 2020

Coverage Status

Coverage remained the same at 99.459% when pulling 8efd83e on fix-readme-on-pypi into 21bdb41 on master.

While this means that the lint & typechecking jobs are isntalling
a bit more than they need, the consistency and simplicity of keeping
them in step feels worth it.
@PeterJCLaw PeterJCLaw merged commit a4d350a into master Jan 8, 2021
@PeterJCLaw PeterJCLaw deleted the fix-readme-on-pypi branch January 8, 2021 15:01
@PeterJCLaw
Copy link
Contributor Author

This didn't work as I missed the way that some of the requirements are specified. b4afed9 aims to fix that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants