Re: [Django] #29233: Proposing to change the spelling of "how-to's"

[Django]

#29233: Proposing to change the spelling of "how-to's"
---+--
 Reporter:  marton bognar  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  2.0
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+--

Comment (by marton bognar):

 Another solution to reduce ambiguity could be to use the term "how-to
 guides", as it is used in other places in the documentation.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.5eab8b1213aa0b8d2099fda65c94be92%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29233: Proposing to change the spelling of "how-to's"

[Django]

#29233: Proposing to change the spelling of "how-to's"
---+--
 Reporter:  marton bognar  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  2.0
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+--
Description changed by marton bognar:

Old description:

> In English grammar apostrophes should not be used to make regular nouns
> plural [https://www.grammarbook.com/punctuation/apostro.asp (Rule 2b.)].
> In the current documentation (at least in some places, including the
> default screen for new Django installations) the word is written as "how-
> to's" instead of the form "how-tos". One could argue whether "how-to" is
> a regular noun, but I think in this case more confusion can stem from the
> first form than the second.
>
> I will gladly create a PR for this issue if you agree with me, but I'm
> not sure whether the locale message id (msgid "Topics, references, 
> how-to's") should be changed as well or preserved in the current form for
> possible legacy reasons.

New description:

 In English grammar apostrophes should not be used to make regular nouns
 plural [https://www.grammarbook.com/punctuation/apostro.asp (Rule 2b.)].
 In the current documentation (at least in some places, including the
 default screen for new Django installations) the word is written as "how-
 to's" instead of the form "how-tos". One could argue whether "how-to" is a
 regular noun, but I think in this case more confusion can stem from the
 usage of the first form than the second.

 I will gladly create a PR for this issue if you agree with me, but I'm not
 sure whether the locale message id (msgid "Topics, references,  how-
 to's") should be changed as well or preserved in the current form for
 possible legacy reasons.

--

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.1fb9b8fd98d7031acf20536727058a54%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #29233: Proposing to change the spelling of "how-to's"

[Django]

#29233: Proposing to change the spelling of "how-to's"
-+
   Reporter:  marton bognar  |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Documentation  |Version:  2.0
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  1  |
-+
 In English grammar apostrophes should not be used to make regular nouns
 plural [https://www.grammarbook.com/punctuation/apostro.asp (Rule 2b.)].
 In the current documentation (at least in some places, including the
 default screen for new Django installations) the word is written as "how-
 to's" instead of the form "how-tos". One could argue whether "how-to" is a
 regular noun, but I think in this case more confusion can stem from the
 first form than the second.

 I will gladly create a PR for this issue if you agree with me, but I'm not
 sure whether the locale message id (msgid "Topics, references,  how-
 to's") should be changed as well or preserved in the current form for
 possible legacy reasons.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/055.afc93305513df3d4cecf24319f9e54f1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29184: TabularInline read-only fields ignore ModelForm Meta.labels and help_texts

[Django]

#29184: TabularInline read-only fields ignore ModelForm Meta.labels and 
help_texts
-+-
 Reporter:  David Sanders|Owner:  Danil
 |  Kozyatnikov
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  2.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  readonly,| Triage Stage:  Accepted
  help_texts, labels |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"274e3e27f366bddbf1bb13b40c3c7b95195c496e" 274e3e2]:
 {{{
 #!CommitTicketReference repository=""
 revision="274e3e27f366bddbf1bb13b40c3c7b95195c496e"
 Fixed #29184 -- Made TabularInline respect model form's Meta.labels and
 help_texts.
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.081975c822ad8978ea55d093649f3f02%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29229: QuerySet.values_list() combined with .extra() or .annotate() may produce wrong .union()

[Django]

#29229: QuerySet.values_list() combined with .extra() or .annotate() may produce
wrong .union()
-+-
 Reporter:  master   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  union values_list| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1
 * version:  master => 2.0
 * easy:  1 => 0
 * stage:  Unreviewed => Accepted


Comment:

 [https://github.com/django/django/pull/9796 PR]

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.e8aedc33db3b1187e08fc05f2566e301%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28975: Skip automatic creation of postgis extension if it already exists

[Django]

#28975: Skip automatic creation of postgis extension if it already exists
-+-
 Reporter:  sphrak   |Owner:  sphrak
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  GIS  |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  create extension,|  worksforme
  postgis, psycopg2, postgresql  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * status:  assigned => closed
 * component:  Database layer (models, ORM) => GIS
 * resolution:   => worksforme


Comment:

 As Shai said on the mailing list, `CREATE EXTENSION IF NOT EXISTS
 postgis;` doesn't seem to fail if the extension already exists, even if
 the user isn't a superuser. I see `NOTICE:  extension "postgis" already
 exists, skipping` in this case.  Unless I'm misunderstanding the original
 report, I don't see a need to make any changes.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.ba2eae240d83e1e4c0d03e2922eb270f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28554: Add support for multiple file fields

[Django]

#28554: Add support for multiple file fields
-+-
 Reporter:  Johannes Hoppe   |Owner:  Johannes
 |  Hoppe
 Type:  New feature  |   Status:  assigned
Component:  File |  Version:  master
  uploads/storage|
 Severity:  Normal   |   Resolution:
 Keywords:  file, storage,   | Triage Stage:  Accepted
  upload, multiple, input|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.6e6b5a998fc4d7a772919c428f1c9ddb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29103: sqlmigrate produces byte literal in SQL for one-off string default value in TextField, CharField on MySQL

[Django]

#29103: sqlmigrate produces byte literal in SQL for one-off string default 
value in
TextField, CharField on MySQL
-+-
 Reporter:  Qlimax   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  2.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  sqlmigrate, byte,| Triage Stage:  Ready for
  default value, one-off |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"3c4ff2176323dd20507e35658599da220fbe1741" 3c4ff217]:
 {{{
 #!CommitTicketReference repository=""
 revision="3c4ff2176323dd20507e35658599da220fbe1741"
 Fixed #29103 -- Removed bad 'b'-prefix added by MySQL's
 SchemaEditor.quote_value().
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.2da7f59fc528ae9650203d832dfe63fb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26291: loaddata cannot deserialize fixtures with forward references and natural foreign keys

[Django]

#26291: loaddata cannot deserialize fixtures with forward references and natural
foreign keys
-+-
 Reporter:  Peter Inglesby   |Owner:  Peter
 |  Inglesby
 Type:  New feature  |   Status:  assigned
Component:  Core |  Version:  1.9
  (Serialization)|
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  0 => 1
 * stage:  Ready for checkin => Accepted


Comment:

 I did a brief review of the patch.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.21e4128f2c16e213823b7955062506ff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25367: Allow expressions in .filter() calls

[Django]

#25367: Allow expressions in .filter() calls
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Matthew
 Type:   |  Schinckel
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_docs:  1 => 0
 * stage:  Ready for checkin => Accepted


Comment:

 After some reviews, the patch is still in progress.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.9a9fed017d18df612b37f8d0e3fe85a8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28600: Add prefetch related support to RawQuerySet

[Django]

#28600: Add prefetch related support to RawQuerySet
-+-
 Reporter:  Adnan Umer   |Owner:  Adnan
 |  Umer
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.b04f79fa5b2a7e8c21421004dd42b39f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29226: @modify_settings append/remove/prepend is affected by dictionary order

[Django]

#29226: @modify_settings append/remove/prepend is affected by dictionary order
-+-
 Reporter:  Manuel Kaufmann  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Testing framework|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  tests,   | Triage Stage:  Accepted
  modify_settings|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * type:  Uncategorized => Cleanup/optimization


Comment:

 If I understand correctly, the requirement to nest `@modify_settings`
 isn't present if targeting Python 3.6+ because dicts are ordered there.
 I'm not sure what would give an expectation of some order of operations in
 older versions of Python. I'm not sure it's worth documenting anything
 about this.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.c502160ac9a07bd5c70c386fbff833c2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27392: Remove "Tests that", "Ensures that", etc. from test docstings

[Django]

#27392: Remove "Tests that", "Ensures that", etc. from test docstings
-+-
 Reporter:  Tim Graham   |Owner:  Harshit
 Type:   |  Agrawal
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 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 Tim Graham):

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


Comment:

 This ticket has too many poor attempts and is causing more distraction
 than it's worth.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.dd37f13cb550087357924a6576058398%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29182: SQLite database migration breaks ForeignKey constraint, leaving __old in db schema

[Django]

#29182: SQLite database migration breaks ForeignKey constraint, leaving
__old in db schema
--+
 Reporter:  ezaquarii |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  2.0
 Severity:  Normal|   Resolution:
 Keywords:  sqlite migration  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham):

 * type:  Uncategorized => Cleanup/optimization


-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.605611b3331d376e57a7e8eabf4ae965%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29074: makemessages duplicates .po file headers when fed with empty strings

[Django]

#29074: makemessages duplicates .po file headers when fed with empty strings
-+-
 Reporter:  instantname  |Owner:  Manthan
 |  Sharma
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  1.11
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  i18n | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Hasan Ramezani):

 It seems the problem goes from `msgmerge` in `def write_po_file`. I think
 merge process destroy the file structure.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.de29a983548c56c22e6c43e823841a6e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28510: Add JSON reporter for technical_500_response (debug) view

[Django]

#28510: Add JSON reporter for technical_500_response (debug) view
-+-
 Reporter:  Ivan Chernoff|Owner:  Ivan Chernoff
 Type:  New feature  |   Status:  closed
Component:  Error reporting  |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 The reporter has withdrawn the ticket, "I don't think this is a needed one
 after all."

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.86557e54a071f0617e8353ff5daddd2f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29226: @modify_settings append/remove/prepend is affected by dictionary order

[Django]

#29226: @modify_settings append/remove/prepend is affected by dictionary order
-+-
 Reporter:  Manuel Kaufmann  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Testing framework|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  tests,   | Triage Stage:  Accepted
  modify_settings|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz):

 I'm not sure `append`/`removed` were designed to run in the same
 `modify_settings` and the same setting.
 What about documenting to nest `modify_settings` calls for this use case?

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.1ccd417b4258a0f3f0ee2bcb7ee57e74%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29226: @modify_settings append/remove/prepend is affected by dictionary order

[Django]

#29226: @modify_settings append/remove/prepend is affected by dictionary order
-+-
 Reporter:  Manuel Kaufmann  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Testing framework|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  tests,   | Triage Stage:  Accepted
  modify_settings|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Markus Holtermann):

 * stage:  Unreviewed => Accepted


Comment:

 Sounds like a legitimate problem.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.d43ea71f33cf65977b96bfa8ebc1c4da%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.