[Python] avoid logging both 'generating' and 'compiling' module in two lines
1 unresolved thread
Merge request reports
Activity
assigned to @andreas.dedner
added 3 commits
-
32fa4fc6...4960775d - 2 commits from branch
master
- 1951c018 - [Python] avoid logging both 'generating' and 'compiling' module in two lines
-
32fa4fc6...4960775d - 2 commits from branch
mentioned in commit a85c317c
265 278 found = line in out.read() 266 279 if not os.path.isfile(sourceFileName) or not found: 267 280 logger.info("Generating " + pythonName) 281 # don't print 'Compiling' twice this wouldn't print Compiling twice, no? It would print Generating and then Compiling which are two separate steps? So at least the comment is wrong.
Edited by Timo Kochgenerating/updating always leads to compilation so no reason to print it twice or have a different log level in my opinion. If you think this information is important then change the
generating
message togenerating and compiling
. As a developer I just want to know if a module is being newly generated, or the generated code has been updated, or if it's being recompiled. As a user I want to know why nothing sees to be happening.
Please register or sign in to reply