Close #13 - better lockstep API

[idanarye]

Assuming:

class Foo:
    @lockstep
    def process(self):
        # ...

foo = Foo()

• foo.process() - run the entire process
• with foo.process.lockstep() as process: - step into the process
• yield from foo.process.lockstep() - for lockstep nesting

[idanarye]

Not 100% sure about the yield from API. Maybe now that we are explicitly running the lockstep, we should also give the yield from it's own API? Something like yield from foo.process.delegate()?

[idanarye]

BTW: please let me merge this. I want to merge it and immediately update testlight - otherwise it'll break the installation.

[koreno]

Shouldn't it be

with foo.process.lockstep() as process:
    yield from process

?

[idanarye]

Currently we allow yielding from the context manager itself.

Yielding from the process object is easy to implement, but I generally prefer APIs that allow their user to avoid binding new names.

I would like to have a separate method for yielding the steps, because having it under .lockstep() forces me to use _LockstepContextManagerWrapper instead of a regular contextmanager, but I struggle to find a good name for it:

• yield from foo.process.unwrap_lockstep()?
• yield from foo.process.nested_lockstep()?
• yield from foo.process.lockstep_steps()?

[idanarye]

?