python-wadllib ftbfs in raring
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-wadllib (Debian) |
Fix Released
|
Unknown
|
|||
python-wadllib (Ubuntu) |
Fix Released
|
High
|
Barry Warsaw | ||
Raring |
Fix Released
|
High
|
Barry Warsaw |
Bug Description
see https:/
running build_ext
/build/
Doctest: README.txt ... /build/
Copyright (C) 2008-2009 Canonical Ltd.
/build/
..
/build/
..
/build/
..
/usr/lib/
test.
FAIL
=======
FAIL: /build/
Doctest: README.txt
-------
Traceback (most recent call last):
File "/usr/lib/
raise self.failureExc
AssertionError: Failed doctest test for README.txt
File "/build/
-------
File "/build/
Failed example:
create_
Differences (ndiff with -expected +actual):
- ('application/
? --------------
+ ('application/
? ++++++++++++++
-------
Ran 1 test in 0.171s
FAILED (failures=1)
make[1]: *** [test-python3.3] Error 1
Related branches
- Gary Poster: Approve
- Curtis Hovey: Pending requested
-
Diff: 99 lines (+22/-5)3 files modifiedsrc/wadllib/NEWS.txt (+9/-0)
src/wadllib/README.txt (+10/-2)
src/wadllib/application.py (+3/-3)
Changed in python-wadllib (Ubuntu Raring): | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in python-wadllib (Ubuntu Raring): | |
status: | Confirmed → In Progress |
summary: |
- python-wadlib ftbfs in raring + python-wadllib ftbfs in raring |
Changed in python-wadllib (Ubuntu Raring): | |
status: | In Progress → Fix Released |
Changed in python-wadllib (Debian): | |
status: | Unknown → Fix Released |
Looks like a sort order dependency. I wonder if it's better to guarantee an order or parse the value in the test and check for dict equality.