Updated XapianEngine module path
Updated XapianEngine module path
Fixed a few typos in docs.
Update README.rst

Update 1.2.6 link to 1.2.7
Fixed deprecation warning

django.conf.urls.defaults is now deprecated. Use django.conf.urls instead.
Maintain Django 1.3 compatibility
Removed star imports
Note enabling INCLUDE_SPELLING requires a reindex.
Fixed the imports that would stomp on each other.

Thanks to codeinthehole, Attorney-Fee & imacleod for pointing this out.
Further docs on autocomplete.
That second colon matters.
Fixed the docs on debugging to cover v2. Thanks to eltesttox for the report.
Because Windows.
Pass active backend to index queryset calls (closes #534)

Now the Index index_queryset() and read_queryset() methods will be called with
the active backend name so they can optionally perform backend-specific
filtering.

This is extremely useful when using something like Solr cores to maintain
language specific backends, allowing an Index to select the appropriate
documents for each language::

    def index_queryset(self, using=None):
        return Post.objects.filter(language=using)

Changes:
    * clear_index, update_index and rebuild_index all default to processing
      *every* backend. ``--using`` may now be provided multiple times to select
      a subset of the configured backends.
    * Added examples to the Multiple Index documentation page
Solr: use nested query syntax for AltParser queries

The previous implementation would, given a query like this::

    sqs.filter(content=AltParser('dismax', 'library', qf="title^2 text" mm=1))

generate a query like this::

    {!dismax v=library qf="title^2 text" mm=1}

This works in certain situations but causes Solr to choke while parsing it
when Haystack wraps this term in parentheses::

    org.apache.lucene.queryParser.ParseException: Cannot parse '({!dismax mm=1 qf='title^2 text institution^0.8' v=library})':
    Encountered " &lt;RANGEEX_GOOP&gt; "qf=\'title^1.25 "" at line 1, column 16.

The solution is to use the nested query syntax described here:

    http://searchhub.org/2009/03/31/nested-queries-in-solr/

This will produce a query like this, which works with Solr 3.6.2::

    (_query_:"{!edismax mm=1 qf='title^1.5 text institution^0.5' v=library}")

Leaving the actual URL query string looking like this::

    q=%28_query_%3A%22%7B%21edismax+mm%3D1+qf%3D%27title%5E1.5+text+institution%5E0.5%27+v%3Dlibrary%7D%22%29

* Tests updated for the new query generation output
* A Solr backend task was added to actually run the dismax queries and verify
  that we're not getting Solr 400s errors due to syntax gremlins
Setup custom routers before settings up signal processor.

Fixes https://github.com/toastdriven/django-haystack/issues/727
Better Solr AltParser quoting (closes #730)

Previously the Solr AltParser implementation embedded the search term as an
attribte inside the {!…} construct, which required it to be doubly escaped.

This change contributed by @ivirabyan moves the value outside the query,
requiring only our normal quoting:

    q=(_query_:"{!edismax}Assassin's Creed")

instead of:

    q=(_query_:"{!edismax v='Assassin's Creed'}")

Thanks @ivirabyan for the patch!
ElasticSearch: fix AltParser test

AltParser queries are still broken but that fucntionality has only been
listed as supported on Solr.
Remove redundant __name__ assignment on SearchView

__name__ was being explicitly set to a value which was the same as the
default value.

Additionally corrected the obsolete __name__ method declaration in the
documentation which reflected the code prior to SHA:89d8096 in 2010.
Simple: removed conflicting score field from raw result objects

This keeps consistency with the Solr backend, which resolves this conflict
in the same manner.