Re: [Django] #34856: Running tests with historical migrations that contain index together fails with TypeError.

2023-09-20 Thread Django
#34856: Running tests with historical migrations that contain index together 
fails
with TypeError.
---+--
 Reporter:  Sage Abdullah  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Migrations |  Version:  dev
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Sage Abdullah):

 Replying to [comment:3 David Sanders]:
 > PS: If you disagree with the removal at the end of deprecation feel free
 to start a thread on the Django forum:
 https://www.djangoproject.com/community/

 Thanks! I don't mind the removal itself, though I wonder if the release
 notes should be updated to better reflect the fact that squashing the
 migrations will be mandatory? The current wording seems to suggest it's
 optional. That said, this ticket is probably enough as additional
 documentation about this issue if anyone else encounters it in the future.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018ab31be4cd-41fd1c3a-1f6e-4334-87fe-d0666e577015-00%40eu-central-1.amazonses.com.


Re: [Django] #34856: Running tests with historical migrations that contain index together fails with TypeError.

2023-09-20 Thread Django
#34856: Running tests with historical migrations that contain index together 
fails
with TypeError.
---+--
 Reporter:  Sage Abdullah  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Migrations |  Version:  dev
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by David Sanders):

 PS: If you disagree with the removal at the end of deprecation feel free
 to start a thread on the Django forum:
 https://www.djangoproject.com/community/

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018ab314d364-f7e608a9-ca02-4ba9-b319-39b8e344df88-00%40eu-central-1.amazonses.com.


Re: [Django] #34856: Running tests with historical migrations that contain index together fails with TypeError.

2023-09-20 Thread Django
#34856: Running tests with historical migrations that contain index together 
fails
with TypeError.
---+--
 Reporter:  Sage Abdullah  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Migrations |  Version:  dev
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by David Sanders):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 I was about to reply linking to the 4.2 release notes then saw you
 answered your own question:

 > To add, the ​4.2 release notes do say the following though:
 > ...
 > But with the problem in this ticket, it seems squashing the migrations
 will be mandatory?

 Yes :)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018ab30e801a-4829da8a-3b6d-49fe-a320-9c50ff6e984d-00%40eu-central-1.amazonses.com.


Re: [Django] #34856: Running tests with historical migrations that contain index together fails with TypeError.

2023-09-20 Thread Django
#34856: Running tests with historical migrations that contain index together 
fails
with TypeError.
---+--
 Reporter:  Sage Abdullah  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Migrations |  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Sage Abdullah):

 To add, the [https://docs.djangoproject.com/en/dev/releases/4.2/#index-
 together-option-is-deprecated-in-favor-of-indexes 4.2 release notes] do
 say the following though:

 > Next, consider squashing migrations to remove `index_together` from
 historical migrations.
 > The `AlterIndexTogether` migration operation is now officially supported
 only for pre-Django 4.2 migration files. For backward compatibility
 reasons, it’s still part of the public API, and there’s no plan to
 deprecate or remove it, but it should not be used for new migrations. Use
 `AddIndex` and `RemoveIndex` operations instead.

 But with the problem in this ticket, it seems squashing the migrations
 will be mandatory?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018ab30c5fd6-8dfa6140-d3c1-4537-a8ff-71905e606d18-00%40eu-central-1.amazonses.com.