Closed
Conversation
Member
|
Thanks for your work! Sorry for the delay on reviewing this; we're currently focused on getting a stable marshmallow 3 release out the door, so we're prioritizing getting the last few backwards-incompatible changes released. We'll return to new features like this one after marshmallow 3 is released. |
Member
|
Closing. See #1003 (comment). |
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
3 participants
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.
closes #612
Actually in case of naive=True timezone is used only for timezone-aware datetimes conversion on serialization, maybe we should drop option naive=True and allow timezone=None instead? In this case on datetime-aware serialization we should throw ValueError, what do you think?