Djangoes

A lot of (small) things in this beta release 0.3.0:
- Multi-processing safety: it's a very limited version of multi-processing safety, as we check only the PID when getting a connection object.
- No more `connection.meta`: there is few use of this. The way to go today is to use only the official ElasticSearch client, that already expose an interface to plug your own transport. Djangoes is here to help you manage connections and indices, not to replace the elasticsearch client.
- Test improvement: you might want to use the provided `TestCase` from `djangoes`, it will help you a bit.

As usual, this release is not a production-ready release, and there are many things I would like to add, remove, and modify. The internal API is not stable, nor really is the public API.

The next release should focus on the indices management, maybe using the equivalent of `connection` and `connections` objects, to access meta-data (such as the settings, the mapping, etc.).

In version 0.1.x, the backend was configured as the database backend is in Django. After further discussion, it appears that it is only a "legacy choice" made by Django, that should not be followed.

So now, instead of a module, the `ENGINE` key is supposed to be the path to a class.

The documentation has been updated with more information - and even more are coming.

I'm very exited to continue this project, I've a lot of ideas, but at the moment, I only added a little shortcut (`alias_names`). More soon!

As seen in 6a51567092441d7268206411dd6ddb6c864ccccc, it looks like the `params` positional argument used in the `elasticsearch` library is, in fact, not used directly, but created by a decorator, using the keywords arguments.

This release fix this annoying bug.

Bug happens, and this time it was found by configuring two connections using the same index. It raised when configuring connections.

One step forward!

OK. Bad news: `install_requires` is just a nightmare when you have to deal with local version and other specific versions in real life project.

I prefer to simply remove `install_requires` than dealing with the setuptools source code.

Good thing it's not yet production ready.