Implement datetime timezone constraints

[antonagestam]

Alright, so I got something together that is seemingly working. Please let me know if you think something should be done differently, or structured in another way.

This implements support for constraining datetime objects based on them having or not having timezone info. The aware kind constrains to objects that have timezone info, and symmetrically, the naive kind constrains to objects that do not have timezone info.

Closes #266.

[codspeed-hq]

CodSpeed Performance Report

Merging #343 feature/implement-datetime-timezone-constraints (9dccdea) will not alter performances.

Summary

🔥 0 improvements
❌ 0 regressions
✅ 65 untouched benchmarks

🆕 0 new benchmarks
⁉️ 0 dropped benchmarks

[antonagestam]

Converted to draft, looking at the test failures.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 90.00000% with 2 lines in your changes missing coverage. Please review.

Project coverage is 97.13%. Comparing base (bb28794) to head (9dccdea).
Report is 784 commits behind head on main.

Files	Patch %	Lines
src/validators/datetime.rs	89.47%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #343      +/-   ##
==========================================
+ Coverage   96.34%   97.13%   +0.78%     
==========================================
  Files          58       58              
  Lines        6953     6978      +25     
  Branches       47       47              
==========================================
+ Hits         6699     6778      +79     
+ Misses        252      200      -52     
+ Partials        2        0       -2     

Files	Coverage Δ
pydantic_core/core_schema.py	100.00% <100.00%> (+11.38%)	⬆️
src/errors/types.rs	77.63% <ø> (ø)
src/validators/datetime.rs	93.33% <89.47%> (-0.79%)	⬇️

... and 5 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bb28794...9dccdea. Read the comment docs.

[antonagestam]

@samuelcolvin Any idea what's going on with the wasm build? Do we need to specify somewhere to also build the zoneinfo standard library or something?

[samuelcolvin]

looks to me like the wasm failures are a problem with hypothesis trying to import tzinfo, not relelated to the tests here.

You could be able to check this by adding conventional tests for this behaviour, then mark the hypothesis tests as skipped on wasm

[samuelcolvin]

overall, this looks great - doesn't look like that much to change.

[antonagestam]

I simplified both tests and merged the two types as suggested.

Overall, even though this is a very small change, very enjoyable to work with Rust I must say! 👍

[samuelcolvin]

This is great, thanks so much.

Pleased you enjoyed it, I'd love you to contribute more if you have the time.