Closed GoogleCodeExporter closed 9 years ago
Hi John,
i think i already tried to catch the failure but didn't succeed until now.
However i try to look into the failure again during my Christmas Holidays. Feel
free to try it as well, maybe you know this mechanism better then me.
regards
Christian
Original comment by christian.kohloeffel
on 1 Dec 2013 at 10:41
This issue was closed by revision r462.
Original comment by johninla...@googlemail.com
on 21 Jan 2014 at 12:55
Fixed with commit 462
My local postpro_config/postpro_config.cfg was outdated.
Had thought it was the main config/config.cfg file as the user-friendly message
wasn't being displayed (due to calling tr() - now removed).
Would be good to show which filename is being referred to... something for the
wishlist.
Original comment by johninla...@googlemail.com
on 21 Jan 2014 at 12:59
Hi all.
Sorted. It was due to an outdated postpro config file but there was a
self.tr() call around the error message so it wasn't being displayed.
Would be good to put the filename into that message, will look at that when
I get a chance.
Also completed the pylint-suggested cleanups over the weekend.
J.
Original comment by johninla...@googlemail.com
on 21 Jan 2014 at 1:39
Original issue reported on code.google.com by
johninla...@googlemail.com
on 30 Nov 2013 at 10:21