Skip to content

Conversation

ggainey
Copy link
Contributor

@ggainey ggainey commented Sep 23, 2025

closes #5324.

@ggainey
Copy link
Contributor Author

ggainey commented Sep 23, 2025

May require plugin-changes to adapt to django-import-export:4.x - DO NOT MERGE until 3.100.

@ggainey ggainey force-pushed the django_impexp_4 branch 2 times, most recently from 922ff33 to d2916d8 Compare September 23, 2025 18:56
Comment on lines +65 to +66
if row[checksum] == "" or checksum not in settings.ALLOWED_CONTENT_CHECKSUMS:
del row[checksum]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Random unrelated question: Do we recalculate missing checksums on import? Or do both systems need the same setting there?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fine question, and the answers are "no we don't" and "...huh." I expect that, "in the wild", systems being exported-to have the same settings as the system being exported-from, so it just never came up. But it's a de-facto standard, not a de-jure one :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Make the import/export machinery compatible with django-import-export>=4.0

2 participants