Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Review Suggested Edit

You can't approve or reject suggested edits because you haven't yet earned the Edit Posts ability.

Approved.
This suggested edit was approved and applied to the post 3 months ago by Alexei‭.

76 / 255
  • How to provide additional information when raising exception
  • How can I provide additional information when raising an exception?
  • # MWE
  • ```py
  • filename = "bad_dir"
  • print(f"File not found: {filename}.")
  • raise(FileNotFoundError)
  • ```
  • # Question
  • How do I raise an exception while adding additional information? In the
  • example above, the exception raised is printed at the bottom of the
  • stacktrace, and the print above it is printed at runtime and hard to
  • find in the terminal.
  • Is there a way to add a string to the raised
  • exception to provide additional information?
  • Suppose I have some code like:
  • ```py
  • filename = "bad_dir"
  • print(f"File not found: {filename}.")
  • raise(FileNotFoundError)
  • ```
  • When the exception isn't caught, the stack trace is printed at the end of the output, right as the program aborts. The `print`ed message could be far above this and is hard to find in the terminal and hard to associate with the exception.
  • How can I provide additional information in the exception, so that it can be seen immediately when the traceback is displayed?

Suggested 3 months ago by Karl Knechtel‭