-
Notifications
You must be signed in to change notification settings - Fork 90
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
twine check
fails when badges have a scale factor ...
#304
Comments
Please provide a concrete reference to a readme that contains the problematic behavior - it's unclear from the linked issue which conditions lead to the problem. |
Related to pypa/readme_renderer#304
From https://github.com/PhasesResearchLab/ESPEI
Gives output:
|
Thanks for the error message, that points out a warning from We have disabled the ability to read external files, which prevents docutils from trying to load images to scale these. See: readme_renderer/readme_renderer/rst.py Lines 68 to 71 in 1d0497c
I haven't looked too hard yet for what alternatives might be avilable, or if there's a way to only allow images, but now there's a reason. |
PyPI does not allow file insertion for security reasons. See pypa/readme_renderer#304 (comment)
PyPI does not allow file insertion for security reasons. See pypa/readme_renderer#304 (comment)
This is actually a blocker to upload a new release for my project. Could this be non fatal maybe (as it used to be)? E.g. just do not render the image in that case. We just display a scaled logo in our readme. I think it is a fairly common use case. Is the inclusion of external files considered a security risk? I'd love to hear your opinion on that @miketheman, thank you. |
Scaling of these images is not supported by the readme_renderer used by the PyPI. See pypa/twine#1102 and pypa/readme_renderer#304.
As reported in:
pypa/twine#1102
twine check
fails when parsing thereadme
file contains badges. If one of the badge has a scale factor, thereadme_renderer
fails claiming it is not allowed to access to the internet.The text was updated successfully, but these errors were encountered: