… me otherwise.
…hiding the main code in a __init__ file is an antipattern.
Conflicts: docs/source/api.rst docs/source/conf.py docs/source/versions.rst pyelasticsearch/__init__.py
…the versions Erik did internally to prepare for the official 0.2 release.
…e those in subclasses.
…gs and for the remaining undocumented normal args. Link to ES docs for each call. Bump version to 0.3.2. QS params not explicitly documented are inserted into the docstrings at import type by es_kwargs itself. Everything shows up in Sphinx.
pyelasticsearch.py has two exception handlers which catch json.JSONDecodeError. Unfortunately, that was only added in simplejson 2.1.0 and because the import uses the requests.compat.json failover mechanism it's easy to install and use pyelasticsearch without having installed simplejson 2.1.0, which will produce unexpected AttributeErrors. A quick test shows that the stdlib json module in Python 2.6, 2.7 and 3.2 lacks the JSONDecodeError.
IOError: [Errno 2] No such file or directory: '/home/ubuntu/votizen/build/pyelasticsearch/docs/source/versions.rst'
I need to tag so I can use the last few backward-incompatible changes. Said changes seem to have settled down now.
…down from orbit and use a concrete term.
Really have to get these doctests running.
…nd make up the difference with documentation. It's not always obvious whether an ES API allows for multiple indexes. This was leading me to have to look aside to the docs to determine whether the kwarg was called "index" or "indexes". Let's just use the singular everywhere, and then the common case--a single index--won't result in any doc lookups. Same with doctypes.