[Django] #32900: Migrations questioner uses bad grammar

[Django]

#32900: Migrations questioner uses bad grammar
+
   Reporter:  Christian Ullrich |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Migrations|Version:  3.2
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 The interactive questioner, when it asks what to do about changes in
 nullability or adding a NOT NULL field, provides multiple options. Some of
 these speak ''to'' the user, some ''as'' the user.

 One example of several:

 {{{
 You are trying to add a non-nullable field 'id' to mymodel without a
 default; we can't do that (the database needs something to populate
 existing rows).
 Please select a fix:
  1) Provide a one-off default now (will be set on all existing rows with a
 null value for this column)
  2) Quit, and let me add a default in models.py
 }}}

 In option 1, Django offers the user the choice of entering the default
 value. Option 2 instead is the user telling Django what to do.

 Each time I read this, I'm asking myself who the "me" in option 2 is. The
 most egregious case is in django.db.migrations.ask_not_null_alteration():
 "[...] let ''me'' handle existing rows [...] (e.g. because ''you'' added a
 RunPython [...]". In this sentence, "me" and "you" are the same.

 Fix: Either reword the "provide" options to say "Let me enter a one-off
 default now", or the "let me" options to the same style as the "provide"
 options. I am very much in favor of the latter because I think this "me,
 the user" style is terrible.

-- 
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/053.9629f5d6362a82e810c9c4f6b7372d8e%40djangoproject.com.

Re: [Django] #32900: Migrations questioner uses bad grammar

[Django]

#32900: Migrations questioner uses bad grammar
-+-
 Reporter:  Christian Ullrich|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  3.2
 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
-+-
Description changed by Christian Ullrich:

Old description:

> The interactive questioner, when it asks what to do about changes in
> nullability or adding a NOT NULL field, provides multiple options. Some
> of these speak ''to'' the user, some ''as'' the user.
>
> One example of several:
>
> {{{
> You are trying to add a non-nullable field 'id' to mymodel without a
> default; we can't do that (the database needs something to populate
> existing rows).
> Please select a fix:
>  1) Provide a one-off default now (will be set on all existing rows with
> a null value for this column)
>  2) Quit, and let me add a default in models.py
> }}}
>
> In option 1, Django offers the user the choice of entering the default
> value. Option 2 instead is the user telling Django what to do.
>
> Each time I read this, I'm asking myself who the "me" in option 2 is. The
> most egregious case is in django.db.migrations.ask_not_null_alteration():
> "[...] let ''me'' handle existing rows [...] (e.g. because ''you'' added
> a RunPython [...]". In this sentence, "me" and "you" are the same.
>
> Fix: Either reword the "provide" options to say "Let me enter a one-off
> default now", or the "let me" options to the same style as the "provide"
> options. I am very much in favor of the latter because I think this "me,
> the user" style is terrible.

New description:

 The interactive questioner, when it asks what to do about changes in
 nullability or adding a NOT NULL field, provides multiple options. Some of
 these speak ''to'' the user, some ''as'' the user.

 One example of several:

 {{{
 You are trying to add a non-nullable field 'id' to mymodel without a
 default; we can't do that (the database needs something to populate
 existing rows).
 Please select a fix:
  1) Provide a one-off default now (will be set on all existing rows with a
 null value for this column)
  2) Quit, and let me add a default in models.py
 }}}

 In option 1, Django offers the user the choice of entering the default
 value. Option 2 instead is the user telling Django what to do.

 Each time I read this, I'm asking myself who the "me" in option 2 is. The
 most egregious case is in
 InteractiveMigrationQuestioner.ask_not_null_alteration(): "[...] let
 ''me'' handle existing rows [...] (e.g. because ''you'' added a RunPython
 [...]". In this sentence, "me" and "you" are the same.

 Fix: Either reword the "provide" options to say "Let me enter a one-off
 default now", or the "let me" options to the same style as the "provide"
 options. I am very much in favor of the latter because I think this "me,
 the user" style is terrible.

--

-- 
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/068.3d746f841d27f2c4a59513101c91af13%40djangoproject.com.

Re: [Django] #32900: Migrations questioner uses bad grammar

[Django]

#32900: Migrations questioner uses bad grammar
--+
 Reporter:  Christian Ullrich |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  3.2
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Jacob Walls):

 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 Thanks, this has also occurred to me. For the example you quoted in full,
 perhaps: "Quit, so that a default in models.py can be added later." And
 something similarly passive for the other cases, avoiding the use of "you"
 entirely.

-- 
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/068.fcb673219260b1cd3c81b70969062037%40djangoproject.com.

Re: [Django] #32900: Migrations questioner uses bad grammar

[Django]

#32900: Migrations questioner uses bad grammar
-+-
 Reporter:  Christian Ullrich|Owner:  Mateo
 Type:   |  Radman
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mateo Radman):

 * owner:  nobody => Mateo Radman
 * status:  new => assigned


-- 
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/068.1eb8c8758daf2de9fae4dbaab0e04e76%40djangoproject.com.

Re: [Django] #32900: Migrations questioner uses bad grammar

[Django]

#32900: Migrations questioner uses bad grammar
-+-
 Reporter:  Christian Ullrich|Owner:  Mateo
 Type:   |  Radman
  Cleanup/optimization   |   Status:  closed
Component:  Migrations   |  Version:  3.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mateo Radman):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 [https://github.com/django/django/pull/14607 PR] is ready. Let me know if
 you have any suggestions regarding phrasing the questions.

-- 
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/068.70e78e0eab32d130f6a6fa6f48345ae8%40djangoproject.com.

Re: [Django] #32900: Migrations questioner uses bad grammar

[Django]

#32900: Migrations questioner uses bad grammar
-+-
 Reporter:  Christian Ullrich|Owner:  Mateo
 Type:   |  Radman
  Cleanup/optimization   |   Status:  new
Component:  Migrations   |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

 * status:  closed => new
 * has_patch:  0 => 1
 * resolution:  fixed =>


Comment:

 When adding a PR, the correct action is to check "Has patch" rather than
 close the ticket. See
 [https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
 tickets/ Triaging tickets] and the "According to the ticket's flags, the
 next step(s) to move this issue forward are:" section of each open ticket.

-- 
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/068.e853c34ca051233104ead7fcf95d7fff%40djangoproject.com.

Re: [Django] #32900: Migrations questioner uses bad grammar

[Django]

#32900: Migrations questioner uses bad grammar
-+-
 Reporter:  Christian Ullrich|Owner:  Muhammad
 Type:   |  Hammad
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Muhammad Hammad):

 * owner:  Mateo Radman => Muhammad Hammad
 * status:  new => assigned


-- 
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/068.0cc5ae689c9354cb38d30cd55cb6d997%40djangoproject.com.

Re: [Django] #32900: Migrations questioner uses bad grammar

[Django]

#32900: Migrations questioner uses bad grammar
-+-
 Reporter:  Christian Ullrich|Owner:  Mateo
 Type:   |  Radman
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  Muhammad Hammad => Mateo Radman


Comment:

 Muhammad, this ticket is already assigned to Mateo. Please try to find a
 ticket that is not assigned.

-- 
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/068.65b53cf0c64aec68e631c12f15ec9087%40djangoproject.com.

Re: [Django] #32900: Migrations questioner uses bad grammar

[Django]

#32900: Migrations questioner uses bad grammar
-+-
 Reporter:  Christian Ullrich|Owner:  Mateo
 Type:   |  Radman
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mateo Radman):

 I think [https://github.com/django/django/pull/14607 PR] is ready to be
 merged. Thanks for everyone’s suggestions and involvement.

-- 
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/068.d3a8f780e00ac1a63181d804cbcc377d%40djangoproject.com.

Re: [Django] #32900: Migrations questioner uses bad grammar

[Django]

#32900: Migrations questioner uses bad grammar
-+-
 Reporter:  Christian Ullrich|Owner:  Mateo
 Type:   |  Radman
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1
 * needs_tests:  0 => 1


-- 
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/068.70617209920c52326637519548ea3726%40djangoproject.com.

Re: [Django] #32900: Migrations questioner uses bad grammar

[Django]

#32900: Migrations questioner uses bad grammar
-+-
 Reporter:  Christian Ullrich|Owner:  Mateo
 Type:   |  Radman
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mateo Radman):

 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0


-- 
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/068.78944fd0fe713df3ab6785d962adcf7d%40djangoproject.com.

Re: [Django] #32900: Migrations questioner uses bad grammar

[Django]

#32900: Migrations questioner uses bad grammar
-+-
 Reporter:  Christian Ullrich|Owner:  Mateo
 Type:   |  Radman
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_tests:  0 => 1


-- 
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/068.20221063fb8a26fcd3768606dd3c8ce8%40djangoproject.com.

Re: [Django] #32900: Migrations questioner uses bad grammar

[Django]

#32900: Migrations questioner uses bad grammar
-+-
 Reporter:  Christian Ullrich|Owner:  Mateo
 Type:   |  Radman
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mateo Radman):

 * needs_tests:  1 => 0


-- 
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/068.aef05d5d51311214ec323da3de4eab99%40djangoproject.com.

Re: [Django] #32900: Migrations questioner uses bad grammar

[Django]

#32900: Migrations questioner uses bad grammar
-+-
 Reporter:  Christian Ullrich|Owner:  Mateo
 Type:   |  Radman
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * stage:  Accepted => Ready for checkin


-- 
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/068.de4b93c4d4fd2d3ff98cf1a45fc3bb81%40djangoproject.com.

Re: [Django] #32900: Migrations questioner uses bad grammar

[Django]

#32900: Migrations questioner uses bad grammar
-+-
 Reporter:  Christian Ullrich|Owner:  Mateo
 Type:   |  Radman
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"d00fb4d2d6f375ace2b4fe35a4acde8e476000d2" d00fb4d2]:
 {{{
 #!CommitTicketReference repository=""
 revision="d00fb4d2d6f375ace2b4fe35a4acde8e476000d2"
 Refs #32900 -- Added test for ignoring the default value in
 InteractiveMigrationQuestioner.ask_not_null_alteration().
 }}}

-- 
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/068.8d012bc1de773b5700ce1b4ca45a9ad1%40djangoproject.com.

Re: [Django] #32900: Migrations questioner uses bad grammar

[Django]

#32900: Migrations questioner uses bad grammar
-+-
 Reporter:  Christian Ullrich|Owner:  Mateo
 Type:   |  Radman
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"61c5eae516257d4827b8a12da2b714f05ac88a9f" 61c5eae]:
 {{{
 #!CommitTicketReference repository=""
 revision="61c5eae516257d4827b8a12da2b714f05ac88a9f"
 Refs #32900 -- Added makemigrations tests for messages in interactive
 mode.
 }}}

-- 
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/068.ab302624402f5fa0d7cfbbc3de33b690%40djangoproject.com.

Re: [Django] #32900: Migrations questioner uses bad grammar

[Django]

#32900: Migrations questioner uses bad grammar
-+-
 Reporter:  Christian Ullrich|Owner:  Mateo
 Type:   |  Radman
  Cleanup/optimization   |   Status:  closed
Component:  Migrations   |  Version:  3.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"02bc7161ec477afd4a7b328936eb8adac078d7b9" 02bc7161]:
 {{{
 #!CommitTicketReference repository=""
 revision="02bc7161ec477afd4a7b328936eb8adac078d7b9"
 Fixed #32900 -- Improved migrations questioner prompts.
 }}}

-- 
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/068.c88fe7aa332afea1a95032d49beb6596%40djangoproject.com.

Re: [Django] #32900: Migrations questioner uses bad grammar

[Django]

#32900: Migrations questioner uses bad grammar
-+-
 Reporter:  Christian Ullrich|Owner:  Mateo
 Type:   |  Radman
  Cleanup/optimization   |   Status:  closed
Component:  Migrations   |  Version:  3.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"aa0d796e37c4b8056148de2f68726aae9d20399c" aa0d796e]:
 {{{
 #!CommitTicketReference repository=""
 revision="aa0d796e37c4b8056148de2f68726aae9d20399c"
 Refs #32900 -- Restored '[y/N]' in questioner prompt when merging
 migrations.

 Regression in 02bc7161ec477afd4a7b328936eb8adac078d7b9.
 }}}

-- 
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/068.080c71dd6cd5210b3ee81a46e0d67294%40djangoproject.com.

Re: [Django] #32900: Migrations questioner uses bad grammar

[Django]

#32900: Migrations questioner uses bad grammar
-+-
 Reporter:  Christian Ullrich|Owner:  Mateo
 Type:   |  Radman
  Cleanup/optimization   |   Status:  closed
Component:  Migrations   |  Version:  3.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"1aada25eeb8debabe5e1a50d64843b085a95237b" 1aada25e]:
 {{{
 #!CommitTicketReference repository=""
 revision="1aada25eeb8debabe5e1a50d64843b085a95237b"
 [4.0.x] Refs #32900 -- Restored '[y/N]' in questioner prompt when merging
 migrations.

 Regression in 02bc7161ec477afd4a7b328936eb8adac078d7b9.

 Backport of aa0d796e37c4b8056148de2f68726aae9d20399c from main
 }}}

-- 
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/068.a2fdc3adbbe43db9c679f22bd1885ac6%40djangoproject.com.