Skip to content

Follow up on #14424 for docstring #15159

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Aug 30, 2019
Merged

Follow up on #14424 for docstring #15159

merged 1 commit into from
Aug 30, 2019

Conversation

ImportanceOfBeingErnest
Copy link
Member

PR Summary

Follow up on #14424 for docstring. This is the suggested edit from #14424 as a new PR.

PR Checklist

  • Has Pytest style unit tests
  • Code is Flake 8 compliant
  • New features are documented, with examples if plot related
  • Documentation is sphinx and numpydoc compliant
  • 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

@ImportanceOfBeingErnest ImportanceOfBeingErnest added this to the v3.2.0 milestone Aug 30, 2019
@jklymak jklymak merged commit 9086f0a into master Aug 30, 2019
@QuLogic QuLogic deleted the quiverdocstring-update branch August 31, 2019 00:34
@aamster aamster mentioned this pull request Sep 1, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@dstansby dstansby dstansby approved these changes

Assignees
No one assigned
Labels
Documentation
Projects
None yet
Milestone
v3.2.0
Development

Successfully merging this pull request may close these issues.
3 participants
@ImportanceOfBeingErnest @dstansby @jklymak