Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Performance regression using FileField and Django 3.1
See original GitHub issueI’ve met problem with using dirtyfields for FileField. Previous Django version used simpler implementation of __getstate__, and 3.1 add instance to state, so deepcopy also copies instance, which is much slower and consume more memory.
Django changes: https://github.com/django/django/commit/f600e3fad6e92d9fe1ad8b351dc8446415f24345 deepcopy: https://github.com/romgar/django-dirtyfields/blob/develop/src/dirtyfields/dirtyfields.py#L95
_Originally posted by @ron8mcr in https://github.com/romgar/django-dirtyfields/issues/153#issuecomment-678922807_
Issue Analytics
- State:
- Created 3 years ago
- Comments:10
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hello! Any update on this issue? We are encountering this on a FileField, it doubles the time of our test pipeline. Is there any way to ignore this field from the dirty fields method?
Fixed in #203