FieldTracker for AbstractModel children is still not stable
See original GitHub issueProblem
I have found that AbstractModelTrackerTests is not quite correct.
Since it inherited from FieldTrackerTestCase that just implements some extra assertions, there are no actual tests for this case.
Solution
I have fixed AbstractModelTrackerTests and it seems that some tests are failed for the case with models inherited from some AbstractModel with fields defined (like AbstractUser and its children)
#381 - pull request
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
django-model-utils - Bountysource
This happens with custom User model in Django 1.5 (not sure if it matters). ... Currently FieldTracker resets only the fields which were...
Read more >Choices - django-model-utils - Read the Docs
A FieldTracker can be added to a model to track changes in model fields. A FieldTracker allows querying for field changes since a...
Read more >autonomous star tracker: Topics by Science.gov
The star tracker is supposed to have the highest accuracy in stable conditions ... Its pixel resolution in not yet satisfactory for precision...
Read more >online identification algorithm: Topics by WorldWideScience.org
It is not only valuable as a reference book for star sensor designers and researchers working in pattern recognition and othe.
Read more >wordlist_no_underscores.txt - Index of /
... ragnacp-child mui-d630 fastqfilter nsurlsession-promisekit commontool rt4 ... not-working rsystem2 key-note debian-wheezy-vagrant-install stream-tools ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Would someone update me/us on the status of this? The last activity (other than bumping the versions) seems to be:
Does that mean this issue is unblocked? Is there a fix in the works?
@Natim has indicated that this is blocked upstream in Django by #30427.