-
Notifications
You must be signed in to change notification settings - Fork 27
feat: updated event signal metadata time #168
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
Conversation
606d5a7 to
eaca0f6
Compare
rgraber
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few questions
rgraber
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One more thought about defaults
rgraber
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for the updates
* Updated time metadata to include UTC timezone. Original implementation used utcnow(), which could give different results if the time were ever interpreted to be local time. See https://docs.python.org/3/library/datetime.html#datetime.datetime.utcnow * Updated send_event to optionally take a time, which would be used for the metadata. Ideally, this will be explicitly set. #162
04d9e2e to
52d6efc
Compare
Description:
interpreted to be local time. See https://docs.python.org/3/library/datetime.html#datetime.datetime.utcnow
ISSUE:
send_event_in_bus_consumer, which will require an additional breaking change to EventsMetadata. That will likely be made in a separate branch and merged into this PR.Testing instructions:
Merge checklist:
Version bumpedPost merge:
Create a tagCheck new version is pushed to PyPI after tag-triggered build isfinished.
Author concerns:
I don't love how EventsMetadata is initialized with time that can be None, but this is how I think it needs to be done for the frozen attributes. Note, this pattern is going to be followed in the follow-up PR where all arguments need to be sent for event bus consumers.Note: We found a way around this. :)