Python logging doesn't create directories
Bug #397111 reported by
Michael Gorven
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ibid |
Fix Released
|
Medium
|
Michael Gorven | ||
Bug Description
The infamous startup error "No such file or directory: 'logs/ibid.log'" is due
to Python logging assuming that directories exist. We need to solve this one
way or another. The options are:
1. Parse the logging config and try to identify logfiles
2. Introspect the logging handlers once the config has been loaded and
identify logfiles
3. Handle the default configuration of logs/ibid.log
affects ibid
milestone 0.1
Related branches
Revision history for this message
| Michael Gorven (mgorven) wrote Re: [Bug 397111] [NEW] Python logging doesn't create directories | #1 |
Revision history for this message
| Stefano Rivera (stefanor) wrote | #2 |
Revision history for this message
| Michael Gorven (mgorven) wrote | #3 |
| Changed in ibid: | |
| assignee: | nobody → Michael Gorven (mgorven) |
| status: | New → In Progress |
Revision history for this message
| Michael Gorven (mgorven) wrote Re: [Bug 397111] Re: Python logging doesn't create directories | #4 |
Revision history for this message
| Michael Gorven (mgorven) wrote | #5 |
| Changed in ibid: | |
| importance: | Undecided → Medium |
Revision history for this message
| Michael Gorven (mgorven) wrote | #6 |
| Changed in ibid: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
> 2. Introspect the logging handlers once the config has been loaded and
> identify logfiles
This won't work since the exception occurs during the fileConfig() call.