Viewing profile — ariebovenberg

Author here. It's indeed a hard problem to parse "All ISO 8601 formats and all its weird mutant children that differ by a tiny bit." Since the ISO standard is so expansive, every l…

No problem. After all, the readme does go from mentioning Pure Python directly to showing a benchmark graph where it's curiously absent

Author here. It's answered briefly in the FAQ > In casual benchmarks, the pure-Python version is about 10x slower than the Rust version, making it 5x slower than the standard libra…

Author here. To summarize the long discussion in the issue: 1. I _love_ pure Python packages. Not everybody should be forced to use Rust. I want installing pure-Python to be as eas…

You are correct that there are improvements to be made. The current internal representation is—for the moment—simply the Python standard library. Probably the approach of Chrono is…

Indeed, structural changes to timezones also need to be handled. Temporal has a good approach here https://tc39.es/proposal-temporal/docs/ambiguity.html#ambigu... . Basically: - St…

Author of the article here— I actually did start out basically porting Chrono to Python, but decided against it for two reasons: 1. While I really liked handling local/UTC conversi…

Author here— This is a conscious decision, I'll explicitly address this in the FAQ soon. As I commented elsewhere, this is completely in line with industry standards (iCal, Unix ti…

I wouldn't consider 'not handling leap seconds' as a pitfall. If you need to account for leap seconds, you're probably not going to use a general-purpose datetime library. Unix tim…

Yeah—the perfect solution doesn't exist. The problem is that fixed-offset datetimes are very common since RFC3339 and ISO8061 don't support timezone names. The result is that you o…

Author here. "Offset" is indeed relative to UTC. The problem with allowing adding timedeltas is that you give users the impression they are doing valid arithmetic, while they may n…

Author of the post here— They are emoji. I've added plain text to the table now, so it is readable without them. edit: I've used a workaround to display emoji as images now

Author of the blog post here— 1) You're absolutely right, I'll fix this mistake in the example. 2) "Made up" was perhaps stirring the pot too much ;), but the fact remains that a t…

Was this inspired by another library or language? Or simply a reaction to the all-too-common experience of dealing with under-specified data?

When parsing timestamps, Pydantic (a wildly popular validation library for Python) will infer for you whether it's in seconds or milliseconds. I've never encountered behavior like …

Author here. I in my article I didn't touch on 'log poinsoning'[1], what they could be referring to. Vulnerability to log poisoning really depends on _what_ you do with your logs. …

__slots__ is a good way to make Python classes more efficient. There is a catch though: you need to use it consistently in all base classes, or you don't get the full benefits. Thi…