Examples: fix formatting issue in 'Errorbar limit selection' #17573
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I'm not sure what those two test job failures pertain to, as I am not willing to sign up to CircleCI which blocks me from seeing anything except, in the "... artifact" job, a message "Artifact not found" which means nothing to me. Let me know if there's anything I need to do. Thanks. |
|
The install did not run cleanly on circle/CI docs-python38: I've restarted to see if this is a persistent problem. |
timhoffm
approved these changes
Jun 4, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
I noticed a minor formatting issue (backticks being displayed due to missing space after a literal item) in the text in the 'Errorbar limit selection' example page that has not been picked up on or fixed in master (as far as I can tell by searching the PRs/ issues from some keywords), & since I had forked the repo already to submit another PR thought I would raise it here. Thanks.
PR Checklist
[Only one checklist item applicable:]
- [ ] Has Pytest style unit tests- [ ] Code is Flake 8 compliant- [ ] New features are documented, with examples if plot related- [ ] Added an entry to doc/users/next_whats_new/ if major new feature (follow instructions in README.rst there)- [ ] Documented in doc/api/api_changes.rst if API changed in a backward-incompatible way