Sujet : Re: FileNotFoundError thrown due to file name in file, rather than file itself
De : dieter.maurer (at) *nospam* online.de
Groupes : comp.lang.pythonDate : 12. Nov 2024, 17:18:57
Autres entêtes
Message-ID : <mailman.98.1731428667.4695.python-list@python.org>
References : 1 2 3
User-Agent : VM 8.0.12-devo-585 under 21.4 (patch 24) "Standard C" XEmacs Lucid (x86_64-linux-gnu)
Cameron Simpson wrote at 2024-11-12 08:17 +1100:
On 11Nov2024 18:24, dieter.maurer@online.de <dieter.maurer@online.de> wrote:
Loris Bennett wrote at 2024-11-11 15:05 +0100:
I have the following in my program:
try:
logging.config.fileConfig(args.config_file)
config = configparser.ConfigParser()
config.read(args.config_file)
if args.verbose:
print(f"Configuration file: {args.config_file}")
except FileNotFoundError:
print(f"Error: configuration file {args.config_file} not found. Exiting.")
>
Do not replace full error information (including a traceback)
with your own reduced error message.
If you omit your "try ... except FileNotFoundError`
(or start the `except` clause with a `raise`), you
will learn where in the code the exception has been raised
and likely as well what was not found (Python is quite good
with such error details).
>
Actually, file-not-found is pretty well defined - the except action
itself is fine in that regard.
The original exception likely tells us which file was not found.