Can't use enc_hook to fix naive datetimes about msgspec

[jcrist]

Hmmm, that's certainly possible to do.

A few questions:

• Do your messages contain a mix of naive and aware datetimes? Or are you only using naive datetimes?
• How do you plan on treating naive datetimes? UTC? Local timezone? Something else?
• Do you plan on serializing datetimes in a different format than RFC3339 (what msgspec currently uses)?

[tuffnatty]

• Do your messages contain a mix of naive and aware datetimes? Or are you only using naive datetimes?

I am dealing with poorly structured data from MongoDB, so I am never sure what kind of datetime I will encounter.

• How do you plan on treating naive datetimes? UTC? Local timezone? Something else?

I attempted to convert them to UTC in enc_hook.

• Do you plan on serializing datetimes in a different format than RFC3339 (what msgspec currently uses)?

I did not have any such plan. RFC3339 is space efficient enough for me, but if I had such a problem, I'd look at Temporenc, although their reference implementation in pure Python may be too slow.
(P.S.: I am using msgpack encoding. Does it also serialize to RFC3339?)

I have already solved my immediate problem by fixing the data before feeding to msgspec, but I still think a hook could be useful here.

[jcrist]

Makes sense, we can definitely add this feature. I'll try to get it in before the next release.

(P.S.: I am using msgpack encoding. Does it also serialize to RFC3339?)

Ah, my mistake, I assumed you were using JSON. Msgpack has a timestamp extension type that provides a builtin efficient representation.