Sometimes an exception, that should be re-cast, would get gobbled up if
it could be interpreted as a "connection broken" exception

satella .select() could return with UnboundLocalError due to processing
resuming on error

satella by default uses poll() in event dispatch. Fallback to select()
will be done on platforms that don't support poll()

superficial

Learned the hard way, sadly.

1) If input data contains heavy Unicode, export() will not fail.
2) Exported string will be reliably a str, UTF-8 encoded

see https://bugs.pypy.org/issue1255 for details

Socket's on_connected() would not always be called when it should. Bug
was fixed and an unit test added

Sometimes, after you fork(), your connections are in pretty bad state.
This call will get them right on their feet.

Quite important adnotation - Socket object does STREAMING comms

Socket constructor does not need to be informed whether socket object
passed is connected or not - it will be autodetected

__close_channel() does not exist anymore

a string version of NumericValueCounter was added. History handling in
NVC and SVC has been formalized and improved.

Previously values of child.parent were generated. This since has been
fixed to parent.child

a satella Socket can be constructed directly from another satella Socket