-
Notifications
You must be signed in to change notification settings - Fork 55
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
fix pypi markdown parser #338
Comments
I've reviewed previous releases on pypi and it looks like parsing breaks between 0.9.2 and 0.10.0 - while I'm in the midst of looking for the root cause, an alternative solution is to write the readme as restructured text instead of markdown and skip the pandoc conversion altogether. Since GitHub can parse both anyway, is there any specific reason to stick with markdown? |
As much as having to do the pandoc conversion annoys me (quite a bit) I prefer markdown enough relative to rst to want the readme in markdown. All that's unimportant though! The Real Solution is here => pypi/warehouse#869 (comment) |
Hi Callisto and hi @lynncyrin! You can now directly upload an sdist containing your This does not work on pypi.python.org (legacy PyPI) which is going away probably by the end of April. And if you as maintainers have any trouble using or uploading to the new PyPI, please let us know! |
(I am still working on this draft explanation of what's new in the new PyPI but want to share it with you in this early form in case it helps or you have questions I could answer in it.) |
@brainwane thanks ^^ |
https://pypi.python.org/pypi/callisto-core <= the markdown there is very clearly not parsed!
The text was updated successfully, but these errors were encountered: