Try to hide the docstring restriction a little less. #824
Conversation
This file contains 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
added 2 commits
May 14, 2020 12:29
… in security chapter
… list of the default security policy
dataflake
requested changes
May 14, 2020
dataflake
approved these changes
May 14, 2020
|
lgtm - thanks for taking your time! |
jugmac00
approved these changes
May 14, 2020
|
The failure in the CI systems is unrelated. I am going to merge this PR now. |
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.
As discussed in #770, the "docstring restriction" when publishing objects is not really part of the security policy stuff. But it is at least related, so I decided to mention it in the security chapter in 2 places which are likely to be read.