OWASP / OWASP/Nettacker

Handle Exception

Open
#401 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

code quality
Dominant language
Python
Stars
5.6k
Forks
1.2k
Avg merge
1d 21h
Merged PRs (30d)
16

Description

We should use except exception as e instead of only except exception, otherwise it often difficult to debug the code. Like in issue #398 it shows module not exists because of import error in that module. This often deceiving and sometimes take bit of our time.


OS: Backbox

OS Version: 7.1

Python Version: 3.8.5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the exception handling involved in issue #398 and reproduce the misleading module-not-found error in the reported Python 3.8.5 environment. Identify the relevant handlers and verify that failures expose the underlying import error instead of only the outer exception message.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.