You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In current version (1.6), on a fresh project, django tries to generate migrations that seem to change the storage class and the choices:
> python manage.py makemigrations
Migrations for 'import_export_celery':
/usr/local/lib/python3.11/site-packages/import_export_celery/migrations/0010_alter_exportjob_file_alter_importjob_change_summary_and_more.py
- Alter field file on exportjob
- Alter field change_summary on importjob
- Alter field file on importjob
> cat /usr/local/lib/python3.11/site-packages/import_export_celery/migrations/0010_alter_exportjob_file_alter_importjob_change_summary_and_more.py
# Generated by Django 4.2.1 on 2023-09-23 14:01
import config.custom_storages
from django.db import migrations
import import_export_celery.fields
class Migration(migrations.Migration):
dependencies = [
('import_export_celery', '0009_alter_exportjob_options_alter_importjob_options_and_more'),
]
operations = [
migrations.AlterField(
model_name='exportjob',
name='file',
field=import_export_celery.fields.ImportExportFileField(max_length=255, storage=config.custom_storages.TempFileStorage(), upload_to='django-import-export-celery-export-jobs', verbose_name='exported file'),
),
migrations.AlterField(
model_name='importjob',
name='change_summary',
field=import_export_celery.fields.ImportExportFileField(blank=True, null=True, storage=config.custom_storages.TempFileStorage(), upload_to='django-import-export-celery-import-change-summaries', verbose_name='Summary of changes made by this import'),
),
migrations.AlterField(
model_name='importjob',
name='file',
field=import_export_celery.fields.ImportExportFileField(max_length=255, storage=config.custom_storages.TempFileStorage(), upload_to='django-import-export-celery-import-jobs', verbose_name='File to be imported'),
),
]
This is effectivelly the same issue as reported in #30 but the error is different + I prepared a PR with a fix, so I opened a new issue.
The text was updated successfully, but these errors were encountered:
In current version (1.6), on a fresh project, django tries to generate migrations that seem to change the storage class and the choices:
This is effectivelly the same issue as reported in #30 but the error is different + I prepared a PR with a fix, so I opened a new issue.
The text was updated successfully, but these errors were encountered: