The solution for not rendering Markdown files already works for .rst files, you append ?plain=1 to the url as in this issue: https://github.com/numpy/numpy/issues/20438 On Tue, Nov 23, 2021, 12:00 PM wrote:

Send NumPy-Discussion mailing list submissions to numpy-discussion@python.org

To subscribe or unsubscribe via the World Wide Web, visit

https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ or, via email, send a message with subject or body 'help' to numpy-discussion-request@python.org

You can reach the person managing the list at numpy-discussion-owner@python.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of NumPy-Discussion digest..."

Today's Topics:

1. Ask GitHub to provide an option to not render .rst files (Warren Weckesser) 2. Re: Code formatters (Adrin)

----------------------------------------------------------------------

Message: 1 Date: Mon, 22 Nov 2021 12:38:41 -0500 From: Warren Weckesser Subject: [Numpy-discussion] Ask GitHub to provide an option to not render .rst files To: Discussion of Numerical Python , SciPy Developers List Message-ID: Content-Type: text/plain; charset="UTF-8"

Hey all,

If you've ever tried to inspect a file on github with the `.rst` extension, there's a good chance that you were frustrated by GitHub providing a rendered view *only* of the file, with no option to view the source code like any other text file. It is certainly nice to have a rendered view, but often I want to inspect the actual source code (e.g. to find out at which line a heading occurs, perhaps to include a link to it in a pull request). There is the "raw" option, or you could click "edit", but what is really desired is a view of the source like any other source code.

Files with the `.md` extension are also rendered by default, but there are buttons that allow you to either "Display the source blob" or "Display the rendered blob". There is no such option for `.rst` files. If they can do it for `.md` files, it seems like it should be easy to do the same for `.rst` files.

I've tried creating a ticket on github about this, but it seems like tickets go to the wrong group. The response I got was from the "GitHub Support" team, and they said they forwarded the request to the "Product" team. (It's all GitHub to me.) It was also suggested that I bring this up in a public feedback discussions, so I did:

https://github.com/github/feedback/discussions/7999

If you have a moment, could you add a comment, or click the upvote button, or add some other feedback to the discussion? It would be nice to get this simple enhancement into the GitHub site.

Thanks,

Warren

------------------------------

Message: 2 Date: Mon, 22 Nov 2021 23:31:32 +0100 From: Adrin Subject: [Numpy-discussion] Re: Code formatters To: Discussion of Numerical Python Message-ID: < CAEOrW4-1CVR2+Taffp382GcvsqcESnbEa5_x2zJGN26kUfC+-w@mail.gmail.com> Content-Type: multipart/alternative; boundary="00000000000073b9aa05d168305c"

This discussion and the linked gist may be of some help: https://github.com/scikit-learn/scikit-learn/issues/11336

On Mon, Nov 22, 2021 at 12:02 PM Andrew Nelson wrote:

...

Is there a way to figure out which files are not touched by any open PR? That way numpy might be able to do a lot more than an incremental code alignment. _______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-leave@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: adrin.jalali@gmail.com