Comment 3 for bug 1269898

Okay, at least one test is caused by some bogus use of __file__. Python 3.3 and 3.4 treat __file__ differently in that with 3.3, the path may be relative to cwd, but in 3.4 it is absolute. oneconf uses the *path* of the logo file as its sha224 checksum (not its contents!) so that breaks the logo checksum test.

paths.py really probably should at least be using the absolute path in all cases, but I don't know if this will break its functionality. Ultimately it should not be using __file__ anyway, since that is not a reliable API. Instead it should be using pkg_resource.get_resource_filename() which comes from the setuptools package.