--
Ticket URL: <https://code.djangoproject.com/ticket/18448>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
I see the reasoning here, but I'm going to reject this one. It's
essentially one of those things that we can't get right either way. If we
use `.rst`, the advantages are as you said, but many OSes won't know what
to do with `.rst` and so we'll get people asking to rename to `.txt` so
that the files open in their text editors. At a certain point you just
gotta make a call, and I'm calling it for `.txt`.
--
Ticket URL: <https://code.djangoproject.com/ticket/18448#comment:1>
Comment (by Mike Lissner):
I just did some work on documentation today and I found the use if txt
extensions instead of rst extension to be a bit frustrating. For example,
my editor couldn't treat these as ReStructured Text, and then when I was
writing my pull request, I couldn't review my work in Github either.
Similarly, for whomever reviews my PR, they won't be able to review it on
Github either, and will have to do so on their laptop, which is an extra
step for them.
I guess I understand the explanation from nine years ago that some people
won't be able to open rst files in their editor, but I think if Github
supports these natively, we can assume that just about everybody
contributing documentation would support them natively too.
Should we reconsider this one? I'd happily make a little PR to rename
files if so.
--
Ticket URL: <https://code.djangoproject.com/ticket/18448#comment:2>