Skip to content

Support markdown in description #238

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
wants to merge 3 commits into from
Closed

Conversation

techtonik
Copy link

@techtonik
Copy link
Author

I don't get what is the purpose of setup.cfg if you still have to double write deps into setup.py

@dstufft
Copy link
Member

dstufft commented Mar 29, 2014

setup.cfg controls what goes into the Wheel, it's a bit of a hack ATM tbh.

I'm going to close this, thanks for the PR but I think this needs to wait for the standards to catch up and allow specifying which markup rendering should be selected. I had thought about doing it similarly to that, but this only covers the markdown which doesn't render as rst. It does nothing for the markdown which renders as ugly rst. Nor does it allow future expansion into other rendering engines like asciidoc or even plain html.

Thanks again though!

@dstufft dstufft closed this Mar 29, 2014
@techtonik
Copy link
Author

Is it possible to enable explicit per-project setting (beta markdown support)? It seems the only possible way for me in this case.

@UlionTse
Copy link

I also think it is popular to use with markdown, not reStructuredText.
For example, Github.
The reStructuredText makes me depressed !

@di
Copy link
Member

di commented Mar 14, 2018

@shinalone See #869, this is in progress.

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

Successfully merging this pull request may close these issues.

4 participants