Formally define traits in swagger parser #346
Merged
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
|
I've gone ahead with an unreviewed merge to try to address doc build issues more clearly. |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
The CI tests for Python 3.7 and 3.8 have started failing recently. It turns out the traitlets 5.0.4 release has removed some deprecated functionality from traitlets 4.2. Since the older python tests still use 4.3.3, they continue working. The removed functionality had to do with member fields getting initialized from same-named keyword arguments without having been "typed" as a trait.
By defining these fields as traits, the expected initialization from keyword arguments occurs (on both versions of traitlets).