-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFE: use zoneinfo
instead of pytz
#56
Comments
Whats the motivation? |
I think there's something to be said for avoiding non-stdlib dependencies when they're not needed. pytz used to be one of the easiest ways to get hold of a timezone object, but that hasn't been the case for a while now. That said, I don't know why this package would use |
https://docs.python.org/3/library/datetime.html#datetime.timezone.utc sadly doesn't list when it was added; possibly 3.2. |
|
I think its dropped in every way that matters. We can remove the classifier as well of course. |
Additionally |
This is true, but it's moot since there's absolutely no point in using zoneinfo for UTC. It's only needed when you need other timezones from the IANA database. |
Both modules ze in standard OOTB set. |
Even the |
#64 drops Python 2 support. If that looks good then we can take advantage of py3-specific timezone handling after that. |
Sorry, I misspoke before about introduction time. I meant
I've merged #64, and will happily merge a change that uses |
Switch to standard
zoneinfo
module.Below may help pydantic/pydantic-core@fd262933
The text was updated successfully, but these errors were encountered: