Python 3 and Django 1.10, 1.11 support

2.0.1 Final

Signed-off-by: Don Naegely <[email protected]>

Support ForeignKey.to_field

1.1.10 Final

Signed-off-by: Byron Ruth <[email protected]>

Django 1.8 and beyond

The 2.0.0 release drops support for Django 1.7 and below.

Support for Django 1.6 and 1.7

Features

• #14 - Support for Django 1.6
• #21 - Support for Django 1.7

Enhancements

• #18 - Multiple excluded routes can be specified for the same target

Bugs

• #18 - Prevent specifying a required route for a target more than once

Proxy Model & ModelTreeManager Enhancement

ModelTreeManager can now be initialized with a specific tree rather than assume a tree given a model (since a model could have multiple trees associated with it.)

A new optional argument model has been added for query_string_for_field and query_condition for specifying the model the field is coming from. This is specifically to support proxy models in Django which allows for defining independent, logical models on an existing one. ModelTree can take advantage of this since different join paths will be inferred.

ModelTree hook

• Implement ModelTree.__contains__ hook for checking for pre-defined modeltrees

Bugs

• Fix ModelTreeQuerySet.raw method to use compiler.results_iter instead of constructing a RawQuery
  • See #8 and cbmi/avocado#98 for the details

Django 1.5 & Python 2.6

1.1.5

1.1.5 Release

Routes

• Add improved support for defining routes
• Annotate modeltree instances with it's alias if one exists
  • This prevents initializing redundant modeltrees for the same root model

Bugs

• Fix incorrect primary key field name on right-hand side of join
  • See #6