-
Notifications
You must be signed in to change notification settings - Fork 395
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
PyPI Readme Rendering #1081
Comments
Thanks a lot for reporting this issue. Your suspicion appears to be correct. We do a check in our deployment script for this exact thing: Line 66 in 5bd84bd
I just ran this and it reports the same error as you mentioned. It is a bit strange that we didn't catch that in the last release, maybe the renderer was changed after that? Let me know if you're interested in providing a PR to fix the issue, this would be really great. |
I would happily draft a PR in the next few days. I am checking the docs to see if there is anything specific I need to know before doing so, or feel free to give me explicit pointers about it. I am also including the explicit content type metadata. We may discuss further these details in the PR thread. |
@Ball-Man Are you still interested in working on this?
No, I don't think that apart from your suggested change, there is anything that needs to be considered. We can ensure that the docs render correctly by invoking |
Yes, I am sorry about the delay for such a quick fix. I was back today from winter holidays. I can probably submit the PR tonight or tomorrow (UTC + 1). |
Fantastic, thanks a lot. This was just intended as a reminder, don't feel pressured. |
Issue #1081: Fix PyPI Readme Rendering
Hello,
I wanted to notify that the PyPI page of skorch is not rendering correctly. In fact, it looks like it the long description is being treated as plain text, while it is actually an rst document.
The problem
I did investigate this on a private fork, and by running a twine check this is what I get:
I did notice myself that
long_description_content_type
is missing. It may or may not be a good idea to make it explicit, even though it is inferred automatically by the renderer.The real problem seems to be related to image scaling, in particular of the badges (coverage, etc.). It looks like this is a common issue, notified earlier this year by other devs (pypa/twine#1102). The issue has reached the actual readme_rendered devs (pypa/readme_renderer#304) but it looks like it still remains unsolved.
A possible solution
What some of the devs in the cited threads suggest, is to remove scaling from the badges. I tried this solution on my fork, and it does solve the rendering issue. I still get some artifacts, but it may be related to the fact that I was testing on TestPyPI.
A practical example:
My fork on GitHub shows that there is no difference in the visualization of the badges without the explicit scaling factor (at least, not on my desktop): https://github.com/Ball-Man/skorch/tree/no_scaling_readme.
If this is of interested, I can quickly apply draft a PR using this branch.
The text was updated successfully, but these errors were encountered: