fossi-foundation/ciel

Introduce ciel-specific Python exceptions

Open

#131 opened on Jun 15, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Python (11 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (56 stars)
PR merge metrics
 (PR metrics pending)

Description

Description

Ciel currently raises normal ValueErrors, RuntimeErrors, etc. This is theoretically fine. but practically that means we have to capture all exceptions for purposes of presenting them to the users, which can include exceptions in other libraries and/or the Python standard library, and not show a traceback. This is a pretty poor user/developer experience.

Proposal

New exception classes should inherit from ValueErrors/RuntimeErrors to match the declared APIs, but ciel should raise exclusively these classes.

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.