Cocaine tools bash completion improvements
Blocking API introduced

 - now chain objects has `get` method which represents blocking result getting without manually event loop handling
Cocaine tools bash completion improvements
Blocking API introduced

 - now chain objects has `get` method which represents blocking result getting without manually event loop handling
Blocking API slightly improved. Functionality expanded

 - `ChainFactory.get` method now should wait forever until timeout explicitly set. Also it now has ability to rethrow exceptions and can return None if it is valid result of chain expression.
 - some documentation added
 - internal example revamped
Fix reconnection policy. Improve stream's working with small messages.

WritableStream sends message immediately if buffer is empty.
Fix installation path for cocaine-tool.

Now It is sensitive to specifying the installation path with
--prefix or -d option of setup.py install command
This patch fix issue
https://github.com/cocaine/cocaine-framework-python/issues/5
Install bash_completion only in with deb package.
Code cleanup and examples fixing

 - code cleanup done
 - examples changed to match the current cocaine-runtime API
 - added some variations of checking cloud application in echo example check.py file
 - one todo item from TODO.py removed cause it is done
Merge branch 'master' of github.com:cocaine/cocaine-framework-python
Crashlog removeall action fixed
Some sketches about uploading application from git has been added

 - without external interface - only internal tool yet. Planning to get interface like `cocaine-tool app upload <url>`
 - only git and python are supported now

With this tool you can upload your application into cocaine-runtime directly from git repository. Only git repositories with python applications are now supported.
After cloning git repository, python virtual environment is created and needed packages is installed into it (including cocaine-framework-python automatically)
There must be manifest file located in repository root. It must contain `slave` key pointing to the slave file relative (from repository root) path
Also there can be `requirements.txt` file with requirement packages.
Gitignore updated
Merge branch 'v0.10'