Skip to content
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

Treat empty/missing writeable as a no-op #4659

Merged
merged 1 commit into from
Mar 31, 2021

Conversation

jakirkham
Copy link
Member

Since writeable filled with None will not equal True or False, this will effectively be treated as a no-op along frames to be pushed into new without copying.

Should fix some issues that users are running into around serialization of data.

Since `writeable` filled with `None` will not equal `True` or `False`,
this will effectively be treated as a no-op along frames to be pushed
into `new` without copying.

Should fix some issues that users are running into around serialization
of data.
@jakirkham
Copy link
Member Author

Went ahead and merged so we can get this fix into the bug fix release this Friday. Happy to follow up on anything else in subsequent issues and PRs as needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant