1. 10 Apr, 2018 2 commits
  2. 22 Feb, 2018 3 commits
  3. 11 Feb, 2018 1 commit
  4. 05 Feb, 2018 2 commits
  5. 17 Jan, 2018 1 commit
  6. 16 Jan, 2018 1 commit
  7. 15 Sep, 2017 2 commits
  8. 07 Jul, 2017 1 commit
  9. 06 Jul, 2017 1 commit
  10. 01 Jun, 2017 2 commits
  11. 24 May, 2017 1 commit
  12. 17 May, 2017 1 commit
  13. 14 Feb, 2017 3 commits
  14. 13 Feb, 2017 1 commit
  15. 07 Feb, 2017 5 commits
  16. 06 Feb, 2017 1 commit
  17. 03 Feb, 2017 2 commits
  18. 30 Jan, 2017 2 commits
  19. 16 Jan, 2017 1 commit
  20. 14 Jan, 2017 2 commits
  21. 22 Dec, 2016 1 commit
  22. 21 Oct, 2016 2 commits
  23. 20 Oct, 2016 2 commits
    • Merge branch '5-disable-logging-messages-in-pure-c-code' into 'master' · 91888597
      Resolve "Disable logging messages in pure C++ code"
      
      Closes #5 
      
      I have implemented functionality to select the log level in pure C++ code. You can now simply use ``bob::core::log_level(bob::core::INFO)`` to allow ``INFO`` messages (and above) to be printed, or ``bob::core::log_level(bob::core::DISABLE)`` to disable all C++ log output. By default, ``DEBUG`` messages are written.
      This functionality should only be used in pure C++ code and is, therefore, not bound to python, which has its own logging system. The interface between bob and the ``logging`` system in Python has not changed.
      
      I have created a new ``bob/core/_test.so`` extension, which contains test cases for the new functionality. To be able to run it using nose, the test case has been bound to Python.
      I have also moved the existing C++-only test cases, which have been in the ``bob/core/_library.so`` into the ``bob/core/_test.so``. Hence, the test cases are not loaded any more when running ``import bob.core``, but only during testing.
      
      @andre.anjos : As you have written the logging system, I assign this PR to you.
      
      See merge request !7
      André Anjos authored