datetime interpretation changed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
wadllib |
Triaged
|
High
|
Unassigned | ||
python-wadllib (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Precise |
Fix Released
|
High
|
Unassigned |
Bug Description
Sorry I haven't looked further, but we started seeing the following error recently, which seems to be related to the recent release of wadllib (note, the error is misleading, as it has skipped the expected date comparison, see further paste below):
{{{
[localhost] run: virtualenv/
Creating test database for alias 'default'...
F
=======
FAIL: test_getForMe_
An example fixture can be used for the devserver.
-------
Traceback (most recent call last):
File "/home/
eg_
File "/home/
self.
AssertionError: '2010-07-02 15:25:28' != u'2010-
-------
Ran 1 test in 0.402s
FAILED (failures=1)
Destroying test database for alias 'default'...
Fatal error: local() encountered an error (return code 1) while executing 'virtualenv/
Aborting.
michael@
wadllib==1.3.0
michael@
Downloading/
Downloading wadllib-
Running setup.py egg_info for package wadllib
Requirement already satisfied (use --upgrade to upgrade): distribute in ./virtualenv/
Requirement already satisfied (use --upgrade to upgrade): elementtree in ./virtualenv/
Requirement already satisfied (use --upgrade to upgrade): lazr.uri in ./virtualenv/
Requirement already satisfied (use --upgrade to upgrade): simplejson in ./virtualenv/
Installing collected packages: wadllib
Found existing installation: wadllib 1.3.0
Uninstalling wadllib:
Successfully uninstalled wadllib
Running setup.py install for wadllib
Successfully installed wadllib
Cleaning up...
michael@
[localhost] run: virtualenv/
Creating test database for alias 'default'...
.
-------
Ran 1 test in 0.483s
OK
}}}
Note: the test is itself expecting to find a datetime object in the api value - see line 21: (yes, we should be using python fixtures)
http://
Related branches
- j.c.sackett (community): Approve
- Richard Harding: Approve (code*)
-
Diff: 19 lines (+2/-7)1 file modifiedsrc/wadllib/application.py (+2/-7)
Changed in wadllib: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in python-wadllib (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Critical |
milestone: | none → ubuntu-12.04-beta-1 |
Changed in python-wadllib (Ubuntu): | |
milestone: | ubuntu-12.04-beta-1 → none |
Changed in python-wadllib (Ubuntu Precise): | |
importance: | Critical → High |
tags: | added: rls-mgr-p-tracking |
Since the new version of this library broke a number of things and since it appears this is not going to get fixed anytime soon, why don't "we" just revert the changes and upload a new version for Precise?