Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hide traceback for epyccel errors #1868

Closed
yguclu opened this issue May 8, 2024 · 0 comments · Fixed by #1869
Closed

Hide traceback for epyccel errors #1868

yguclu opened this issue May 8, 2024 · 0 comments · Fixed by #1869
Assignees
Labels
enhancement next release This PR must be merged before the next release

Comments

@yguclu
Copy link
Member

yguclu commented May 8, 2024

When an error is raised from within a call to epyccel, a traceback is printed which is not informative to the user (nor to the developer).

This may be due to a missing except block, which is present for pyccel instead.

The problem does not depend on the language.

@yguclu yguclu added enhancement next release This PR must be merged before the next release labels May 8, 2024
@EmilyBourne EmilyBourne self-assigned this May 8, 2024
@yguclu yguclu closed this as completed in 6f222d9 May 13, 2024
EmilyBourne added a commit that referenced this issue May 13, 2024
Add a `try/except` around internal Pyccel calls to catch all
`PyccelError`s. This allows the shortest possible traceback to be shown
to the user when the error is recognised, handled and reported by
Pyccel. Fixes #1868.
EmilyBourne added a commit to pyccel/pyccel-cuda that referenced this issue May 14, 2024
Add a `try/except` around internal Pyccel calls to catch all
`PyccelError`s. This allows the shortest possible traceback to be shown
to the user when the error is recognised, handled and reported by
Pyccel. Fixes pyccel#1868.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement next release This PR must be merged before the next release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants