Re: [Django] #33070: Select2 doesn't load translations with subtags.

[Django]

#33070: Select2 doesn't load translations with subtags.
-+-
 Reporter:  Cleiton de Lima  |Owner:  Cleiton
 |  de Lima
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:  select2  | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|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/071.568825a8220135992929e895a4bd485e%40djangoproject.com.

Re: [Django] #33122: createsuperuser fails when using USERNAME_FIELD (was: createsuperuser bug)

[Django]

#33122: createsuperuser fails when using USERNAME_FIELD
-+-
 Reporter:  Raymond Olavides |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  3.2
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  createsuperuser, | Triage Stage:
  command-line utility   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 This appears to be a usage mistake. You need to use a custom manager with
 your user model that defines
 
[https://docs.djangoproject.com/en/stable/topics/auth/customizing/#django.contrib.auth.models.CustomUserManager.create_superuser
 create_superuser()] with appropriate parameters (corresponding to your
 `USERNAME_FIELD`.

 For an example of how this works, you can look at Django's
 
[https://github.com/django/django/blob/32b7ffc2bbfd1ae055bdbe287f8598de731adce1/tests/auth_tests/test_management.py#L335
 test] for `createsuperuser` which uses
 
[https://github.com/django/django/blob/32b7ffc2bbfd1ae055bdbe287f8598de731adce1/tests/auth_tests/models/custom_user.py
 a custom user] that defines `REQUIRED_FIELDS`.

-- 
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/067.f4ee9e32bef836134dd5f82eb3beef17%40djangoproject.com.

Re: [Django] #33122: createsuperuser bug

[Django]

#33122: createsuperuser bug
-+-
 Reporter:  Raymond Olavides |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:  createsuperuser, | Triage Stage:
  command-line utility   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Raymond Olavides):

 * cc: Raymond Olavides (added)


-- 
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/067.12ee35d79282bcb9b776d678d664cd39%40djangoproject.com.

Re: [Django] #33122: createsuperuser bug

[Django]

#33122: createsuperuser bug
-+-
 Reporter:  rolavides|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:  createsuperuser, | Triage Stage:
  command-line utility   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by rolavides):

 * Attachment "createsuperuser-username_field.patch" added.

 patch to add the username positional parameter

-- 
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/067.1317e4e8bbb509bc69bd9ef9700391fa%40djangoproject.com.

[Django] #33122: createsuperuser bug

[Django]

#33122: createsuperuser bug
-+-
   Reporter:  rolavides  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component: |Version:  3.2
  contrib.auth   |   Keywords:  createsuperuser,
   Severity:  Normal |  command-line utility
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 Creation of user via Django’s command-line utility fails when using
 USERNAME_FIELD.

 Positional parameter is missing.

-- 
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/052.3b3f8e37419f22f26bc11ecd152abf41%40djangoproject.com.

Re: [Django] #33120: Add OGC-compliant models for GeoDjango running on MySQL 8.0

[Django]

#33120: Add OGC-compliant models for GeoDjango running on MySQL 8.0
+
 Reporter:  Jeff Hitchcock  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  GIS |  Version:  dev
 Severity:  Normal  |   Resolution:
 Keywords:  mysql   | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by Jeff Hitchcock):

 Replying to [comment:1 Mariusz Felisiak]:
 > #27464 is probably a partially duplicate of this ticket. What do you
 think?

 They are definitely related, but that ticket has more to do with setting
 SRID on columns (aka support for `ALTER TABLE _ ADD pt POINT SRID 4326`)
 while this deals with being able to add new SRS entries into the database
 (`MySQLSpatialRefSys` and `add_srs_entry`) and introspection of columns
 that have spatial information (`MySQLGeometryColumns`).

-- 
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/064.212f24868d697f1c152b5ee6c7c590c7%40djangoproject.com.

Re: [Django] #33070: Select2 doesn't load translations with subtags.

[Django]

#33070: Select2 doesn't load translations with subtags.
-+-
 Reporter:  Cleiton de Lima  |Owner:  Cleiton
 |  de Lima
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:  select2  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jacob Walls):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/14871 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.6ab564597e8d3c872f5d80f8c61743a9%40djangoproject.com.

Re: [Django] #31670: Change "whitelist" to "allow list" and "blacklist" to "deny list".

[Django]

#31670: Change "whitelist" to "allow list" and "blacklist" to "deny list".
-+-
 Reporter:  Adam Johnson |Owner:  David
 Type:   |  Smith
  Cleanup/optimization   |   Status:  closed
Component:  Core (Other) |  Version:  dev
 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:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"d25710a625fbb6dbb047c159417f796102fd721a" d25710a6]:
 {{{
 #!CommitTicketReference repository=""
 revision="d25710a625fbb6dbb047c159417f796102fd721a"
 Refs #31670 -- Removed whitelist argument and domain_whitelist attribute
 in EmailValidator per deprecation timeline.
 }}}

-- 
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.e677c8a99ad8111bbd9348e64a3f27f8%40djangoproject.com.

Re: [Django] #31235: assertQuerysetEqual cannot compare querysets directly.

[Django]

#31235: assertQuerysetEqual cannot compare querysets directly.
-+-
 Reporter:  Peter Inglesby   |Owner:  Hasan
 |  Ramezani
 Type:  New feature  |   Status:  closed
Component:  Testing framework|  Version:  dev
 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:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"e2be307b3ab6ebf339b3a765fe64967c9602266f" e2be307]:
 {{{
 #!CommitTicketReference repository=""
 revision="e2be307b3ab6ebf339b3a765fe64967c9602266f"
 Refs #31235 -- Made assertQuerysetEqual() not call repr() on a queryset
 when compared to string values.

 Per deprecation timeline.
 }}}

-- 
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/065.7cd5225e203f95047e8685847b05724b%40djangoproject.com.

Re: [Django] #31180: Deprecate default_app_config.

[Django]

#31180: Deprecate default_app_config.
-+-
 Reporter:  Aymeric Augustin |Owner:  Aymeric
 |  Augustin
 Type:  New feature  |   Status:  closed
Component:  Core (Other) |  Version:  dev
 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:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"75d6c4ae6df93c4c4d8621aced3a180afa18a6cb" 75d6c4ae]:
 {{{
 #!CommitTicketReference repository=""
 revision="75d6c4ae6df93c4c4d8621aced3a180afa18a6cb"
 Refs #31180 -- Removed default_app_config application configuration
 variable per deprecation timeline.
 }}}

-- 
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/067.e0cd5b0bd583714fdd012a06a96ab91c%40djangoproject.com.

Re: [Django] #31395: Make TestCase.setUpTestData enforce in-memory data isolation.

[Django]

#31395: Make TestCase.setUpTestData enforce in-memory data isolation.
-+-
 Reporter:  Simon Charette   |Owner:  Simon
 |  Charette
 Type:  New feature  |   Status:  closed
Component:  Testing framework|  Version:  dev
 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:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"2e10abeb7f375d56dca21b1baed11f98e74ab7f5" 2e10abe]:
 {{{
 #!CommitTicketReference repository=""
 revision="2e10abeb7f375d56dca21b1baed11f98e74ab7f5"
 Refs #31395 -- Removed support for assigning objects which don't support
 deepcopy() in setUpTestData().

 Per deprecation timeline.
 }}}

-- 
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/067.e990e009dc912c0e646c8051e51d7055%40djangoproject.com.

Re: [Django] #32191: Not RFC 6265 compliant cookies in contrib.messages.

[Django]

#32191: Not RFC 6265 compliant cookies in contrib.messages.
-+-
 Reporter:  Nico Giefing |Owner:  Craig
 |  Smith
 Type:  Bug  |   Status:  closed
Component:  contrib.messages |  Version:  3.1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Cookie malformed | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"737fa72ae3de1debe97f0a527eeebda3869aa227" 737fa72]:
 {{{
 #!CommitTicketReference repository=""
 revision="737fa72ae3de1debe97f0a527eeebda3869aa227"
 Refs #32191 -- Removed for the pre-Django 3.2 format of messages in
 CookieStorage.

 Per deprecation timeline.
 }}}

-- 
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/063.1f2dd017c3e57a12d3d34f3a9c461c5d%40djangoproject.com.

Re: [Django] #32193: Deprecate MemcachedCache.

[Django]

#32193: Deprecate MemcachedCache.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 Type:   |  Felisiak
  Cleanup/optimization   |   Status:  closed
Component:  Core (Cache system)  |  Version:  dev
 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:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"05f3a6186efefc9fca2204a745b992501c6fd91f" 05f3a61]:
 {{{
 #!CommitTicketReference repository=""
 revision="05f3a6186efefc9fca2204a745b992501c6fd91f"
 Refs #32193 -- Removed MemcachedCache per deprecation timeline.
 }}}

-- 
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/065.86bb6677afecf6704c1dfa6da1f85a38%40djangoproject.com.

Re: [Django] #31546: Replace Command.requires_system_checks = True by something like Command.required_system_checks = '__all__'

[Django]

#31546: Replace Command.requires_system_checks = True by something like
Command.required_system_checks = '__all__'
-+-
 Reporter:  Hasan Ramezani   |Owner:  Hasan
 Type:   |  Ramezani
  Cleanup/optimization   |   Status:  closed
Component:  Core (Management |  Version:  dev
  commands)  |
 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:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"1cb495074f6d983096a015736fed16176588cd33" 1cb4950]:
 {{{
 #!CommitTicketReference repository=""
 revision="1cb495074f6d983096a015736fed16176588cd33"
 Refs #31546 -- Removed support for boolean values in
 Command.requires_system_checks.

 Per deprecation timeline.
 }}}

-- 
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/067.bc292ff95586b11e4b88778dd1b52c21%40djangoproject.com.

Re: [Django] #33070: Select2 doesn't load translations with subtags.

[Django]

#33070: Select2 doesn't load translations with subtags.
-+-
 Reporter:  Cleiton de Lima  |Owner:  Cleiton
 |  de Lima
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:  select2  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Cleiton de Lima):

 * owner:  sarath ak => Cleiton de Lima
 * 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/071.2787059c6fb073b7de22d12b641a637c%40djangoproject.com.

Re: [Django] #33070: Select2 doesn't load translations with subtags.

[Django]

#33070: Select2 doesn't load translations with subtags.
-+-
 Reporter:  Cleiton de Lima  |Owner:  sarath ak
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:  select2  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Cleiton de Lima):

 Yes, I will.

 Replying to [comment:8 Mariusz Felisiak]:
 > Cleiton, thanks for checking. Would you like to prepare a 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.91e403e36a64305482770cab3fe8af0b%40djangoproject.com.

Re: [Django] #33070: Select2 doesn't load translations with subtags.

[Django]

#33070: Select2 doesn't load translations with subtags.
-+-
 Reporter:  Cleiton de Lima  |Owner:  sarath ak
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:  select2  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 Cleiton, thanks for checking. Would you like to prepare a 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.69cc9edfa813671cc33b5b845528b366%40djangoproject.com.

Re: [Django] #33070: Select2 doesn't load translations with subtags.

[Django]

#33070: Select2 doesn't load translations with subtags.
-+-
 Reporter:  Cleiton de Lima  |Owner:  sarath ak
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:  select2  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Cleiton de Lima):

 * cc: Cleiton de Lima (added)


-- 
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/071.42fa4785d3e02003a731785367badb63%40djangoproject.com.

Re: [Django] #33070: Select2 doesn't load translations with subtags.

[Django]

#33070: Select2 doesn't load translations with subtags.
-+-
 Reporter:  Cleiton de Lima  |Owner:  sarath ak
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:  select2  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Cleiton de Lima):

 It looks good to me too!

 Replying to [comment:5 Mariusz Felisiak]:
 > Replying to [comment:4 Cleiton de Lima]:
 > > Replying to [comment:3 Mariusz Felisiak]:
 > > > `LANGUAGE_CODE` should be lowercased, so `pt-br` instead of `pt-BR`,
 see [https://docs.djangoproject.com/en/3.2/topics/i18n/#definitions
 "Definitions"], [https://docs.djangoproject.com/en/3.2/ref/settings
 /#language-code LANGUAGE_CODE docs], and the list of
 
[https://github.com/django/django/blob/3219dd3388c437b4bd869b76ddd43c9cdad05090/django/conf/global_settings.py#L124
 LANGUAGES].
 > >
 > > The translation of select2 only accepts pt-BR that way.
 > > The file is found but the translation doesn't work. It only works when
 the tag html has
 > > {{{...}}}
 > >
 >
 > Thanks, I didn't notice that `Select2` loads translations based on
 `LANG`. Lowercase when searching for a file will help only for `pt-BR` but
 not for `zh-hans`, `pt-br` etc. We could probably add `lang` to the
 `attrs`, e.g.:
 > {{{
 > diff --git a/django/contrib/admin/widgets.py
 b/django/contrib/admin/widgets.py
 > index aeb74773ac..f1002cac6c 100644
 > --- a/django/contrib/admin/widgets.py
 > +++ b/django/contrib/admin/widgets.py
 > @@ -388,6 +388,7 @@ class AutocompleteMixin:
 >  self.db = using
 >  self.choices = choices
 >  self.attrs = {} if attrs is None else attrs.copy()
 > +self.i18n_name = SELECT2_TRANSLATIONS.get(get_language())
 >
 >  def get_url(self):
 >  return reverse(self.url_name % self.admin_site.name)
 > @@ -413,6 +414,7 @@ class AutocompleteMixin:
 >  'data-theme': 'admin-autocomplete',
 >  'data-allow-clear': json.dumps(not self.is_required),
 >  'data-placeholder': '',  # Allows clearing of the input.
 > +'lang': self.i18n_name,
 >  'class': attrs['class'] + (' ' if attrs['class'] else '') +
 'admin-autocomplete',
 >  })
 >  return attrs
 > @@ -449,8 +451,7 @@ class AutocompleteMixin:
 >  @property
 >  def media(self):
 >  extra = '' if settings.DEBUG else '.min'
 > -i18n_name = SELECT2_TRANSLATIONS.get(get_language())
 > -i18n_file = ('admin/js/vendor/select2/i18n/%s.js' % i18n_name,)
 if i18n_name else ()
 > +i18n_file = ('admin/js/vendor/select2/i18n/%s.js' %
 self.i18n_name,) if self.i18n_name else ()
 >  return forms.Media(
 >  js=(
 >  'admin/js/vendor/jquery/jquery%s.js' % extra,
 > }}}
 > What do you think? It works for me.

-- 
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/071.2b42edbbfbefedbe8161c9acbca309b4%40djangoproject.com.

Re: [Django] #31026: Switch form rendering to template engine

[Django]

#31026: Switch form rendering to template engine
-+-
 Reporter:  Johannes Maron   |Owner:  David
 Type:   |  Smith
  Cleanup/optimization   |   Status:  closed
Component:  Forms|  Version:  dev
 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:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"456466d932830b096d39806e291fe23ec5ed38d5" 456466d]:
 {{{
 #!CommitTicketReference repository=""
 revision="456466d932830b096d39806e291fe23ec5ed38d5"
 Fixed #31026 -- Switched form rendering to template engine.

 Thanks Carlton Gibson, Keryn Knight, Mariusz Felisiak, and Nick Pope
 for reviews.

 Co-authored-by: Johannes Hoppe 
 }}}

-- 
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/067.e9250c74d8ca045293b24c93191d0a53%40djangoproject.com.

Re: [Django] #33083: "Select All" in admin changelist does not work when both action_on_bottom and actions_on_top are True.

[Django]

#33083: "Select All" in admin changelist does not work when both 
action_on_bottom
and actions_on_top are True.
-+-
 Reporter:  Benjamin Locher  |Owner:  Carlton
 |  Gibson
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  3.2
 Severity:  Release blocker  |   Resolution:
 Keywords:  actions_on_bottom,   | Triage Stage:  Accepted
  change_list, admin, actions,   |
  admin_actions, select_across,  |
  ModelAdmin,|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/14870 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.ad886331d314118870413eed1359940c%40djangoproject.com.

Re: [Django] #27624: Optimize ORM by using more immutable data structures

[Django]

#27624: Optimize ORM by using more immutable data structures
-+-
 Reporter:  Adam Johnson |Owner:  Adam
 Type:   |  Johnson
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"5353e7c2505c0d0ab8232ad9c131b3c99c833988" 5353e7c]:
 {{{
 #!CommitTicketReference repository=""
 revision="5353e7c2505c0d0ab8232ad9c131b3c99c833988"
 Refs #27624 -- Optimized Query.clone() for non-combined queries.

 This avoids constructing a generator expression and a new tuple if the
 Query has no combined queries.
 }}}

-- 
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.f1b9e49e8885b274e1211b6f7be0948a%40djangoproject.com.

Re: [Django] #33092: Add note regarding thread-safety when using PyMemcacheCache.

[Django]

#33092: Add note regarding thread-safety when using PyMemcacheCache.
--+
 Reporter:  Martijn van der Blom  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Cache system)   |  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:  0 |UI/UX:  0
--+

Comment (by Martijn van der Blom):

 Hi Nick, did you get a chance to look at this issue again? I'm still in
 the dark as to how to resolve this issue.
 For now this prevents me from using the suggested alternative to
 MemcachedCache and when time comes, it will prevent me (and probably
 others) to update to Django 4.1.
 If you want me to investigate something, please let me know.

-- 
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/069.d148519b6ad429ae2215e6321fb2cab5%40djangoproject.com.

Re: [Django] #33119: Change casing of a model's name referenced by ManyToManyField generates unnecessary migrations.

[Django]

#33119: Change casing of a model's name referenced by ManyToManyField generates
unnecessary migrations.
-+-
 Reporter:  AliGhotbizadeh   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  3.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:
  M2M,RenameModel,deconstruct|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"b8f3a3ad54b05b83774716483afac7d0b9535fb4" b8f3a3a]:
 {{{
 #!CommitTicketReference repository=""
 revision="b8f3a3ad54b05b83774716483afac7d0b9535fb4"
 Refs #33119 -- Added tests for changing model name case referenced by
 ManyToManyField.

 Fixed in aa4acc164d1247c0de515c959f7b09648b57dc42.
 }}}

-- 
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/066.3940f98dfb090a0b5e0fe2dbd9ea3b28%40djangoproject.com.

Re: [Django] #6106: make-messages.py should not touch POT-Creation-Date

[Django]

#6106: make-messages.py should not touch POT-Creation-Date
-+-
 Reporter:  Marc Fargas  |Owner:  Daniyal
 Type:   |  Abbasi
  Cleanup/optimization   |   Status:  assigned
Component:   |  Version:  dev
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Daniyal Abbasi):

 Hey
 Yes I do have the time to work on this. I'm waiting on some guidance on
 how I should be incorporating the tests for the same!

-- 
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/067.3bc8f3edc8e62c5d0815b20d9eb336af%40djangoproject.com.

Re: [Django] #33119: Change casing of a model's name referenced by ManyToManyField generates unnecessary migrations. (was: Change casing of a model's name cause endless creation of migrations)

[Django]

#33119: Change casing of a model's name referenced by ManyToManyField generates
unnecessary migrations.
-+-
 Reporter:  AliGhotbizadeh   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  3.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:
  M2M,RenameModel,deconstruct|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


Comment:

 Thanks for the report, it was fixed in
 aa4acc164d1247c0de515c959f7b09648b57dc42 (Django 4.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/066.a31c80c6cd7804903b321bfb756b632e%40djangoproject.com.

Re: [Django] #31026: Switch form rendering to template engine

[Django]

#31026: Switch form rendering to template engine
-+-
 Reporter:  Johannes Maron   |Owner:  David
 Type:   |  Smith
  Cleanup/optimization   |   Status:  assigned
Component:  Forms|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|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/067.203e1e9ae647a26213ac00126ee1d429%40djangoproject.com.

Re: [Django] #33117: sitemap.xml template used with alternates for multiple languages returns an invalid xml

[Django]

#33117: sitemap.xml template used with alternates for multiple languages 
returns an
invalid xml
--+--
 Reporter:  Viggie|Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.sitemaps  |  Version:  3.2
 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 Mariusz Felisiak):

 * status:  new => closed
 * resolution:   => invalid
 * easy:  1 => 0


Comment:

 Florian, thanks for checking!

-- 
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/070.24cc01612ed19abe04e6571dcdad2372%40djangoproject.com.

Re: [Django] #33117: sitemap.xml template used with alternates for multiple languages returns an invalid xml

[Django]

#33117: sitemap.xml template used with alternates for multiple languages 
returns an
invalid xml
--+--
 Reporter:  Viggie|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.sitemaps  |  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:  1 |UI/UX:  0
--+--

Comment (by Florian Demmer):

 What validator was used to produce this error?

 Not only is the namespace name "http://www.w3.org/1999/xhtml; valid, the
 name "http://www.w3.org/1999/xhtml/; (with trailing slash) would be a
 different namespace.

 As specified in [https://www.w3.org/TR/REC-xml-names/#NSNameComparison 2.3
 Comparing URI References]:

   URI references identifying namespaces are compared when determining
 whether a name belongs to a given namespace, and whether two names belong
 to the same namespace. [Definition: The two URIs are treated as strings,
 and they are identical if and only if the strings are identical, that is,
 if they are the same sequence of characters. ] The comparison is case-
 sensitive, and no %-escaping is done or undone.

 and [https://www.w3.org/TR/REC-xml-names/#ns-decl 3 Declaring Namespaces]:

   The namespace name, to serve its intended purpose, SHOULD have the
 characteristics of uniqueness and persistence. It is not a goal that it be
 directly usable for retrieval of a schema (if any exists).

 The namespace name for XHTML is specified [https://www.w3.org/1999/xhtml/
 here]:

   The namespace name http://www.w3.org/1999/xhtml is intended for use in
 various specifications such as: [...]

 Therefore I conclude, that the validator and the StackOverflow
 recommendations are wrong and nothing should be changed in the
 {{{sitemap.xml}}} template.

-- 
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/070.04497b3cd6f5df6d915d5ae73d04cfb3%40djangoproject.com.

Re: [Django] #32970: Investigate feasibility of improving WhereNode clone performance

[Django]

#32970: Investigate feasibility of improving WhereNode clone performance
-+-
 Reporter:  Keryn Knight |Owner:  Keryn
 Type:   |  Knight
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 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:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"e441847ecae99dd1ccd0d9ce76dbcff51afa863c" e441847e]:
 {{{
 #!CommitTicketReference repository=""
 revision="e441847ecae99dd1ccd0d9ce76dbcff51afa863c"
 Fixed #32970 -- Changed WhereNode.clone() to create a shallow copy of
 children.
 }}}

-- 
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/067.17a1e7d83b7feab0143232a8987d13b5%40djangoproject.com.