Skip to content

Markdown formatting not applied to PyPi page? #121

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

Closed
itsderek23 opened this issue Aug 27, 2018 · 5 comments
Closed

Markdown formatting not applied to PyPi page? #121

itsderek23 opened this issue Aug 27, 2018 · 5 comments

Comments

@itsderek23
Copy link
Contributor

It looks like Markdown formatting is applied to the PyPi listing for scout-apm:

image

@itsderek23 itsderek23 changed the title Markdown formatting not applied to PyPi text? Markdown formatting not applied to PyPi page? Aug 27, 2018
@dlanderson
Copy link
Contributor

This seemed to happen after releasing wheel builds. According to

The Markdown description should be showing correctly. I checked:

  • The METADATA in the wheel files specify Metadata-Version: 2.1 and Description-Content-Type: text/markdown
  • Wheel files do not contain a DESCRIPTION file
  • The version of twine used to upload is 1.11 (show in the travis build logs)

@dlanderson
Copy link
Contributor

d05a94f added explicit install/upgrade to setuptools and wheel. https://dustingram.com/articles/2018/03/16/markdown-descriptions-on-pypi specifies needing setuptools >= 38.6.0 and wheel >= 0.31.0. After the explicit install/upgrade of setuptools and wheel in travis it shows:

Installing collected packages: setuptools, wheel, enum34, bashlex, cibuildwheel
  Found existing installation: setuptools 38.2.4
    Uninstalling setuptools-38.2.4:
      Successfully uninstalled setuptools-38.2.4
  Found existing installation: wheel 0.30.0
    Uninstalling wheel-0.30.0:
      Successfully uninstalled wheel-0.30.0
Successfully installed bashlex-0.12 cibuildwheel-0.9.4 enum34-1.1.6 setuptools-40.2.0 wheel-0.31.1

So we'll see if this is fixed when the next release goes out.

@itsderek23
Copy link
Contributor Author

itsderek23 commented Aug 27, 2018 via email

@dlanderson
Copy link
Contributor

Appears to be fixed.

@itsderek23
Copy link
Contributor Author

itsderek23 commented Aug 27, 2018 via email

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

No branches or pull requests

2 participants