- 07 Nov, 2014 7 commits
-
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
- 04 Nov, 2014 3 commits
-
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
- 03 Nov, 2014 8 commits
-
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
- 30 Oct, 2014 2 commits
-
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
- 29 Oct, 2014 1 commit
-
-
Guillaume Seguin authored
-
- 23 Oct, 2014 10 commits
-
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
And move setup_logging to the main printcore app file. This way we don't need to butcher loggers anymore
-
- 22 Oct, 2014 9 commits
-
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
All we are interested in is catching potential exceptions indicating the variable does not exist, the print was just a sanity check.
-
Guillaume Seguin authored
-
Guillaume Seguin authored
-
Guillaume Seguin authored
This commit changes the way the Tee in Pronterface works. When no log is specified, sys.stdout is redirected as before to a tee between the console panel and the true sys.stdout. When a log is specified, sys.stdout is untouched and logging output is saved in both the console panel and the log file. The side effect is that all output must now go through the logging module to properly get in the console panel and in the log. Now we have to catch all "print" statements =)
-