Prefix date parser
This is a helper class to parse dates with varied degrees of precision. For
example, a data source might state a date as 2001, 2001-4 or 2001-04-02,
with the implication that only the year, month or day is known. This library
will process such partial dates into a structured format and allow their
validation and re-formatting (e.g. turning 2001-4 into 2001-04 above).
The library does not support the complexities of the ISO 8601 and RFC 3339 standards including date ranges and calendar-week/day-of-year notations.
Installation
Install prefixdate using PyPI. It requires Python 3.11 or newer and has no
dependencies:
$ pip install prefixdate
Usage
The library provides a variety of helper functions to parse and format partial dates:
from prefixdate import parse, normalize_date, Precision # Parse returns a `DatePrefix` object: date = parse('2001-3') assert date.text == '2001-03' date = parse(2001) assert date.text == '2001' assert date.precision == Precision.YEAR date = parse(None) assert date.text is None assert date.precision == Precision.EMPTY # This will also be the outcome for invalid dates! # Normalize to a standard string: assert normalize_date('2001-1') == '2001-01' assert normalize_date('2001-00-00') == '2001' assert normalize_date('Boo!') is None # This also works for datetimes: from datetime import UTC, date, datetime now = datetime.now(UTC).isoformat() minute = normalize_date(now, precision=Precision.MINUTE) # You can also feed in None, date and datetime: normalize_date(datetime.now(UTC)) normalize_date(date.today()) normalize_date(None)
You can also use the parse_parts helper, which is similar to the constructor
for a datetime:
from prefixdate import parse_parts, Precision date = parse_parts(2001, '3', None) assert date.precision == Precision.MONTH assert date.text == '2001-03'
Format strings
For dates which are not already stored in an ISO 8601-like string format, you
can supply one or many format strings for datetime.strptime. The format strings
will be analysed to determine how precise the resulting dates are expected to be.
from prefixdate import parse_format, parse_formats, Precision date = parse_format('YEAR 2021', 'YEAR %Y') assert date.precision == Precision.YEAR assert date.text == '2021' # You can try out multiple formats in sequence. The first non-empty prefix # will be returned: date = parse_formats('2021', ['%Y-%m-%d', '%Y-%m', '%Y']) assert date.precision == Precision.YEAR assert date.text == '2021'
Two-digit years
A %y format leaves the century open. strptime resolves it in a fixed
1969-2068 window, so a date outside of that lands in the wrong century. Pass
two_digit_year_base to choose the 100 years to read the year in yourself --
a base of 1926 covers 1926 to 2025:
from prefixdate import parse_format date = parse_format('24-03', '%y-%m', two_digit_year_base=1926) assert date.text == '2024-03' date = parse_format('68-03', '%y-%m', two_digit_year_base=1926) assert date.text == '1968-03'
Without a base year the strptime window applies and a warning is logged.
parse_formats takes the same argument.
Inspecting format strings
The helpers used to analyse formats are public, in case you want to apply the same reasoning before parsing:
from prefixdate import Precision, format_precision, has_two_digit_year from prefixdate import resolve_two_digit_year from datetime import datetime # The precision a format string implies: assert format_precision('%Y-%m') == Precision.MONTH # Whether it reads the year as two digits: assert has_two_digit_year('%y-%m') is True # Move an already-parsed date into the century starting at a base year: dt = resolve_two_digit_year(datetime(2024, 3, 1), 1926) assert dt.year == 2024
Caveats
- Datetimes are always converted to UTC.
DatePrefix.dtkeeps its timezone and is aware (tzinfo=timezone.utc), whileDatePrefix.textreads as naive because the UTC offset sits past the precision the text is cut to. - Does not process milliseconds yet: fractional seconds are matched, but
discarded, so
DatePrefix.dt.microsecondis always0. - Does not process invalid dates, like Feb 31st.