Aman Goel

Hi @yurivict, the testing information is under the [Contributing](https://hist.readthedocs.io/en/latest/contributing.html) section rather than Installation! `pytest` should work well in a development environment if you're in Hist's root directory.

Closing this issue since I believe it's resolved. @yurivict, feel free to follow up!

Hi @eduardo-rodrigues, I haven't made one from scratch recently, but I like the ones present in [uproot-browser](https://github.com/scikit-hep/uproot-browser/blob/main/.github/CONTRIBUTING.md) and [Hist](https://hist.readthedocs.io/en/latest/contributing.html). The basic idea is to have something similar to what @henryiii...

Could there be a potential workaround to this? Keeping plain-text as well as the formatting intact.

Thank you, these ideas are really insightful!

> In the browser tracebacks don't show the actual error message if I try to plot something like `uproot-Event.root:event`. I also think this should show a message like "Something went...

- The [Style Guide](https://carpentries.github.io/sandpaper-docs/instructor/style.html) has since been [updated](https://github.com/carpentries/sandpaper-docs/pull/241) to **not recommend** semantic line breaks anymore - The [updated guidelines](https://carpentries.github.io/sandpaper-docs/instructor/style.html#line-length) now recommend "writing one complete sentence per line" so we can...