• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

collective / icalendar / 33754050143
98%

Build:
DEFAULT BRANCH: main
Ran 03 Sep 2026 12:15PM UTC
Jobs 6
Files 259
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

03 Sep 2026 12:14PM UTC coverage: 97.562%. Remained the same
33754050143

push

github

web-flow
Deprecate single_string_parameter as private function for icalendar 8 (#1750)

* Deprecate single_string_parameter as private function for icalendar 8

Author: Morningstar202604 <morningstar202604@users.noreply.github.com>
Date: 2026-09-02 18:45:16

Rename single_string_parameter to _single_string_parameter and add
deprecation wrapper for backwards compatibility.

The function was never part of the public API (not listed in __all__)
and is only used internally as a decorator for Parameters.value and
Parameters.tzid properties.

Changes:
- Renamed single_string_parameter to _single_string_parameter
- Added deprecated wrapper single_string_parameter that issues
  DeprecationWarning when used
- Updated internal usages to use the new private name
- Added changelog entry in news/1011.removal.1

AI disclosure: I used AI (Claude) to assist me with this change.
The AI helped with code analysis, implementation, and testing.

* Future proof news fragment for #1011

Updated the changelog entry to be more specific about the deprecation
and provide clearer guidance for users.

* Use deprecate_for_version_8 for single_string_parameter and future proof news

Per review:
- parser/parameter.py: replace the hand-written DeprecationWarning wrapper
  with the shared icalendar.compatibility.deprecate_for_version_8 utility,
  so all version-8 deprecations use one searchable mechanism
  (parser/string.py already does this). The warning message is unchanged.
- news/1011.removal.1: use the reviewed wording that stays valid after the
  icalendar 8 release.

AI: GLM (via ZCode coding agent) applied both review items and verified
the deprecation warning locally; the author reviewed the change.

---------

Co-authored-by: Morningstar202604 <320475654+Morningstar202604@users.noreply.github.com>

1671 of 1810 branches covered (92.32%)

Branch coverage included in aggregate %.

5 of 5 new or added lines in 1 file covered. (100.0%)

14697 of 14967 relevant lines covered (98.2%)

5.89 hits per line

Jobs
ID Job ID Ran Files Coverage
1 run-pypy3 - 33754050143.1 03 Sep 2026 12:25PM UTC 259
97.53
GitHub Action Run
2 run-3.11 - 33754050143.2 03 Sep 2026 12:16PM UTC 259
97.53
GitHub Action Run
3 run-3.13 - 33754050143.3 03 Sep 2026 12:16PM UTC 259
97.53
GitHub Action Run
4 run-3.10 (nopytz) - 33754050143.4 03 Sep 2026 12:16PM UTC 259
97.56
GitHub Action Run
5 run-3.10 - 33754050143.5 03 Sep 2026 12:17PM UTC 259
97.56
GitHub Action Run
6 run-3.12 - 33754050143.6 03 Sep 2026 12:15PM UTC 259
97.53
GitHub Action Run
Source Files on build 33754050143
  • Tree
  • List 259
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #33754050143
  • 9c758246 on github
  • Prev Build on main (#33685001811)
  • Next Build on main (#33774094874)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc