5

I am using py.test to test some modules of mine that contains quite a bit of stdlib logging. I would of course like for the logging to log to stdout, which is captured by py.test, so that I will get all relevant logging messages if a test fails.

The problem with this is that the logging module ends up trying to log messages to the 'stdout'-object provided by py.test after this object has been discarded by py.test. That is, I get:

Traceback (most recent call last):
  File "/usr/lib/python2.6/atexit.py", line 24, in _run_exitfuncs
    func(*targs, **kargs)
  File "/usr/lib/python2.6/logging/__init__.py", line 1508, in shutdown
    h.flush()
  File "/usr/lib/python2.6/logging/__init__.py", line 754, in flush
    self.stream.flush()
ValueError: I/O operation on closed file

If I turn off capturing with -s, I don't have any problems, but of course that makes the test output unreadable with irrelevant logging.

Can anyone tell me the proper way to integrate stdlib logging with py.test?

(I tried looking at this, where it looks like it should just work without issues, so it didn't help me much)

Community
  • 1
  • 1
porgarmingduod
  • 7,668
  • 10
  • 50
  • 83
  • could you show us how you run your py.test code? If that happens it must be that the logging is configured and initialized BEFORE py.test, but this should not happen if you run the code through py.test executable. – Alan Franzoni Jan 21 '11 at 21:48
  • I run it using the basic command line `py.test` and let it collect and run things as it please. – porgarmingduod Jan 22 '11 at 11:53

3 Answers3

6

Logging/capturing interactions are to better work with the upcoming 2.0.1 release, which you can install already as a development snapshot by:

pip install -i http://pypi.testrun.org pytest

You should get at least "2.0.1.dev9" when you type "py.test --version" afterwards. And the problem/error your posted should now be gone.

A bit of background: the logging package insists on "owning" the streams it uses, and by default it grabs sys.stderr and insists to close it at process exit, registered via the atexit module. py.test substitutes sys.stdout with a temporary file in order to snapshot output (including output at file-descriptor level in order to also catch subprocess output). So py.test evolved to be very careful to always use the same temporary file as to not have logging's atexit-code complain.

Not that you can also install the [pytest-capturelog][1] plugin which will help some more with dealing with logging output.

[1] http://pypi.python.org/pypi/pytest-capturelog/0.7

hpk42
  • 21,501
  • 4
  • 47
  • 53
  • The new version did work fine, thanks. I couldn't get your `pip ...` command to work though, but installed the packages manually. – porgarmingduod Jan 22 '11 at 15:15
  • glad it worked. was it "pip" that missing? Otherwise maybe adding a "-U" would help to make sure it will upgrade. Or use "easy_install" as an alternative tool with the same options. – hpk42 Jan 22 '11 at 18:40
  • I installed pip. Didn't work as prescribed. Tried easy_install, which was a bit confused. So I just downloaded the zipfiles for py and pytest manually and used easy_install to install them. – porgarmingduod Jan 24 '11 at 12:16
  • Just tried it: "easy_install pip" then "pip install --upgrade -i http://pypi.testrun.org pytest". It installed 2.0.1.dev10, and the reported issue is fixed :-) – thebjorn Jan 31 '11 at 14:39
3

If you don't mind the logging going nowhere after the objects have been discarded by py.test you could set the module-level variable logging.raiseExceptions to False somewhere early in your modules or tests.

This will make the logging module swallow exceptions that occur in the logging subsystem. (Also a good practice for production systems where you don't want errors in logging crash your system)

You could also use logging.basicConfig() to set logging output to a separate file. But this is probably not what you want.

Hannah S.
  • 3,081
  • 3
  • 20
  • 27
-1

All you need to do is to pass the -s option to py.test, so that it won't capture the stdout.

rubik
  • 8,814
  • 9
  • 58
  • 88
  • "If I turn off capturing with -s, I don't have any problems, but of course that makes the test output unreadable with irrelevant logging." – porgarmingduod Jan 18 '11 at 17:09