[AdrianAtZyte]

No description provided.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.19%. Comparing base (533b0df) to head (599afae).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1556      +/-   ##
==========================================
+ Coverage   99.18%   99.19%   +0.01%     
==========================================
  Files         239      239              
  Lines        4030     4098      +68     
==========================================
+ Hits         3997     4065      +68     
  Misses         33       33              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[codspeed]

Merging this PR will not alter performance

✅ 10 untouched benchmarks

---

_{Comparing AdrianAtZyte:deprecate-instead-of-remove (599afae) with master (533b0df)}

[serhii73]

Approving. CI is green, and I ran the full suite with this PR and the other pending 1.5.0 changes together (25107 passed).

Two non-blocking gaps compared with 1.4.3, both on undocumented extension points, that you may want to close here or in a follow-up. I checked both against v1.4.3:

• CalendarBase.get_date() now calls parser._parse_with_parts(). A parser class that only has parse(source, settings) -> (date, period) raises AttributeError; it works on 1.4.3.
• DateParser.parse() still unpacks the result of parse_method as (date, period, parts). A parse_method that returns (date, period) raises ValueError: not enough values to unpack; it works on 1.4.3.

Neither affects the library's own code paths.