Repository navigation
Use fields.Raw instead of fields.Field for Pika port - #219
Merged
Merged
Conversation
Marshmallow 3.24 deprecated instantiating the base Field class, raising ChangedInMarshmallow4Warning on import. fields.Raw is the equivalent untyped field. Fixes #188.
ndevenish
force-pushed
the
marshmallow-raw-field
branch
from
November 6, 2026 14:28
71ec170 to
5c2f3af
Compare
ndevenish
enabled auto-merge (squash)
November 6, 2026 14:29
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
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.
Marshmallow 3.24 deprecated instantiating the base
fields.Field, so importingworkflows.util.zocalo.configurationraisedChangedInMarshmallow4Warning. The Pika schema'sportnow usesfields.Raw, which behaves the same: it accepts any value without conversion.Checked by importing the module with
-W erroron marshmallow 3.x: the warning fires before this change and not after. Marshmallow 4 doesn't warn either way.Fixes #188.