Skip to content

feastdate 1.0.5: refuse Sundays the year did not have; document the CLI year range - #2

Merged
isaacschepp merged 1 commit into
mainfrom
fix/year-and-ordinal-caps
Sep 23, 2026
Merged

isaacschepp merged 1 commit into
mainfrom
fix/year-and-ordinal-caps

Conversation

@isaacschepp

Copy link
Copy Markdown
Owner

A misread numeral used to answer a plausible date in the next season:
Dom. 28. Trin. 1680 gave Sun 19 Dec 1680, the 4th Sunday of Advent, and
Dom. 7. p. Epiph. 1680 gave a Sunday two weeks into Septuagesima. The
count is now checked against the year: the Sundays after Trinity run up
to Advent 1 (22 to 27 of them) and the Sundays after Epiphany up to
Septuagesima (1 to 6). A Sunday numbered 0 is refused, and so is a feria
outside 1 to 7 (Fer. 9. Pasch. used to answer Easter + 8).

The README and --help said a separate year could be 1 to 9999, but the
CLI reads a separate last word as a year only from three digits up, on
purpose: "Dom. Trin." 9 could be an ordinal, and reading it as AD 9
would answer in silence. The docs now say 100 to 9999, and the "no year"
error says why a one- or two-digit last word was not taken as a year.
--easter and the Python API still take any year from 1.

…LI year range

A misread numeral used to answer a plausible date in the next season:
Dom. 28. Trin. 1680 gave Sun 19 Dec 1680, the 4th Sunday of Advent, and
Dom. 7. p. Epiph. 1680 gave a Sunday two weeks into Septuagesima. The
count is now checked against the year: the Sundays after Trinity run up
to Advent 1 (22 to 27 of them) and the Sundays after Epiphany up to
Septuagesima (1 to 6). A Sunday numbered 0 is refused, and so is a feria
outside 1 to 7 (Fer. 9. Pasch. used to answer Easter + 8).

The README and --help said a separate year could be 1 to 9999, but the
CLI reads a separate last word as a year only from three digits up, on
purpose: "Dom. Trin." 9 could be an ordinal, and reading it as AD 9
would answer in silence. The docs now say 100 to 9999, and the "no year"
error says why a one- or two-digit last word was not taken as a year.
--easter and the Python API still take any year from 1.
@isaacschepp
isaacschepp merged commit 979e5f1 into main Sep 23, 2026
10 checks passed
@isaacschepp
isaacschepp deleted the fix/year-and-ordinal-caps branch September 23, 2026 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant