Gracefully handle bad imports
Bug #1181036 reported by
Joe Gordon
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| hacking |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
Currently when a stacktrace occurs upon an import, we just print the stacktrace and do nothing.
Instead we should add a new rule (H307 ?) that says modules must be importable on their own. So when a module isn't importable without a stacktrace we just raise a H warning.
| Changed in hacking: | |
| assignee: | nobody → Joe Gordon (jogo) |
| Changed in hacking: | |
| status: | New → Confirmed |
| Changed in hacking: | |
| assignee: | Joe Gordon (jogo) → nobody |
| Changed in hacking: | |
| importance: | Undecided → Wishlist |
To post a comment you must log in.
