NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI · #3228 most downloaded on PyPI
Backport of Python 3.11's datetime.fromisoformat
Last release 2 years ago
no release in 18 months
Ships unpredictably
gaps range from 6 weeks to 4.0 years
Nearly every release is documented
notes for 7 of 7 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
7 releases · first in 2018
Silenced errors when compiling against Python 3.13
backports.datetime_fromisoformat does nothing when used against Python 3.11+. Use backports-datetime-fromisoformat; python_version < '3.11' in your dependency list to avoid even downloading it in modern PythonsVersion 2.0.2 Add support for aarch64 wheels Add builds for PyPy 3.10
One column per quarter.
Switched to pytest as a test runner
pyproject.tomlpytest as a test runnerpyproject.tomlpytest as a test runnerBackport the logic from Python 3.11's fromisoformat methods, instead of Python 3.7's, #22
fromisoformat methods, instead of Python 3.7's, #22
No migration is needed.
However, starting in version 2, backports.datetime_fromisoformat will apply its changes to Python < 3.11, whereas v1 only applied changes to Python < 3.7. If you happened to be using backports.datetime_fromisoformat v1 on Python 3.7 through Python 3.10 and then upgrade to v2, it will patch the fromisoformat methods, whereas in v1 it did not. The fromisoformat methods will be able to parse timestamps from a wider portion of the ISO 8601 specification. This is unlikely to be a problem, but for completeness it is mentioned here.
Fixed issue where datetimes with timezones would not be picklable/copyable.
Fixed issue where datetimes with timezones would not be picklable/copyable.
Thanks @jappievw
Fixed build issue that impacted certain installations (#10, Thanks @rlyons)
This first release is meant mostly as a test of the release process. While the code should work for Python 3.4+, it should not be considered ready for
This first release is meant mostly as a test of the release process.
While the code should work for Python 3.4+, it should not be considered ready for production.
Your coding agent can read these notes before it upgrades. Set up the MCP server →