Re: [Django] #27704: contrib.postgres.ArrayField with choices should use TypedMultipleChoiceField as its default form field class

[Django]

#27704: contrib.postgres.ArrayField with choices should use
TypedMultipleChoiceField as its default form field class
-+-
 Reporter:  Carl Meyer   |Owner:  Anvesh
 |  Mishra
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  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/01070181adad29d1-0f435129-3534-482e-be52-8ce9bbe0e56f-00%40eu-central-1.amazonses.com.

Re: [Django] #33616: Supporting robust on_commit handlers.

[Django]

#33616: Supporting robust on_commit handlers.
-+-
 Reporter:  Josh Smeaton |Owner:  Abhinav
 |  Yadav
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 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/01070181ada7776f-a72c5a74-78b0-4106-8648-6a6a1f0d49eb-00%40eu-central-1.amazonses.com.

Re: [Django] #28785: Tracking migrations

[Django]

#28785: Tracking migrations
---+-
 Reporter:  Ramez Kabbani  |Owner:  Abhinav Yadav
 Type:  New feature|   Status:  assigned
Component:  Migrations |  Version:  1.11
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by Adam Johnson):

 #26760 added the `--prune` option to `migrate`, to clear up stale entries
 from `django_migrations`. Perhaps we no longer need to add a warning now
 there's this option.

-- 
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/01070181ac4a96dd-879bef12-6cb3-44a6-8e5b-2c04b7770156-00%40eu-central-1.amazonses.com.

Re: [Django] #27704: contrib.postgres.ArrayField with choices should use TypedMultipleChoiceField as its default form field class

[Django]

#27704: contrib.postgres.ArrayField with choices should use
TypedMultipleChoiceField as its default form field class
-+-
 Reporter:  Carl Meyer   |Owner:  Anvesh
 |  Mishra
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  dev
 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
-+-

Comment (by Anvesh Mishra):

 Submitted a [https://github.com/django/django/pull/15805 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/01070181ac090f4a-89ec31f7-862d-4067-b93b-b1e21363bd0f-00%40eu-central-1.amazonses.com.

Re: [Django] #32749: Document default options set by PyMemcacheCache.

[Django]

#32749: Document default options set by PyMemcacheCache.
-+-
 Reporter:  yakirsudry   |Owner:  Pablo
 Type:   |  Montepagano
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  3.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  pymemcache   | Triage Stage:  Ready for
  PyMemcacheCache|  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:"72358f0110f3967d95f077986e70e5c8080e9962" 72358f01]:
 {{{
 #!CommitTicketReference repository=""
 revision="72358f0110f3967d95f077986e70e5c8080e9962"
 [4.1.x] Fixed #32749 -- Doc'd PyMemcacheCache defaults.

 Backport of bb2c5f69f47466fa52f3cf2727d10b3ebd79a4da 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/01070181abe4e889-cf8f2dfc-b894-4610-8eed-dbee7cf82dd6-00%40eu-central-1.amazonses.com.

Re: [Django] #32749: Document default options set by PyMemcacheCache.

[Django]

#32749: Document default options set by PyMemcacheCache.
-+-
 Reporter:  yakirsudry   |Owner:  Pablo
 Type:   |  Montepagano
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  3.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  pymemcache   | Triage Stage:  Ready for
  PyMemcacheCache|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by GitHub ):

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


Comment:

 In [changeset:"bb2c5f69f47466fa52f3cf2727d10b3ebd79a4da" bb2c5f69]:
 {{{
 #!CommitTicketReference repository=""
 revision="bb2c5f69f47466fa52f3cf2727d10b3ebd79a4da"
 Fixed #32749 -- Doc'd PyMemcacheCache defaults.
 }}}

-- 
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/01070181abe3871f-0bc0ab1e-3132-4baa-9c31-d6e72973a32b-00%40eu-central-1.amazonses.com.

Re: [Django] #32749: Document default options set by PyMemcacheCache.

[Django]

#32749: Document default options set by PyMemcacheCache.
-+-
 Reporter:  yakirsudry   |Owner:  Pablo
 Type:   |  Montepagano
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:  pymemcache   | Triage Stage:  Ready for
  PyMemcacheCache|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  1 => 0
 * 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/01070181abddee38-358b44b6-426c-4f43-8e89-23e22caae14e-00%40eu-central-1.amazonses.com.

Re: [Django] #33697: Cleanup duplication of HTTP header parsing in utils.http and multipart parser.

[Django]

#33697: Cleanup duplication of HTTP header parsing in utils.http and multipart
parser.
-+-
 Reporter:  Carlton Gibson   |Owner:  Mehrdad
 Type:   |  Moradizadeh
  Cleanup/optimization   |   Status:  closed
Component:  Utilities|  Version:  4.0
 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 GitHub ):

 In [changeset:"154dd1c0edb25f3ab1e951eef8e0c2a1e6274e87" 154dd1c]:
 {{{
 #!CommitTicketReference repository=""
 revision="154dd1c0edb25f3ab1e951eef8e0c2a1e6274e87"
 Refs #33697 -- Added backward incompatibility note about removing
 multipartparser.parse_header().
 }}}

-- 
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/01070181abd8db34-d4970fb9-01db-4607-b12f-6e70e8b7f153-00%40eu-central-1.amazonses.com.

Re: [Django] #33616: Supporting robust on_commit handlers.

[Django]

#33616: Supporting robust on_commit handlers.
-+-
 Reporter:  Josh Smeaton |Owner:  Abhinav
 |  Yadav
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 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 David Wobrock):

 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0
 * needs_docs:  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/01070181a9e17bd3-4fbdfb48-b903-4f8c-bfe2-ef2d55bc473b-00%40eu-central-1.amazonses.com.

Re: [Django] #33810: Admin "now" time is incorrect

[Django]

#33810: Admin "now" time is incorrect
---+--
 Reporter:  Michael|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  4.0
 Severity:  Normal |   Resolution:  worksforme
 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 Michael):

 Replying to [comment:5 Carlton Gibson]:
 > This looks like a configuration error. As far as I can see everything is
 working as expected.
 >
 > > `You are 7 hours ahead of server time.`
 >
 > The default `TIME_ZONE` is `'America/Chicago'`, which is GMT-5.
 `'Africa/Johannesburg'` is (as you say) GMT+2, so there's your 7. Best
 guess is that your settings aren't applied as you think they are.
 >
 > However, without more detail it's impossible to say if there's a deeper
 error.
 >
 > If you can create a sample project that demonstrates an issue, then we
 can have a look, but short of that, there's nothing we can say.

 Thank for you that extra insight, I will see if I can isolate it and make
 a sample project.
 It appears as though the setting is applied to me:

 {{{
 $ python manage.py shell
 Python 3.9.2 (default, Feb 28 2021, 17:03:44)
 [GCC 10.2.1 20210110] on linux
 Type "help", "copyright", "credits" or "license" for more information.
 (InteractiveConsole)
 >>> from django.conf import settings
 >>> settings.TIME_ZONE
 'Africa/Johannesburg'
 }}}

 I will try think of what else I can do.

-- 
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/01070181a9be3857-5b3439b6-0b75-4390-9a27-73d0b6fb50a1-00%40eu-central-1.amazonses.com.

Re: [Django] #29822: Timezone-aware widget for admin site

[Django]

#29822: Timezone-aware widget for admin site
---+
 Reporter:  Paul Tiplady   |Owner:  Shubh Parmar
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  2.1
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Denny Biasiolli):

 What about using standard input types and use `isoformat()` strings in
 templates?

 - input type="date"
 https://caniuse.com/mdn-html_elements_input_type_date

 - input type="time"
 https://caniuse.com/mdn-html_elements_input_type_time

 - input type="datetime-local"
 https://caniuse.com/mdn-html_elements_input_type_datetime-local

 I can help with that

-- 
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/01070181a9b7b9fb-6f0f9b6c-c9a2-490d-a7ca-6a2cd0e8a189-00%40eu-central-1.amazonses.com.

Re: [Django] #33779: Add an encoder parameter to django.utils.html.json_script().

[Django]

#33779: Add an encoder parameter to django.utils.html.json_script().
-+-
 Reporter:  Claude Paroz |Owner:
 |  Hrushikesh Vaidya
 Type:  New feature  |   Status:  assigned
Component:  Utilities|  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
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"0ee03a439b7016c068ab2e0c477d5c84f750a82c" 0ee03a43]:
 {{{
 #!CommitTicketReference repository=""
 revision="0ee03a439b7016c068ab2e0c477d5c84f750a82c"
 Refs #33779 -- Doc'd django.utils.html.json_script().
 }}}

-- 
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/01070181a9ab259f-1a6272e3-303f-4105-8866-3c0d48143d8d-00%40eu-central-1.amazonses.com.

Re: [Django] #33779: Add an encoder parameter to django.utils.html.json_script().

[Django]

#33779: Add an encoder parameter to django.utils.html.json_script().
-+-
 Reporter:  Claude Paroz |Owner:
 |  Hrushikesh Vaidya
 Type:  New feature  |   Status:  closed
Component:  Utilities|  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:"e40b77365fb030b66c039a263ae9fd262a59e373" e40b7736]:
 {{{
 #!CommitTicketReference repository=""
 revision="e40b77365fb030b66c039a263ae9fd262a59e373"
 [4.1.x] Refs #33779 -- Doc'd django.utils.html.json_script().

 Backport of 0ee03a439b7016c068ab2e0c477d5c84f750a82c 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/01070181a9ab2614-34d7193a-b940-4f44-a28e-1d983a3f1a75-00%40eu-central-1.amazonses.com.

Re: [Django] #33779: Add an encoder parameter to django.utils.html.json_script().

[Django]

#33779: Add an encoder parameter to django.utils.html.json_script().
-+-
 Reporter:  Claude Paroz |Owner:
 |  Hrushikesh Vaidya
 Type:  New feature  |   Status:  closed
Component:  Utilities|  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:"72e41a0df6db23410135364223eeda83ac2a8b27" 72e41a0d]:
 {{{
 #!CommitTicketReference repository=""
 revision="72e41a0df6db23410135364223eeda83ac2a8b27"
 Fixed #33779 -- Allowed customizing encoder class in
 django.utils.html.json_script().
 }}}

-- 
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/01070181a9ab25e3-463cca31-13b3-4de4-8f32-788194d3aa97-00%40eu-central-1.amazonses.com.

Re: [Django] #33779: Add an encoder parameter to django.utils.html.json_script().

[Django]

#33779: Add an encoder parameter to django.utils.html.json_script().
-+-
 Reporter:  Claude Paroz |Owner:
 |  Hrushikesh Vaidya
 Type:  New feature  |   Status:  assigned
Component:  Utilities|  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):

 * needs_docs:  1 => 0
 * needs_tests:  1 => 0
 * 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/01070181a985e92e-060ba820-0281-4f14-83ad-b7f4d76c0626-00%40eu-central-1.amazonses.com.

Re: [Django] #33810: Admin "now" time is incorrect

[Django]

#33810: Admin "now" time is incorrect
---+--
 Reporter:  Michael|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  4.0
 Severity:  Normal |   Resolution:  worksforme
 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 Carlton Gibson):

 * resolution:  needsinfo => worksforme


Comment:

 This looks like a configuration error. As far as I can see everything is
 working as expected.

 > `You are 7 hours ahead of server time.`

 The default `TIME_ZONE` is `'America/Chicago'`, which is GMT-5.
 `'Africa/Johannesburg'` is (as you say) GMT+2, so there's your 7. Best
 guess is that your settings aren't applied as you think they are.

 However, without more detail it's impossible to say if there's a deeper
 error.

 If you can create a sample project that demonstrates an issue, then we can
 have a look, but short of that, there's nothing we can say.

-- 
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/01070181a98214c2-370aede8-c99c-4959-9493-e1f13bcdd40e-00%40eu-central-1.amazonses.com.

Re: [Django] #33810: Admin "now" time is incorrect (was: Admin "now" time very strange)

[Django]

#33810: Admin "now" time is incorrect
---+--
 Reporter:  Michael|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  4.0
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  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/01070181a975fb6c-8a9d6505-99a0-4968-a1e4-ec0915c41c20-00%40eu-central-1.amazonses.com.

Re: [Django] #33810: Admin "now" time very strange

[Django]

#33810: Admin "now" time very strange
---+--
 Reporter:  Michael|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  4.0
 Severity:  Normal |   Resolution:  needsinfo
 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 Michael):

 Replying to [comment:2 Mariusz Felisiak]:
 > The admin's site operates in the server time and it works for me with
 `TIME_ZONE = 'Africa/Johannesburg'`. I don't think you've explained the
 issue in enough detail to confirm a bug in Django. Please reopen the
 ticket if you can debug your issue and provide details about why and where
 Django is at fault. If you're having trouble understanding how Django
 works, see TicketClosingReasons/UseSupportChannels for ways to get help.

 As explained and checked the server time is SAST, and Django settings is
 set to SAST, and so is my computer SAST, but Django Admin is showing a 7hr
 timezone error. I am not asking for help, there is nothing else one can
 change, the admin site is auto generated.

-- 
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/01070181a9756877-7b1309f0-cc52-4d3b-87d2-5a2e795dcc44-00%40eu-central-1.amazonses.com.

Re: [Django] #33697: Cleanup duplication of HTTP header parsing in utils.http and multipart parser.

[Django]

#33697: Cleanup duplication of HTTP header parsing in utils.http and multipart
parser.
-+-
 Reporter:  Carlton Gibson   |Owner:  Mehrdad
 Type:   |  Moradizadeh
  Cleanup/optimization   |   Status:  closed
Component:  Utilities|  Version:  4.0
 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


-- 
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/01070181a96d0adf-38f17a20-aae1-477d-8b36-fb1bf323690e-00%40eu-central-1.amazonses.com.

Re: [Django] #33697: Cleanup duplication of HTTP header parsing in utils.http and multipart parser.

[Django]

#33697: Cleanup duplication of HTTP header parsing in utils.http and multipart
parser.
-+-
 Reporter:  Carlton Gibson   |Owner:  Mehrdad
 Type:   |  Moradizadeh
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  Version:  4.0
 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:"d4d5427571b4bf3a21c902276c2a00215c2a37cc" d4d54275]:
 {{{
 #!CommitTicketReference repository=""
 revision="d4d5427571b4bf3a21c902276c2a00215c2a37cc"
 Refs #33697 -- Used django.utils.http.parse_header_parameters() for
 parsing boundary streams.

 This also removes unused parse_header() and _parse_header_params()
 helpers in django.http.multipartparser.
 }}}

-- 
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/01070181a96cb7b8-9c321338-291e-41d6-a86e-343f3bde9087-00%40eu-central-1.amazonses.com.

Re: [Django] #33807: Suggestion: Admin actions drop-down with opt-groups

[Django]

#33807: Suggestion: Admin actions drop-down with opt-groups
-+-
 Reporter:  Jonas Vacek  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  admin, actions,  | Triage Stage:
  drop-down, optgroup|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Carlton Gibson):

 * status:  new => closed
 * type:  Uncategorized => New feature
 * resolution:   => wontfix


Comment:

 This should already be possible overriding
 `ModelAdmin.get_action_choices()`
 
([https://github.com/django/django/blob/bff5c114be2b7a3fbc735c232abcc6ad4db89a9d/django/contrib/admin/options.py#L1022
 src])

 This returns an iterable to be assigned to the form field's `choices`, so
 grouping them works as expected:

 [[Image(https://code.djangoproject.com/raw-
 attachment/ticket/33807/Screenshot%202022-06-28%20at%2009.52.55.png)]]

 Historically, e.g. #19235, requests have centred around not using a select
 at all, since the number of actions is typically low, so I don't think
 expanding the documentation here is worthwhile.

-- 
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/01070181a96419ed-ac6c39e6-b085-4484-a1a2-d54e132781b5-00%40eu-central-1.amazonses.com.

Re: [Django] #33807: Suggestion: Admin actions drop-down with opt-groups

[Django]

#33807: Suggestion: Admin actions drop-down with opt-groups
-+-
 Reporter:  Jonas Vacek  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  admin, actions,  | Triage Stage:
  drop-down, optgroup|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Carlton Gibson):

 * Attachment "Screenshot 2022-06-28 at 09.52.55.png" added.

 Screenshot of grouped actions.

-- 
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/01070181a9604c65-e8544357-11cd-46f6-bd8b-6ca312aa5ff9-00%40eu-central-1.amazonses.com.

Re: [Django] #33781: Timezone warning visual regression.

[Django]

#33781: Timezone warning visual regression.
--+-
 Reporter:  Mariusz Felisiak  |Owner:  Yahyaali1
 Type:  Bug   |   Status:  assigned
Component:  contrib.admin |  Version:  dev
 Severity:  Release blocker   |   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  1
--+-
Changes (by Yahyaali1):

 * owner:  nobody => Yahyaali1
 * 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/01070181a95416b0-38991297-e207-46a0-8ad7-1c778ab1ac54-00%40eu-central-1.amazonses.com.

Re: [Django] #33781: Timezone warning visual regression.

[Django]

#33781: Timezone warning visual regression.
--+
 Reporter:  Mariusz Felisiak  |Owner:  (none)
 Type:  Bug   |   Status:  new
Component:  contrib.admin |  Version:  dev
 Severity:  Release blocker   |   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  1
--+
Changes (by Zainab Amir):

 * owner:  Zainab Amir => (none)
 * status:  assigned => new


-- 
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/01070181a952eba5-26cfb1e2-20ec-43ab-aef5-ad9a76cf6133-00%40eu-central-1.amazonses.com.

Re: [Django] #33803: Add crossorigin attribute to django admin templates

[Django]

#33803: Add crossorigin attribute to django admin templates
--+--
 Reporter:  fcrozatier|Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.admin |  Version:  4.0
 Severity:  Normal|   Resolution:  invalid
 Keywords:  crossorigin COEP  | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by fcrozatier):

 Replying to [comment:2 Adam Johnson]:
 Thank you.

 > No, the answer here is not to change Django. When setting COEP to
 require-corp, you have two options to allow cross-origin assets to work.
 *Either* you set the `crossorigin` attribute, or the assets are served
 with a CORP header declaring cross-origin loading to be allowed. Thus, you
 should change your static asset hosting to add this CORP header. I blogged
 about these headers here: https://adamj.eu/tech/2021/05/01/how-to-set-
 coep-coop-corp-security-headers-in-django/
 >
 > Also with HTTP 2+ it's more efficient to serve your assets from the same
 domain, as they can be served on a single connection. Most sites should be
 doing this. Whitenoise is a popular solution for doing so with minimal
 configuration: https://whitenoise.evans.io/en/stable/ .

-- 
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/01070181a9475918-b12dd680-ca63-4106-aa53-a437915d1032-00%40eu-central-1.amazonses.com.

Re: [Django] #33697: Cleanup duplication of HTTP header parsing in utils.http and multipart parser.

[Django]

#33697: Cleanup duplication of HTTP header parsing in utils.http and multipart
parser.
-+-
 Reporter:  Carlton Gibson   |Owner:  Mehrdad
 Type:   |  Moradizadeh
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  Version:  4.0
 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):

 * needs_better_patch:  1 => 0
 * 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/01070181a9444bbd-c02d987c-178a-4dff-9526-78382d29748a-00%40eu-central-1.amazonses.com.

Re: [Django] #33738: ASGI http.disconnect not handled on requests with body.

[Django]

#33738: ASGI http.disconnect not handled on requests with body.
+
 Reporter:  Carlton Gibson  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  HTTP handling   |  Version:  4.0
 Severity:  Normal  |   Resolution:
 Keywords:  ASGI| Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by Carlton Gibson):

 Hi Rahul.

 > ... if we perform a loop only while receiving the message and break it
 after X interval of time...

 This won't work I'm afraid. We still need to be able to handle the
 incoming `http.disconnect` at any time.

 It's not 100% straightforward but something **like** Channels'
 `await_many_dispatch()` will be needed. See
 
[https://github.com/django/channels/blob/ae60a7d86f3655a1cc35cd9198e61fe5dcc5d1a1/channels/consumer.py#L56-L62
 the usage here]: it's able to route multiple messages.
 (I don't think the example there is 100% properly handling the disconnect,
 as a kind of interrupt there either, since the dispatch task will only
 process one message at a time, where we're looking to handle a disconnect
 whilst processing a long-running request… 樂)

-- 
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/01070181a9211192-14b4a726-3dc2-4083-9053-527246239424-00%40eu-central-1.amazonses.com.

Re: [Django] #33697: Cleanup duplication of HTTP header parsing in utils.http and multipart parser.

[Django]

#33697: Cleanup duplication of HTTP header parsing in utils.http and multipart
parser.
-+-
 Reporter:  Carlton Gibson   |Owner:  Mehrdad
 Type:   |  Moradizadeh
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"d6e0c7c30c1eb83f49345181dc63723968f297ae" d6e0c7c3]:
 {{{
 #!CommitTicketReference repository=""
 revision="d6e0c7c30c1eb83f49345181dc63723968f297ae"
 Refs #33697 -- Made MediaType use
 django.utils.http.parse_header_parameters().
 }}}

-- 
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/01070181a8f696db-9d43dc60-3a88-4d32-aa8e-461783e05c72-00%40eu-central-1.amazonses.com.