Remove unused / unreferenced dependencies.
(Django is the core dependency, django-reversion is referenced and so can be left as is…no idea how well it's supported, Sphinx will be needed if recompiling docs)
The fact these are out of sync (no models.py file) with the main adminlinkinline folder adds more weight to the notion they cannot possibly be used for anything meaningful.
Just in case, let's add the folder to the .gitignore file so it's less likely to come back.
Update Sphinx to a version that works so the following command will actually build something instead of giving a cryptic error:
/adminlinkinline/docs/ > make html
Pylint - unused imports.
We shouldn't be in the business of manually maintaining these indexes. It's un-Pythonic, and indeed the one in foreignkey.py is already a bug:
- a Python 2.7 string wrapped in brackets is not converted to a tuple
- it requires a comma somewhere, e.g. `('RenderLink',)` to turn it into a tuple
- hence foreignkey.__all__ is defined from the iterable string 'RenderLink', i.e. __all__ = ('R','e','n','d','e','r','l','i','n','k')
- and thus `from adminlinkinline.tree.admin.widgets.foreignkey import *` will fail by attempting to import `R` which should not exist

If you want to hang yourself by importing something we're importing (and not from its original location) or doing something like `from … import *` to pollute your namespace; feel free to.
Actually since the successor to this model didn't integrate with django-reversion, and we don't use it, we shouldn't have it as a requirement.
We honestly aren't supporting i18n (in our main project) just yet either, so I'm going to remove the sole reference to polib too.
Start migrating to Django 1.5 - remove some unused templates, especially those that reference to removed `adminmedia`.
Remove one-line template file.
… mostly to make it clearer that this is dead code.
Let's see if I can get away with removing this crazy file and keep our main project working...
Since that works fine, most of this docstring is misleading. Since the first part is at best out of date (contains no reference to the fact there are two classes defined in the module), I really cannot be bothered fixing it - yes it's technically a PEP257 violation, but I'd rather no docstring than a misleading docstring, and any IDE should be capable of giving you a far better indication what is going on in the module.
Fix many PEP8 line-length violations. Because onereallyreallyreallylonglineofcodethatseemslikeitgoesonforever is kind of hard to read :)
The `adminoverride.js` is needed to `dismissAddAnotherPopup`…though why that needs so many lines I have no idea.
Can't find any reason to keep `menu-sort.js` around.
Hunch: We don't need breadcrumbs for the add view, which looks like the only good reason to need to have it on the parent model (otherwise it should be possible to inherit from both FKAwareMA and InvisibleMA…i.e. mix in both pieces of functionality if that was required).
Which means there's virtually no value keeping the _CanFindParentLink class, just merge it into InvisibleModelAdmin.
These docs suggest the original intent of "InvisibleModelAdmin" was to NOT show the child model in the admin interface listing.

Which would imply that having a flag like "invisible_in_admin" on such a class is just silly, and a sign that the class may have too many responsibilities and should be broken down into separate mixins if such responsibilities are actually required.
Fix the hiding models from the admin index regression (I probably introduced back when removing the crazy index.html file) in a far cleaner way.
It makes sense to have something like this be a more mixin-oriented class (include it if you actually need it), it might even trigger renaming InvisibleModelAdmin to something else.
Oh…I think the TODO means it never worked as advertised =/
https://github.com/specialunderwear/django-easymode/commit/7c4239bf12684c0263a0d72f487102c497e07cfa

So make it work as advertised! Nice bug fix for our content editors :)
Rename `parent_model` to `parent_model_url`
Actually there's a cleaner way to do the same thing by overriding `response_change` - so we can decouple the changes further and also save another round-trip to the DB on save at least.