↳
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 @prologic@twtxt.net Ok, there you go: https://git.mills.io/yarnsocial/yarn/pulls/459 However, I mixed something up. The bug I found two weeks ago in my implementation was something different regarding seconds precision. Go will always invent UTC for time.Time objects (if I’m not mistaken it’s impossible to have a timestamp without a timezone), Python does not.