Carl Meyer

Never mind, not sure why I closed it, I'll leave it open since we don't have the feature and I'd accept it in principle (not sure what the API should...

@AlexCid No, nobody has written any code to implement the proposed feature. If they had and it had been merged, this issue would be closed.

@AndrewHows I'd think that would be possible, yeah. That's actually not a bad API for this; placing the decision on the FK side makes some sense.

I'm not sure what code this applies to, since there is no `PolymorphicModel` in django-model-utils and never has been.

No argument from me!

@romgar Not quite sure your analysis fully explains the problem. `StatusField` also sets `choices` on the field, and a change in `choices` should also trigger a new migration, independent of...

Yes, this was also a problem for `PassThroughManager` and we fixed it with Solution 2, which as you say is ugly but works (requires some care to avoid breaking pickling)....

It might be possible to fix `for_queryset_class()` so it doesn't ignore the superclass version of `get_query_set`. Specifically I'm thinking that `Queryset._clone()` accepts a `klass` argument to supply a new class...

Looks good to me! A pull request would be great; just add a test, add a note in `CHANGES.rst`, and add yourself to `AUTHORS`. I don't think this requires any...

Thanks for the report! This does look like a bug. I'm not sure if or when I'll have time to look into it, but I'd be happy to review a...