Description of problem: When using caching, the update() call is not guaranteed for nested objects. Thus the explicit request to call update() manually should be documented (in bold;) Version-Release number of selected component (if applicable): python-nitrate-0.9-1.fc19.noarch Actual results: The only occurrences of 'update' in pydoc nitrate are in the context of: "Automatically update data upon destruction." and "By default CACHE_OBJECTS is used. That means any changes to objects are pushed to the server only upon destruction or when explicitly requested with the update() method." No need of the explicit update() call is hinted. Expected results: The necessity to call update() is mentioned and explained. Version-Release number of selected component (if applicable): python-nitrate-0.9-1.fc19.noarch
Thanks for the bug. This should now be better documented: https://github.com/psss/python-nitrate/commit/5c5043f
python-nitrate-1.0-0.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/python-nitrate-1.0-0.fc20
Great, thanks for fixing it. pydoc nitrate.cache now says: By default CACHE_OBJECTS is used. That means any changes to objects are pushed to the server only when explicitly requested with the update() method.
python-nitrate-1.0-0.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.