[1.7.x] Fixed #23159 -- Skipped non-conrete fields in migrations.

https://code.djangoproject.com/ticket/23159

It makes sense to skip non-concrete fields in the migrations framework too.
Otherwise IMHO the way django 1.7 would treat these non-concrete fields would be really inconsistent (sad). It slighlty differs already from django models than django model forms (which is daunting), and it would differ in a new way in the migration framework (not nice at all).
I hope you can consider these points in this new awsome feature that is the migration framework. I'm pretty sure one of these two solutions won't break existing tests and would ensure maximum compatibility, hence benefit future django versions lot.