Matthias Schoettle
Matthias Schoettle
I'm in favour of moving ahead with this. My suggestion would be to merge #276, #277 and then #258 before this one.
I’ll fix #258 ASAP to prevent blocking your PR
Hm, looks like `RenameIndex` was only added in Django 4.1: https://docs.djangoproject.com/en/4.2/ref/migration-operations/#renameindex On Django 3.2 the following operations are created: ```python operations = [ migrations.AlterIndexTogether( name='crudevent', index_together=set(), ), migrations.AddIndex( model_name='crudevent', index=models.Index(fields=['object_id',...
@jheld Can we drop Django 3.2 in a future version? It is going to be end of life soon anyway (April 2024).
With Django 5 being in beta, is there any chance we can move this forward? I suggest to drop support for older Django versions in a new version which allows...
@jheld Thanks for your quick response. I understand your view. Now that I checked a few packages, it was a bit harsh to suggest dropping support for Django 3.2 right...
@jheld See #264 and #265 for Django 5.0 support I just saw that in the Django 5.0, they recommend third-party app authors to drop support for Django < 4.2: https://docs.djangoproject.com/en/5.0/releases/5.0/#third-party-library-support-for-older-version-of-django
Thanks for fixing it and creating the extra issue (#269 for reference).
Created #277 which this PR is dependant on.
@jheld Brought this up to date with `master` which resolved the pipeline failure