-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Mention gr backend in docs. #14706
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.
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
Mention gr backend in docs. #14706
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really useful new section.
Not merging yet, because I'm not sure why the tests fail.
I think we merged something w a flake8 error. |
...or something happened to flake8 so it no longer works |
pydocstyle 4.0 was released yesterday (https://pypi.org/project/pydocstyle/#history). I'm quite sure this is the reason for the failure (though I did not check what exactly goes wrong there). |
basically flake8-pydocstyle doesn't support (yet) the last version of pydocstyle, although there's a PR open on their repo to fix that |
Since this is doc-only. I don't think flake8 would check the changes anyway. So merging without waiting for the flake8-docstring fix (#14710). |
…706-on-v3.1.1-doc Backport PR #14706 on branch v3.1.1-doc (Mention gr backend in docs.)
…706-on-v3.1.x Backport PR #14706 on branch v3.1.x (Mention gr backend in docs.)
PR Summary
Closes #7950. The text for gr was paraphrased from http://gr-framework.org/ and http://gr-framework.org/about.html.
PR Checklist