-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Hash field expiration commands #3218
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
Merged
Merged
Changes from 4 commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
9e5a797
Hash field expiration commands
gerzse 93f6ddb
Merge remote-tracking branch 'origin/master' into hash-fields-expiration
gerzse 4ce03fb
Remove doctests and switch to Google style docstrings
gerzse b4cd85a
Fix linter errors
gerzse 8316fd3
Sphinx config
gerzse 92a02fe
Merge remote-tracking branch 'origin/master' into hash-fields-expiration
gerzse 6f07645
Add FIELDS keyword to commands
gerzse 82c6582
Cover HGETF and HSETF
gerzse 74b8fe8
Merge remote-tracking branch 'origin/master' into hash-fields-expiration
gerzse 6a61ef1
Adapt to latest server side changes
gerzse 3430e61
Merge remote-tracking branch 'origin/master' into hash-fields-expiration
gerzse 733e96d
Merge remote-tracking branch 'origin/master' into hash-fields-expiration
gerzse df4dd02
Fix linter errors
gerzse 151ee8d
Guard new unit tests with correct Redis version
gerzse 3f15dc4
Update test related to memory stats
gerzse 4fa51df
Make CLIENT KILL test not run with cluster
gerzse b770e33
Disable tests related to Graph module
gerzse File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
BTW on the topic of docstrings : as mentioned by this discussion in Stackoverflow we can use the Pyment tool to generate new reST documentation or convert existing one from other formats. This is probably going to help in the general direction of consistency.
IMHO it is a good idea to continue with the reST format you are using here chiefly because of two things - we can generate documentation using Sphinx and it is generally recommended by PEP 287
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.
After trying out some more things, I think that the Google style documentation would be better suited. The main reason is that it supports bullet lists in a straightforward way. With reST I could not get a bullet list properly formatted in the PyCharm documentation popup.
Also it seems to me that a great deal of the existing documentation is a flavor of the Google style. It would be the least effort to convert it to the proper Google format.
And, after enabling the
napoleon
preprocessor for Sphinx, this Google style documentation also gets converted well (after some additional fine tuning related to typing).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.
Makes sense.