API changes: use Feed rather than Interface in many places
commit462af17062d60112e323252044531dbe7ef6b578
authorThomas Leonard <talex5@gmail.com>
Sat, 22 May 2010 17:37:27 +0000 (22 18:37 +0100)
committerThomas Leonard <talex5@gmail.com>
Sun, 23 May 2010 11:46:51 +0000 (23 12:46 +0100)
tree5a1acf0382f4984a86cd06b639c30b8a06cb7397
parent78ac1f2470f6bd8f146b4715c948564228980cfa
API changes: use Feed rather than Interface in many places

Originally, we only had Interfaces, which included the XML. Then we split this
into Interface for configuration (e.g. user's preferred stability policy) and
Feeds (for the XML).

Before, iface_cache only cached interfaces (each of which contained a feed).
That meant that if you only wanted a feed, we had to make up a dummy interface
for it. This patch updates the terminology in many places and passes around
Feed objects where it makes sense.

To see if you're using a deprecated API, uncomment the "warnings" lines in
model.py.
22 files changed:
tests/basetest.py
tests/server.py
tests/testautopolicy.py
tests/testdownload.py
tests/testgpg.py
tests/testifacecache.py
tests/testmodel.py
tests/testreader.py
tests/testsat.py
tests/testsolver.py
tests/testwriter.py
zeroinstall/0launch-gui/iface_browser.py
zeroinstall/0launch-gui/properties.py
zeroinstall/injector/background.py
zeroinstall/injector/cli.py
zeroinstall/injector/fetch.py
zeroinstall/injector/iface_cache.py
zeroinstall/injector/model.py
zeroinstall/injector/policy.py
zeroinstall/injector/reader.py
zeroinstall/injector/solver.py
zeroinstall/injector/writer.py