Remove get_excluded_fields function from manager – shouldn't be part … #515
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.
…of public API
Description
In #477,
get_excluded_fields
was added to the history manager since the initial version of that PR had a more complicated function definition forget_excluded_fields
. Since that function is only now used in one place and only consists of one line, I'd rather not have it part of the public API for history manager, so I'm removing it before the next release.Related Issue
Motivation and Context
How Has This Been Tested?
All current tests pass
Screenshots (if appropriate):
Types of changes
Checklist:
make format
command to format my codeAUTHORS.rst
CHANGES.rst