Re: [Django] #35475: In admin sidebar, hide empty app headers

[Django]

#35475: In admin sidebar, hide empty app headers
-+-
 Reporter:  Alex Coates  |Owner:  Alex
 Type:   |  Coates
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  sidebar  | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Alex Coates):

 * has_patch:  0 => 1
 * version:  5.0 => dev

-- 
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/0107018fa3c48794-d516b7ac-305e-49c2-b85b-7e000e2d7676-00%40eu-central-1.amazonses.com.

Re: [Django] #35475: In admin sidebar, hide empty app headers

[Django]

#35475: In admin sidebar, hide empty app headers
-+-
 Reporter:  Alex Coates  |Owner:  Alex
 Type:   |  Coates
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  sidebar  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Description changed by Alex Coates:

Old description:

> In the admin sidebar, when a filter is applied, app headers, that don't
> have any matching models, are still visible.
> In project with a lot of apps, these app titles can consume all vertical
> space, leaving relevant models out of sight,
> or just clutter the sidebar.
> [[Image()]]
> [[Image()]]
> To improve user experience, I suggest that the headers for apps, that
> have no remaining models, should be hidden.

New description:

 In the admin sidebar, when a filter is applied, app headers, that don't
 have any matching models, are still visible.
 In project with a lot of apps, these app titles can consume all vertical
 space, leaving relevant models out of sight,
 or just clutter the sidebar.

 [[Image(all-models.png)]]

 [[Image(empty-app.png)]]

 To improve user experience, I suggest that the headers for apps, that have
 no remaining models, should be hidden:

 [[Image(proper.png)]]

--
-- 
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/0107018fa3821a32-c2ea3291-de07-4a0b-a90d-4b56cbfbf118-00%40eu-central-1.amazonses.com.

Re: [Django] #35475: In admin sidebar, hide empty app headers

[Django]

#35475: In admin sidebar, hide empty app headers
-+-
 Reporter:  Alex Coates  |Owner:  Alex
 Type:   |  Coates
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  sidebar  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Alex Coates):

 * Attachment "all-models.png" 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/0107018fa37fd703-480a3210-3a9b-42cc-a09e-d3ac120918f5-00%40eu-central-1.amazonses.com.

Re: [Django] #35475: In admin sidebar, hide empty app headers

[Django]

#35475: In admin sidebar, hide empty app headers
-+-
 Reporter:  Alex Coates  |Owner:  Alex
 Type:   |  Coates
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  sidebar  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Alex Coates):

 * Attachment "proper.png" 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/0107018fa37fdb9b-bf0dda83-31f9-41b9-b167-91ff5942e567-00%40eu-central-1.amazonses.com.

Re: [Django] #35475: In admin sidebar, hide empty app headers

[Django]

#35475: In admin sidebar, hide empty app headers
-+-
 Reporter:  Alex Coates  |Owner:  Alex
 Type:   |  Coates
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  sidebar  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Alex Coates):

 * Attachment "empty-app.png" 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/0107018fa37fd9b7-139fbfd3-1a8e-49f5-bed8-faa348f9ff78-00%40eu-central-1.amazonses.com.

[Django] #35475: In admin sidebar, hide empty app headers

[Django]

#35475: In admin sidebar, hide empty app headers
-+-
   Reporter:  Alex   |  Owner:  Alex Coates
  Coates |
   Type: | Status:  assigned
  Cleanup/optimization   |
  Component: |Version:  5.0
  contrib.admin  |
   Severity:  Normal |   Keywords:  sidebar
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  1  |
-+-
 In the admin sidebar, when a filter is applied, app headers, that don't
 have any matching models, are still visible.
 In project with a lot of apps, these app titles can consume all vertical
 space, leaving relevant models out of sight,
 or just clutter the sidebar.
 [[Image()]]
 [[Image()]]
 To improve user experience, I suggest that the headers for apps, that have
 no remaining models, should be hidden.
-- 
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/0107018fa37eab9c-33fc46cc-6272-4069-85bd-426a6c2f4280-00%40eu-central-1.amazonses.com.

[Django] #35474: django use oracledb and enable thick mode，but sometimes Aborted

[Django]

#35474: django use oracledb and enable thick mode，but sometimes Aborted
-+-
   Reporter:  HeroZ09|  Owner:  nobody
   Type: | Status:  new
  Uncategorized  |
  Component: |Version:  5.0
  Uncategorized  |   Keywords:  django ，oracledb
   Severity:  Normal |  ，thick mode
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 for more detail：https://github.com/oracle/python-oracledb/discussions/337

 1、django 5.0.X, python 3.11.X ,daphne asgi run service
 DATABASES in setting.py:
 DATABASES = {
 "default": {
 "ENGINE": "django.db.backends.oracle",
 "NAME": XX,
 "USER": XX,
 "PASSWORD": XX,
 "HOST": XX,
 "PORT": XX,
 }
 }

 oracledb.init_oracle_client()

 2、OS : debian linux
 3、oracle: instantclient_21_13
 4、python-oracledb : 2.1.1
 5、log：
 double free or corruption (out)
 Fatal Python error: Aborted

 Current thread 0x7f6470cfd6c0 (most recent call first):
   File "/opt/conda/envs/cn_venv/lib/python3.11/site-
 packages/oracledb/connection.py", line 544 in __init__
   File "/opt/conda/envs/cn_venv/lib/python3.11/site-
 packages/oracledb/connection.py", line 1158 in connect
   File "/opt/conda/envs/cn_venv/lib/python3.11/site-
 packages/django/db/backends/oracle/base.py", line 252 in
 get_new_connection
   File "/opt/conda/envs/cn_venv/lib/python3.11/site-
 packages/django/utils/asyncio.py", line 26 in inner
   File "/opt/conda/envs/cn_venv/lib/python3.11/site-
 packages/django/db/backends/base/base.py", line 256 in connect
   File "/opt/conda/envs/cn_venv/lib/python3.11/site-
 packages/django/utils/asyncio.py", line 26 in inner
   File "/opt/conda/envs/cn_venv/lib/python3.11/site-
 packages/django/db/backends/base/base.py", line 275 in ensure_connection
   File "/opt/conda/envs/cn_venv/lib/python3.11/site-
 packages/django/utils/asyncio.py", line 26 in inner
   File "/opt/conda/envs/cn_venv/lib/python3.11/site-
 packages/django/db/backends/base/base.py", line 292 in _cursor
   File "/opt/conda/envs/cn_venv/lib/python3.11/site-
 packages/django/db/backends/base/base.py", line 316 in cursor
   File "/opt/conda/envs/cn_venv/lib/python3.11/site-
 packages/django/utils/asyncio.py", line 26 in inner

 6、I check the django official with how to config oracle datadb（
 https://docs.djangoproject.com/zh-hans/5.0/ref/databases/#oracle-notes），
 and try to settins DATABASES with OPTIONS（threaded = true），but it looks
 not support ，logs below:

  File "D:\SW\Anaconda\anaconda\envs\cn_env\Lib\site-
 packages\oracledb\connection.py", line 1150, in connect
 f(dsn=dsn, pool=pool, conn_class=conn_class, params=params, **kwargs)
 TypeError: connect() got an unexpected keyword argument 'threaded'
-- 
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/0107018fa33bb912-5e4be959-0345-47be-90ee-413c28693ede-00%40eu-central-1.amazonses.com.

Re: [Django] #35473: Typo in historic security advisory

[Django]

#35473: Typo in historic security advisory
---+
 Reporter:  Darakian   |Owner:  sammy20d
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by Tim Graham):

 * stage:  Unreviewed => Accepted
 * type:  Uncategorized => Bug
 * version:   => dev

-- 
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/0107018fa3180b9f-057d738a-594a-4783-8a9f-f3c06234bc7b-00%40eu-central-1.amazonses.com.

Re: [Django] #35451: Documentation: Gunicorn deployment should probably mention the usage of a proxy

[Django]

#35451: Documentation: Gunicorn deployment should probably mention the usage of 
a
proxy
--+
 Reporter:  Klaas van Schelven|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  5.0
 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
--+
Changes (by eboeh1):

 * owner:  eboeh1 => nobody

-- 
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/0107018fa2540d11-5ca36826-8c15-45e4-9337-51262362b659-00%40eu-central-1.amazonses.com.

Re: [Django] #35451: Documentation: Gunicorn deployment should probably mention the usage of a proxy

[Django]

#35451: Documentation: Gunicorn deployment should probably mention the usage of 
a
proxy
-+-
 Reporter:  Klaas van Schelven   |Owner:  Edward
 Type:   |  Boehling
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  5.0
 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
-+-
Changes (by Edward Boehling):

 * owner:  nobody => Edward Boehling
 * 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/0107018fa2463bf7-4e3aa539-3c78-4c1a-b998-19059785929e-00%40eu-central-1.amazonses.com.

Re: [Django] #35472: Image files aren't cleaned up after running tests

[Django]

#35472: Image files aren't cleaned up after running tests
-+-
 Reporter:  bcail|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  File |  Version:  5.1
  uploads/storage|
 Severity:  Release blocker  |   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 Natalia Bidart):

 * 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/0107018fa1d09526-2696eef3-01ab-4724-b832-fa964dd3f3e3-00%40eu-central-1.amazonses.com.

Re: [Django] #35472: Image files aren't cleaned up after running tests

[Django]

#35472: Image files aren't cleaned up after running tests
--+
 Reporter:  bcail |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  File uploads/storage  |  Version:  5.1
 Severity:  Release blocker   |   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Comment (by Natalia <124304+nessita@…>):

 In [changeset:"501e32a7f5012aa014931a39699391d91ca0a9be" 501e32a]:
 {{{#!CommitTicketReference repository=""
 revision="501e32a7f5012aa014931a39699391d91ca0a9be"
 [5.1.x] Fixed #35472 -- Used temporary directory in
 test_imagefield.NoReadTests.

 Backport of 7e39ae5c8cf4c6601a4f47b72914349481c5331b 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/0107018fa1d03494-33d1bd56-caba-471b-9c85-1a0e873972d6-00%40eu-central-1.amazonses.com.

Re: [Django] #28800: Add a management command to list URL patterns

[Django]

#28800: Add a management command to list URL patterns
-+-
 Reporter:  Martín Peveri|Owner:  Keanya
 |  Phelps
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  1.11
  commands)  |
 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 Alexandr Artemyev):

 Replying to [comment:11 Keanya Phelps]:
 Not sure if this change was made intentionally or by mistake.

 Replying to [comment:10 Xavier Tilley]:
 > I have the feature finished I just haven't had time to finished up the
 tests and documentation. Hopefully my day job will slow down a bit and I
 can get a PR in next month.

 Do you still plan to make these changes?

 Replying to [comment:8 Adam Johnson]:
 Could we push this feature?
-- 
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/0107018fa1d02919-1a456c42-3866-472c-9c87-a74e97bc49e9-00%40eu-central-1.amazonses.com.

Re: [Django] #35472: Image files aren't cleaned up after running tests

[Django]

#35472: Image files aren't cleaned up after running tests
--+
 Reporter:  bcail |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  File uploads/storage  |  Version:  5.1
 Severity:  Release blocker   |   Resolution:  fixed
 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 nessita <124304+nessita@…>):

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

Comment:

 In [changeset:"7e39ae5c8cf4c6601a4f47b72914349481c5331b" 7e39ae5]:
 {{{#!CommitTicketReference repository=""
 revision="7e39ae5c8cf4c6601a4f47b72914349481c5331b"
 Fixed #35472 -- Used temporary directory in test_imagefield.NoReadTests.
 }}}
-- 
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/0107018fa1cefd98-af7eba3e-9097-4389-b181-075533b575e4-00%40eu-central-1.amazonses.com.

Re: [Django] #35472: Image files aren't cleaned up after running tests

[Django]

#35472: Image files aren't cleaned up after running tests
--+
 Reporter:  bcail |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  File uploads/storage  |  Version:  5.1
 Severity:  Release blocker   |   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 Natalia Bidart):

 * severity:  Normal => Release blocker

Comment:

 Marking as release blocker so we backport to `stable/5.1.x`.
-- 
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/0107018fa1b86559-4a408ad7-ad13-492f-89f0-3780681dfeb1-00%40eu-central-1.amazonses.com.

Re: [Django] #35167: JSONField get_db_prep_value being called with `Cast` types

[Django]

#35167: JSONField get_db_prep_value being called with `Cast` types
-+-
 Reporter:  Samantha Hughes  |Owner:
 |  HeejunShin
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  JSONField| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by HeejunShin):

 i have a question.
 maybe The bug reproduction seems to be incorrect.

 i tested using 2 ways.

 {{{
 tests[1].json = {"test": Cast('good', output_field=CharField())}
 Test.objects.bulk_update(tests_will_be_updated, fields=["json"])
 }}}

 {{{
 tests[1].json = Cast("good", output_field=CharField())
 Test.objects.bulk_update(tests_will_be_updated, fields=["json"])
 }}}

 first one, i got  "raise TypeError(f'Object of type {o.__class__.__name__}
 'TypeError: Object of type Cast is not JSON serializable" error.
 but value argument type in get_db_prep_value is dict.

 second one, i could not get error.
 value argument type in get_db_prep_value is . (CASE WHEN  THEN Cast(Col(polls_test,
 polls.Test.json)), ELSE Value(None)).

 i thought first one is type dict, so this is wrong.
 is second one wrong way that reproduce bug 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018fa17fdf9a-499173ea-9027-44ff-b6a1-0a6dd6ac09d1-00%40eu-central-1.amazonses.com.

Re: [Django] #35473: Typo in historic security advisory

[Django]

#35473: Typo in historic security advisory
---+--
 Reporter:  Darakian   |Owner:  sammy20d
 Type:  Uncategorized  |   Status:  assigned
Component:  Documentation  |  Version:
 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
---+--
Changes (by sammy20d):

 * owner:  nobody => sammy20d
 * 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/0107018fa16440f5-acbb09a0-048e-4871-bc4d-e9341d6c9d9b-00%40eu-central-1.amazonses.com.

[Django] #35473: Typo in historic security advisory

[Django]

#35473: Typo in historic security advisory
-+
   Reporter:  Darakian   |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Documentation  |Version:
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+
 Hey all,

 Wanted to raise a very minor issue to you all. I work on the advisory
 database for github and had a user come and suggest an improvement on an
 old CVE from 2009 (CVE-2009-3965)
 See: https://github.com/github/advisory-database/pull/4451

 The CVE itself seemed entirely unrelated to me, but then a reference to
 some django docs was brought up
 
https://docs.djangoproject.com/en/3.2/releases/security/#october-9-2009-cve-2009-3965
 which references the same CVE id.

 I ended up doing some digging and I think what happened is that someone
 typoed on that doc and it should have been 3695 rather than 3965
 See: https://nvd.nist.gov/vuln/detail/CVE-2009-3695
 vs https://nvd.nist.gov/vuln/detail/CVE-2009-3965

 Anyway, very minor issue but figured it would be good to report it all the
 same so that it can get updated :)
-- 
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/0107018fa162d30a-8763f8f4-e4d2-46f8-a1ae-0ec8e6c54931-00%40eu-central-1.amazonses.com.

Re: [Django] #35472: Image files aren't cleaned up after running tests

[Django]

#35472: Image files aren't cleaned up after running tests
--+
 Reporter:  bcail |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  File uploads/storage  |  Version:  5.1
 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 Sarah Boyce):

 * component:  Uncategorized => File uploads/storage
 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted
 * version:  dev => 5.1

Comment:

 Thank you bcail!
 Yes, this was introduced in 9c5fe93349bd4339c41d057b87046e5d28be6f77
 (#35139), I have raised a patch. I think we should backport this into 5.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/0107018fa15e7380-cdd3e314-ddf3-4c3e-b436-a50f4002d5f8-00%40eu-central-1.amazonses.com.

Re: [Django] #21602: FileSystemStorage._save() Should Save to a Temporary Filename and Rename to Attempt to be Atomic

[Django]

#21602: FileSystemStorage._save() Should Save to a Temporary Filename and 
Rename to
Attempt to be Atomic
--+
 Reporter:  Kevin Stone   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  File uploads/storage  |  Version:  dev
 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
--+
Changes (by bcail):

 * cc: bcail (added)

Comment:

 This should be easier to implement once the
 
[https://github.com/django/django/blob/main/django/core/files/storage/filesystem.py#L122
 OS_OPEN_FLAGS] are removed (they're currently deprecated).
-- 
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/0107018fa1133cb6-c3f44a31-b770-44db-b552-07f310275ddd-00%40eu-central-1.amazonses.com.

Re: [Django] #35469: Squashing migrations from unique=True to unique=False to UniqueConstraint produces irreversible migration on Postgres

[Django]

#35469: Squashing migrations from unique=True to unique=False to 
UniqueConstraint
produces irreversible migration on Postgres
-+
 Reporter:  Jacob Walls  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  4.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 Jacob Walls):

 Sorry, still forming first impressions here, but just piping up to clarify
 that my last comment mostly barks up the wrong tree: the field values for
 `db_index` and whatnot look fine. And on a closer read of #28646, it
 strikes me as mostly focused on SlugField, which *doesn't* have the
 problem presented here. So I think having separate tickets makes sense.
-- 
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/0107018fa0933187-8d92ae29-ab14-45fa-9a24-19e3b45ff0d2-00%40eu-central-1.amazonses.com.

[Django] #35472: Image files aren't cleaned up after running tests

[Django]

#35472: Image files aren't cleaned up after running tests
+
   Reporter:  bcail |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Uncategorized |Version:  dev
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 After each run of the django test suite, I'm seeing two image files
 ("mug*") left on the filesystem. It looks like the issue is from this
 commit: 9c5fe93349bd4339c41d057b87046e5d28be6f77.
-- 
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/0107018fa086c268-9e8b95fa-39dd-4744-b6ee-25f525df7eab-00%40eu-central-1.amazonses.com.

Re: [Django] #35328: Improve CSRF Origin checking messaging

[Django]

#35328: Improve CSRF Origin checking messaging
-+-
 Reporter:  Ryan Hiebert |Owner:  Ryan
 Type:   |  Hiebert
  Cleanup/optimization   |   Status:  assigned
Component:  CSRF |  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 Ryan Hiebert):

 * 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/0107018fa034fa55-db2d8036-8d1c-499f-a2b4-6dd77a2c75de-00%40eu-central-1.amazonses.com.

Re: [Django] #35469: Squashing migrations from unique=True to unique=False to UniqueConstraint produces irreversible migration on Postgres

[Django]

#35469: Squashing migrations from unique=True to unique=False to 
UniqueConstraint
produces irreversible migration on Postgres
-+
 Reporter:  Jacob Walls  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  4.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 Jacob Walls):

 Thanks for the link to #28646. It's related, but most of the discussion
 there centers around the "boolean logic" cited in that ticket's OP. I
 tried the various patches, and they don't fix my report because they just
 shuffle the logic fathoming the booleans `db_index` and `unique` on
 `old_field` and `new_fields`, whereas the problem here seems to be that
 one of those values is wrong.

 #26805 inspired me to check SlugField. I can't reproduce with SlugField,
 leading me to wonder if it's something to do with `URLField`'s different
 implementation of `deconstruct()`?

 When using SlugField, and breaking on the comment "Added an index? ..." in
 db/backends/postgresql/schema.py, I get:
 {{{
 (Pdb) new_field.db_index
 True
 }}}
 versus with URLField:
 {{{
 (Pdb) new_field.db_index
 False
 }}}
-- 
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/0107018fa02a4273-b1425df9-b7c9-42ea-983a-ff27174b6c5a-00%40eu-central-1.amazonses.com.

Re: [Django] #35443: Fix negative numbers for ordinals

[Django]

#35443: Fix negative numbers for ordinals
-+-
 Reporter:  Siburg   |Owner:
 |  S-Tornqvist, Crustum7
 Type:  Bug  |   Status:  assigned
Component:  contrib.humanize |  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  humanize ordinal | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sarah Boyce):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018f9fcc82c2-5591e8d2-c5dd-4987-b402-4ba0bbf9c8af-00%40eu-central-1.amazonses.com.

Re: [Django] #35328: Improve CSRF Origin checking messaging

[Django]

#35328: Improve CSRF Origin checking messaging
-+-
 Reporter:  Ryan Hiebert |Owner:  Ryan
 Type:   |  Hiebert
  Cleanup/optimization   |   Status:  assigned
Component:  CSRF |  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
-+-
Changes (by Sarah Boyce):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018f9fc410c4-b11b858c-b6f6-45aa-9889-bab5882c6116-00%40eu-central-1.amazonses.com.

Re: [Django] #35469: Squashing migrations from unique=True to unique=False to UniqueConstraint produces irreversible migration on Postgres (was: Squashing migrations from unique=True to unique=False t

[Django]

#35469: Squashing migrations from unique=True to unique=False to 
UniqueConstraint
produces irreversible migration on Postgres
-+
 Reporter:  Jacob Walls  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  4.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
-+
Changes (by Sarah Boyce):

 * stage:  Unreviewed => Accepted
 * summary:
 Squashing migrations from unique=True to unique=False to
 UniqueConstraint produces irreversible migration
 =>
 Squashing migrations from unique=True to unique=False to
 UniqueConstraint produces irreversible migration on Postgres

Comment:

 Replicated on Postgres, accepting 
-- 
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/0107018f9fb2c504-1184dd02-60c2-4610-a3e1-a99a4e73fe82-00%40eu-central-1.amazonses.com.

Re: [Django] #35467: Prefer urlsplit() over urlparse()

[Django]

#35467: Prefer urlsplit() over urlparse()
-+-
 Reporter:  Adam Johnson |Owner:  Jake
 Type:   |  Howard
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  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 Jake Howard):

 * has_patch:  0 => 1

Comment:

 [https://github.com/django/django/pull18187 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/0107018f9f816580-8394f786-626d-4a89-81fb-457b79cb6816-00%40eu-central-1.amazonses.com.

Re: [Django] #35469: Squashing migrations from unique=True to unique=False to UniqueConstraint produces irreversible migration

[Django]

#35469: Squashing migrations from unique=True to unique=False to 
UniqueConstraint
produces irreversible migration
-+--
 Reporter:  Jacob Walls  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Comment (by Sarah Boyce):

 Hi Jacob, thank you for this. I tried to replicate on main with SQLite and
 couldn't, so this might be postgres specific (I will try out again later).
 I was wondering if you have seen #28646 and whether you think this is
 related or this issue would be resolved with that ticket?
-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018f9f7cafd2-8310c1fa-e315-4843-b2b8-00e3a7182ba8-00%40eu-central-1.amazonses.com.

Re: [Django] #35393: InlineAdmin's are not possible with an editable UUIDField as primary key.

[Django]

#35393: InlineAdmin's are not possible with an editable UUIDField as primary 
key.
-+-
 Reporter:  Willem Van Onsem |Owner:  Willem
 |  Van Onsem
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  5.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:  0|UI/UX:  0
-+-
Changes (by Sarah Boyce <42296566+sarahboyce@…>):

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

Comment:

 In [changeset:"2995aeab56d661663e2851b29bba1fc20c2541f0" 2995aeab]:
 {{{#!CommitTicketReference repository=""
 revision="2995aeab56d661663e2851b29bba1fc20c2541f0"
 Fixed #35393 -- Added excluded pk as a hidden field to the inline admin.
 }}}
-- 
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/0107018f9f6d442d-dee10563-a82a-41bf-bc20-53c6362b3305-00%40eu-central-1.amazonses.com.

Re: [Django] #35393: InlineAdmin's are not possible with an editable UUIDField as primary key.

[Django]

#35393: InlineAdmin's are not possible with an editable UUIDField as primary 
key.
-+-
 Reporter:  Willem Van Onsem |Owner:  Willem
 |  Van Onsem
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  5.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:  0|UI/UX:  0
-+-
Changes (by Sarah Boyce):

 * 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/0107018f9f6c0483-377bcbad-0d96-4b2a-8c06-f4cf3403a1e4-00%40eu-central-1.amazonses.com.

Re: [Django] #35447: Request attribute upload handlers is immutable when method is POST

[Django]

#35447: Request attribute upload handlers is immutable when method is POST
---+--
 Reporter:  matsony_15 |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Generic views  |  Version:  dev
 Severity:  Normal |   Resolution:  needsinfo
 Keywords:  UploadHandler  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Comment (by matsony_15):

 Also checked that issue is present in Django 5.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/0107018f9f50aafc-136aef1f-4ac6-4f7c-af81-2fc864dcda30-00%40eu-central-1.amazonses.com.

Re: [Django] #35458: Docs: clarify need for ALLOWED_HOSTS

[Django]

#35458: Docs: clarify need for ALLOWED_HOSTS
+--
 Reporter:  Klaas van Schelven  |Owner:  nobody
 Type:  Uncategorized   |   Status:  closed
Component:  Documentation   |  Version:  5.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 Klaas van Schelven):

 Those notes give slightly more context, but not too much more. i.e. "it
 has been reported to us that even with the recommended web server
 configurations there are still techniques available for tricking many
 common web servers into supplying the application with an incorrect and
 possibly malicious Host header." still leaves me to wonder what these
 techniques would be and how one could defend against them at the level of
 the webserver (Apache, Nginx) rather than Django.

 > I think you're suggesting that Django should recommend or imply having
 `ALLOWED_HOSTS` as `["*"]` is safe.

 This was indeed one of the options in my original post. However, having
 since tried my hand at properly configuring the front-facing part, I have
 come to the conclusion that defense in depth is indeed a good
 recommendation. Still, I think the wording of the docs could be more
 clear, but I have to admit I don't have a good alternative myself.

 Closing this issue for now is good 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/0107018f9f4156c4-29aa2536-c868-4e53-b972-1124761f87dc-00%40eu-central-1.amazonses.com.

Re: [Django] #35471: Make the admin search filter optional in nav sidebar?

[Django]

#35471: Make the admin search filter optional in nav sidebar?
---+--
 Reporter:  Ryu|Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  5.0
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+--
Changes (by Sarah Boyce):

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

Comment:

 You can propose this on the

 If you wish to do this on your project you could overwrite the template
 
[https://github.com/django/django/blob/main/django/contrib/admin/templates/admin/nav_sidebar.html
 admin/nav_sidebar.html] to be empty, see
 [https://docs.djangoproject.com/en/5.0/intro/tutorial07/#customize-the-
 admin-index-page customizing the admin index page].

 Otherwise, to way to request new features is to first propose and discuss
 the idea with the community and gain consensus. To do that, please
 consider starting a new conversation on the
 [https://forum.djangoproject.com/c/internals/5 Django Forum], where you'll
 reach a wider audience and likely get extra feedback.

 I'll close the ticket for now, but if there is a community agreement for
 the feature request, you are welcome to come back to the ticket and point
 to the forum topic, so we can then re-open it. For more details, please
 see [https://docs.djangoproject.com/en/stable/internals/contributing/bugs-
 and-features/#requesting-features the documented guidelines for requesting
 features].
-- 
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/0107018f9f19c06b-b2b2dd9c-0059-4c0d-8124-23200304d810-00%40eu-central-1.amazonses.com.

Re: [Django] #31405: LoginRequiredAuthenticationMiddleware force all views to require authentication by default.

[Django]

#31405: LoginRequiredAuthenticationMiddleware force all views to require
authentication by default.
-+-
 Reporter:  Mehmet İnce  |Owner:  Hisham
 |  Mahmood
 Type:  New feature  |   Status:  closed
Component:  contrib.auth |  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 Sarah Boyce <42296566+sarahboyce@…>):

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

Comment:

 In [changeset:"c7fc9f20b49b5889a9a8f47de45165ac443c1a21" c7fc9f20]:
 {{{#!CommitTicketReference repository=""
 revision="c7fc9f20b49b5889a9a8f47de45165ac443c1a21"
 Fixed #31405 -- Added LoginRequiredMiddleware.

 Co-authored-by: Adam Johnson 
 Co-authored-by: Mehmet İnce 
 Co-authored-by: Sarah Boyce <42296566+sarahbo...@users.noreply.github.com>
 }}}
-- 
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/0107018f9f119c2d-e2a37c88-1162-4416-ae30-a3e19d9b6e3b-00%40eu-central-1.amazonses.com.

Re: [Django] #35470: Separate i18n and l10n globalization settings into two sublists.

[Django]

#35470: Separate i18n  and  l10n globalization settings into two sublists.
-+-
 Reporter:  Lufafa Joshua|Owner:  Lufafa
 Type:   |  Joshua
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  5.0
 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
-+-
Changes (by Sarah Boyce):

 * component:  Uncategorized => Documentation
 * stage:  Unreviewed => Accepted

Comment:

 Thank you! I agree that, separating
 [https://docs.djangoproject.com/en/5.0/ref/settings/#globalization-i18n-
 l10n Globalization (i18n/l10n) settings] between those that may overriding
 by locale formats and those that don't, is a nice clarification
-- 
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/0107018f9f0df4d5-5539a368-c1ae-4ed5-8537-a05d9c6aa601-00%40eu-central-1.amazonses.com.

Re: [Django] #35470: Separate i18n and l10n globalization settings into two sublists.

[Django]

#35470: Separate i18n  and  l10n globalization settings into two sublists.
-+-
 Reporter:  Lufafa Joshua|Owner:  Lufafa
 Type:   |  Joshua
  Cleanup/optimization   |   Status:  assigned
Component:  Uncategorized|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Lufafa Joshua):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018f9f094a0b-76912a3c-d217-488a-aa5c-ec7271f6fb50-00%40eu-central-1.amazonses.com.

Re: [Django] #35458: Docs: clarify need for ALLOWED_HOSTS

[Django]

#35458: Docs: clarify need for ALLOWED_HOSTS
+--
 Reporter:  Klaas van Schelven  |Owner:  nobody
 Type:  Uncategorized   |   Status:  closed
Component:  Documentation   |  Version:  5.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
+--
Changes (by Sarah Boyce):

 * component:  Uncategorized => Documentation
 * resolution:   => needsinfo
 * status:  new => closed

Comment:

 I believe the [https://docs.djangoproject.com/en/5.0/releases/1.4.4/#host-
 header-poisoning Django 1.4.4 release notes] gives more context.

 I think you're suggesting that Django should recommend or imply having
 `ALLOWED_HOSTS` as `["*"]` is safe.
 You should discuss this on the
 [https://forum.djangoproject.com/c/internals/5 Django forum] and state why
 this should be updated/allowed. As this relates to security, we need very
 strong consensus and evidence that this is safe before we can make an
 update. The security team may also want to review such an update. During
 this discussion you might conclude to add some doc clarifications.

 I am closing this request for now but if after a discussion you have a
 concrete proposal, please reopen the ticket for consideration.
-- 
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/0107018f9f086387-b9b6053b-cb7d-4f93-af62-5c2a1acb171b-00%40eu-central-1.amazonses.com.