None returning dumper #642
Open
+345
−124
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
dvarrazzo
force-pushed
the
none-returning-dumper
branch
from
2952d85
to
5ac82ca
Compare
dvarrazzo
force-pushed
the
none-returning-dumper
branch
from
5ac82ca
to
ae569f2
Compare
dvarrazzo
force-pushed
the
none-returning-dumper
branch
5 times, most recently
from
0c8b2a0
to
e8d95d7
Compare
These are only the changes suggested by Mypy; no test added to verify that the code paths actually work. Only Python test fixed, no C yet.
Even if these classes never return None, this allows to create subclasses returning None without making Mypy unhappy. Similarly, annotate quote() methods as returning Buffer to allow subclasses to return other types.
dvarrazzo
force-pushed
the
none-returning-dumper
branch
from
e8d95d7
to
bc8286d
Compare
|
This branch is now ready to review. Will merge it in a few days, unless anyone has anything to point out. |
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.
Allow dumpers to return None, which would be then treated adequately in normal queries, in COPY, as part of composite objects such as Composite or Range.
In the C code, currently only Python dumpers are checked for returning None, because no builtin dumper does it and I don't expect anyone currently subclassing a C dumper. Should the need arise, we can allow None as C dumpers result in a bugfix.
Close #377