↳
In-reply-to
»
@quark Maybe at the weekend, but I’m rather busy these days with birthdays coming up (and/or no energy left after work to debug software 😳). But don’t worry, we’ll get this sorted out. 😊
⤋ Read More
@movq@www.uninformativ.de It might be timestamps which are missing a timezone. In this case the spec says UTC must be assumed: if twt_date.tzinfo is None: twt_date = twt_date.replace(tzinfo=datetime.timezone.utc). I had to fix this in my implementation recently, too. Let me quickly provide a fix for the Python reference implementation in the spec.