Closed philipstarkey closed 10 years ago
Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).
Resolves issue #17, failed default loading of config file exception handling.
→ \<\<cset 6033996ae62792e607f093f8c71cefc5186c140c>>
Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).
Huh, really? It doesn't for me, it creates the file, which was what I intended. If you type something in there that isn't even a valid filename, then you get an error, sure. So I've written some code to handle that, but I'm curious, was it not creating the files for you if they were valid filepaths that didn't exist?
Original comment by Philip Starkey (Bitbucket: pstarkey, GitHub: philipstarkey).
Ah, I see. The exact scenario was that I specified a blank path :) I assumed it wasn't a special case as it raised the error "WindowsError: [Error 3] The system cannot find the path specified: '' I didn't look closely enough!
Original report (archived issue) by Philip Starkey (Bitbucket: pstarkey, GitHub: philipstarkey).
If the autoload_config_file parameter in the runmanager section of the LabConfig file points to a file that does not exist, an Exception is raised.
Given that we are printing "loading default config file..." in the output box, we should probably catch/suppress the Exception and print a warning indicating that the file could not be loaded.