Skip to content

refactor(py)!: rename exceptions to follow Error suffix convention#2022

Draft
kajal-jotwani wants to merge 1 commit intoconda:mainfrom
kajal-jotwani:fix/exception-naming
Draft

refactor(py)!: rename exceptions to follow Error suffix convention#2022
kajal-jotwani wants to merge 1 commit intoconda:mainfrom
kajal-jotwani:fix/exception-naming

Conversation

@kajal-jotwani
Copy link

@kajal-jotwani kajal-jotwani commented Jan 30, 2026

Description

This PR resolves an inconsistency where several exceptions were exported as *Error in Python but appeared with an *Exception suffix in tracebacks and documentation. This mismatch was causing confusion in the developer experience

Changes made:

  • Renamed all internal exception types from *Exception to *Error in error.rs
  • Updated imports and registrations in lib.rs to use the new names
  • Exception names now consistently use *Error suffix in both namespace and tracebacks

Related Issue: #1959

@kajal-jotwani kajal-jotwani marked this pull request as draft January 30, 2026 19:12
@baszalmstra baszalmstra changed the title refactor: rename exceptions to follow Error suffix convention refactor(py): rename exceptions to follow Error suffix convention Jan 30, 2026
@baszalmstra baszalmstra changed the title refactor(py): rename exceptions to follow Error suffix convention refactor(py)!: rename exceptions to follow Error suffix convention Jan 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants