Re: [Distutils] Basic Markdown Readme Support

> On May 3, 2016, at 9:47 AM, Nick Coghlan wrote: > > On 3 May 2016 at 23:18, Fred Drake wrote: >> My perspective, for what it's worth, is that while I find Markdown a >> horrible pain, there are a lot of people who pick it up before picking >> up Python,

Re: [Distutils] Basic Markdown Readme Support

On Tue, 3 May 2016, Jim Fulton wrote: In my last job, I had to use a suite of tools (from a single company that I won't name but is easy to guess :) ) for which no 2 tools used the same dialect of Markdown. :( Which begs the question, which dialect of Markdown are you suggesting we support. :)

Re: [Distutils] Basic Markdown Readme Support

On Tue, May 3, 2016 at 9:29 AM, Jim Fulton wrote: > But wait, it's worse. Unlike ReStructuredText, there's no Markdown standard. We agree that this is a problem, and it's why I don't use Markdown when tools don't force it. > In my last job, I had to use a suite of tools

Re: [Distutils] Basic Markdown Readme Support

On 3 May 2016 at 23:18, Fred Drake wrote: > My perspective, for what it's worth, is that while I find Markdown a > horrible pain, there are a lot of people who pick it up before picking > up Python, and tools like GitHub and BitBucket encourage (and make it > easier to add)

Re: [Distutils] Basic Markdown Readme Support

On 3 May 2016 at 14:18, Fred Drake wrote: > My perspective, for what it's worth, is that while I find Markdown a > horrible pain, there are a lot of people who pick it up before picking > up Python, and tools like GitHub and BitBucket encourage (and make it > easier to add)

Re: [Distutils] Basic Markdown Readme Support

On Tue, May 3, 2016 at 9:18 AM, Fred Drake wrote: > My perspective, for what it's worth, is that while I find Markdown a > horrible pain, But wait, it's worse. Unlike ReStructuredText, there's no Markdown standard. In my last job, I had to use a suite of tools (from a single

Re: [Distutils] Basic Markdown Readme Support

My perspective, for what it's worth, is that while I find Markdown a horrible pain, there are a lot of people who pick it up before picking up Python, and tools like GitHub and BitBucket encourage (and make it easier to add) README.md to a project. For someone who isn't familiar with

Re: [Distutils] Basic Markdown Readme Support

> -Original Message- > From: Nick Coghlan [mailto:ncogh...@gmail.com] > As I understand it, it's more a matter of folks finding the context > switch between Markdown and non-Sphinx reStructuredText a pain (with > the main differences being double-backticks for inline code and `link > text

Re: [Distutils] Basic Markdown Readme Support

On 3 May 2016 at 14:33, Alexander Walters wrote: > The justification was "Because Github et. al. support markdown, pypi should > too", presumably for the purpose of allowing one to write their README once, > and have it work in both places. This is already possible, and

Re: [Distutils] Basic Markdown Readme Support

The justification was "Because Github et. al. support markdown, pypi should too", presumably for the purpose of allowing one to write their README once, and have it work in both places. This is already possible, and only adds unneeded complexity to an already complex system. If you want to

Re: [Distutils] Basic Markdown Readme Support

On 3 May 2016 4:19 PM, "Alexander Walters" wrote: > > I am -1 on this on the basis that the services mentioned also happily support restructured text READMEs I don't understand why that makes you say no to the ability to support markdown. Rob

Re: [Distutils] Basic Markdown Readme Support

I am -1 on this on the basis that the services mentioned also happily support restructured text READMEs On 5/2/2016 12:40, Nick Timkovich wrote: Markdown READMEs are becoming increasingly ubiquitous for many projects. GitHub, GitLab, Bitbucket, among others, happily detect .md readme files

[Distutils] Basic Markdown Readme Support

Markdown READMEs are becoming increasingly ubiquitous for many projects. GitHub, GitLab, Bitbucket, among others, happily detect .md readme files and render them in their web interfaces. rST is nice, but is generally overkill for single-page documents (as opposed to more intricate documentation).