New bag implementation improves a lot how bonobo works, even if this is
highly backward incompatible (sorry, that's needed, and better sooner
than later).
* New implementation uses the same approach as python's namedtuple,
by dynamically creating the python type's code. This has drawbacks, as
it feels like not the right way, but also a lot of benefits that
cannot be achieved using a regular approach, especially the
constructor parameter order, hardcoded.
* Memory usage is now much more efficient. The "keys" memory space will
be used only once per "io type", being spent in the underlying type
definition instead of in the actual instances.
* Transformations now needs to use tuples as output, which will be bound
to its "output type". The output type can be infered from the tuple
length, or explicitely set by the user using either
`context.set_output_type(...)` or `context.set_output_fields(...)` (to
build a bag type from a list of field names).
Jupyter/Graphviz integration is more tight, allowing to easily display
graphs in a notebook, or displaying the live transformation status in an
html table instead of a simple <div>.
For now, context processors were hacked to stay working as before but
the current API is not satisfactory, and should be replaced. This new
big change being unreasonable without some time to work on it properly,
it is postponed for next versions (0.7, 0.8, ...). Maybe the best idea
is to have some kind of "local services", that would use the same
dependency injection mechanism as the execution-wide services.
Services are now passed by keywoerd arguments only, to avoid confusion
with data-arguments.
Plugins now run in the main thread, instead of their own threads, and
the API changed to use an event dispatcher approach instead of a static
class interface.
This is the commit where I admit that having more than one input/output
format for readers and writers was complicating the code too much for a
very small gain, and that it would be easier to only have one way to do
it.
So such way is now:
- Returning (or yielding) a dict if you have key-value type collections.
- Returning (or yielding) a tuple if you have a list-type collection.
- Returning (or yielding) something else otherwise, which will continue
to work like the old "arg0" format.
IOFORMAT options has been removed in favour of a RemovedOption, which
will complain if you're still trying to set it to anything else than the
one value allowed.
