Since Object knows its base now, the initialization of the tree with the content of its base can be delayed until the moment someone wants to actually modify the tree, thus implementing copy on write semantics. For this a new `write` method is added that will initialize the base and return the writable tree. It should be used instead of `path` whenever the a client wants to write to the tree of the Object. Adapt the pipeline and the tests to use the new `write` method in all the appropriate places. NB: since the intention can not be inferred when using `path` directly, the Object is still being initialized there. |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| __main__.py | ||
| api.py | ||
| buildroot.py | ||
| loop.py | ||
| objectstore.py | ||
| pipeline.py | ||
| remoteloop.py | ||
| sources.py | ||
| tmpfs.py | ||
| treesum.py | ||