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 c
Well, at least abspath()ing FAKE_WALLPAPER makes Python 3.3 break in the
same way, so that's a good thing. :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269898
Title:
Python 3.4 failures
To man
** Changed in: oneconf (Ubuntu Trusty)
Assignee: (unassigned) => Barry Warsaw (barry)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269898
Title:
Python 3.4 failures
To manage notifications a
** Tags added: ftbfs python3.4
** Changed in: oneconf (Ubuntu)
Importance: Undecided => High
** Changed in: oneconf (Ubuntu)
Milestone: None => ubuntu-14.02
** Also affects: oneconf (Ubuntu Trusty)
Importance: High
Status: Confirmed
--
You received this bug notification becaus
Seems to be deeper than these errors, even. While resolving the build
failures in a pristine sbuild using the python3-all addition, I'm seeing
timeout failures. If I then add python2.7-all to the b-d, then I receive
many test failures due to test/test_mainfeatures.py (line 69), since
/tmp/oneconf-t
Actually, the problem is a little deeper. I see two test failures with
Python 3.4 against trunk code. Still investigating, by you should be
able to reproduce with this in Trusty (assuming python3.4 is installed).
$ python3.4 setup.py nosetests -vv --test test.test_syncing
==
