How arrow-py/arrow works
File structure
• Top-level directories & files:
• tests/ ← unit test suite
• docs/ ← user documentation
• requirements/ ← pinned dependencies
• CI and config files (GitHub Actions, tox.ini, setup.cfg, pyproject.toml, Makefile)
• api.py ← module exposing the public API functions
• parser.py ← parsing engine for a variety of date/time input formats (ISO 8601, timestamps, etc.)
• formatter.py ← string‐formatting logic, pattern definitions
• locales.py ← localizations for humanization (“an hour ago”, etc.)
• constants.py ← shared constants (default formats, lookup tables)
• util.py ← utility functions (time span generation, floor/ceiling operations)
• _version.py, __init__.py ← package version & export points
README for additional insights
• The README emphasizes:
• Drop-in replacement for datetime
• Timezone-aware by default (supports dateutil, pytz, ZoneInfo)
• Parsing, shifting, formatting, ranges, humanization, extensibility
• PEP 484 type hints
Don’t overthink—capture these essential elements
• Consumer entry point and API façade
• Factory & parsing pipeline
• Formatter & localization subsystems
• External TZ back-ends
• Extension/customization hooks