robyoung
I’m pretty sure Thailand isn’t in Mexico
That looks like ISO8601 format so you can use fromisoformat to make the parsing a bit simpler. I’m not clear why you need to drop the microsecond part. Surely if one timestamp is a few microseconds past the second it is later.
d1 = datetime.fromisoformat(date1)
d2 = datetime.fromisoformat(date2)
return date1 if d1 > d2 else date2
What exactly do you mean by an algorithmic system? Your introduction to the form implies you have a pretty broad definition. If that is the case then I think you should also account for a large proportion of your target not being sure that they are actually what you’re looking for. Define your terms. Give examples of what you determine inside the definition and examples of what you determine outside of it.
All that said, I think the research area sounds really interesting. I look forward to hearing how it goes.
The integrations with other services are implemented in plugins which are separate programs, that are installed separately, and communicate with the core over RPC. I would imagine these plugins can continue to be licensed however their owners choose. I think this license change just applies to core.
I don’t understand why the most_recent
field is needed. Surely the most recent state can be derived from the order field and the unique constraint on it can prevent concurrency issues if the previous sequence is taken before the state change. The benefit would be that the transition history table could then be append only.
Not even a mention of PyO3?