date:20231019

Re: [Django] #34911: Admindocs index skips from h1 to h3

2023-10-19 Thread Django

#34911: Admindocs index skips from h1 to h3
-+-
 Reporter:  Thibaud Colas|Owner:
 |  laserhyena
 Type:  Bug  |   Status:  closed
Component:  contrib.admindocs|  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  accessibility,   | Triage Stage:  Ready for
  screen reader, headings|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"bba963df50f73f14f7e48f285f9bc920e48093cb" bba963d]:
 {{{
 #!CommitTicketReference repository=""
 revision="bba963df50f73f14f7e48f285f9bc920e48093cb"
 [5.0.x] Fixed #34911 -- Corrected HTML heading levels on admindocs' main
 page.

 Backport of 21382e2743d06efbf5623e7c9b6dccf2a325669b 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/0107018b4b508f31-23c94a06-8bb7-4aee-8d34-4122ee4e2503-00%40eu-central-1.amazonses.com.

Re: [Django] #34911: Admindocs index skips from h1 to h3

2023-10-19 Thread Django

#34911: Admindocs index skips from h1 to h3
-+-
 Reporter:  Thibaud Colas|Owner:
 |  laserhyena
 Type:  Bug  |   Status:  closed
Component:  contrib.admindocs|  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  accessibility,   | Triage Stage:  Ready for
  screen reader, headings|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"21382e2743d06efbf5623e7c9b6dccf2a325669b" 21382e27]:
 {{{
 #!CommitTicketReference repository=""
 revision="21382e2743d06efbf5623e7c9b6dccf2a325669b"
 Fixed #34911 -- Corrected HTML heading levels on admindocs' main page.
 }}}

-- 
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/0107018b4b503451-f712af52-358c-42b7-8066-7b196d719036-00%40eu-central-1.amazonses.com.

Re: [Django] #34903: Parallel test runner failure on Windows

2023-10-19 Thread Django

#34903: Parallel test runner failure on Windows
-+-
 Reporter:  David Smith  |Owner:  David
 |  Sanders
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  dev
 Severity:  Release blocker  |   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 Mariusz Felisiak):

 * 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/0107018b4b3bf870-85c7cc1c-030e-4a30-a0c0-24603337870e-00%40eu-central-1.amazonses.com.

Re: [Django] #34911: Admindocs index skips from h1 to h3

2023-10-19 Thread Django

#34911: Admindocs index skips from h1 to h3
-+-
 Reporter:  Thibaud Colas|Owner:
 |  laserhyena
 Type:  Bug  |   Status:  assigned
Component:  contrib.admindocs|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Ready for
  screen reader, headings|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Mariusz Felisiak):

 * has_patch:  0 => 1
 * 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/0107018b4b340eee-70b16ed8-afb8-42ba-96c8-68df1bf508e3-00%40eu-central-1.amazonses.com.

Re: [Django] #15578: loaddata and processing order of fixtures

2023-10-19 Thread Django

#15578: loaddata and processing order of fixtures
-+-
 Reporter:  Luc Saffre   |Owner:  Leo
 Type:   |  Suarez
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.2
 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 Mariusz Felisiak):

 [https://code.djangoproject.com/ticket/15578 New 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/0107018b4b24f422-1f4b3b80-d86e-491f-a9ba-fac4c4d82b76-00%40eu-central-1.amazonses.com.

Re: [Django] #34914: Postgres connection is not restarted after it's dropped by the server, even if we use CONN_HEALTH_CHECKS=True

2023-10-19 Thread Django

#34914: Postgres connection is not restarted after it's dropped by the server, 
even
if we use CONN_HEALTH_CHECKS=True
-+-
 Reporter:  Vitor Menegat|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 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:   => duplicate


Comment:

 Agreed, this can be closed as a duplicate of #14845 (just like #32589).

-- 
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/0107018b4b1c01c5-d19d80c5-c075-4058-a888-2088c8bf00a3-00%40eu-central-1.amazonses.com.

Re: [Django] #34913: Django Admin high contrast mode no clear session (was: [Accessibility] Django Admin high contrast mode no clear session)

2023-10-19 Thread Django

#34913: Django Admin high contrast mode no clear session
-+-
 Reporter:  Cheuk Ting Ho|Owner:  Cheuk
 |  Ting Ho
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  forced-colors  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Mariusz Felisiak):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/17387/ 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/0107018b4b1912fb-e4d66e1a-cc6a-486d-8fd6-d64b81942ccb-00%40eu-central-1.amazonses.com.

Re: [Django] #34914: Postgres connection is not restarted after it's dropped by the server, even if we use CONN_HEALTH_CHECKS=True

2023-10-19 Thread Django

#34914: Postgres connection is not restarted after it's dropped by the server, 
even
if we use CONN_HEALTH_CHECKS=True
-+-
 Reporter:  Vitor Menegat|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 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 Simon Charette):

 I think this is closely related to #32589 and #14845.

 Django being mainly a web framework most of its connection management is
 based around HTTP request lifecycle handling. For example, Django
 automatically checks whether database connections should be closed
 
[https://github.com/django/django/blob/89d2ae257bfdbe6f32c4671d97bf572623992ace/django/db/__init__.py#L53-L61
 when starting and finishing HTTP requests].

 The way management commands were designed though didn't account for
 lifecycle events for the framework to hook into and manage connections
 appropriately. In other words, `BaseCommand.handle` is a blackbox to the
 framework and it cannot safely determine that a unit of work is completed
 and that is is safe to close a connection.

 In the case of long-running / demonized commands that are meant to run for
 longer than `CONN_MAX_AGE` (or the TTL of the underlying server
 connection) it is the responsibility of the user to call
 `close_old_connections`. This is something that is unfortunately not
 documented but given how common this use case and the lack of progress on
 #14845 in the past years I think we should consider a documentation
 admonition that focuses solely on the long-runner command use case if that
 means documenting this pattern more broadly.

 If you feel so inclined to get this documented it appears to be a good
 opportunity to resolve a 10 years old issue ;)

 TL;DR the following should address your issue but it's unfortunately not
 documented

 {{{#!python
 import logging
 import time

 from django.core.management import BaseCommand
 from django.db import close_old_connections, connection


 logger = logging.getLogger(__name__)


 class Command(BaseCommand):
 def handle(self, *args, **kwargs):
 while True:
 close_old_connections()  # <- this ensures
 DATABASES["default"]["CONN_*"] settings are honoured.
 time.sleep(1)
 try:
 logger.info(f"health_check_enabled:
 {connection.health_check_enabled}")
 logger.info(f"health_check_done:
 {connection.health_check_done}")
 logger.info(f"errors_occurred:
 {connection.errors_occurred}")
 with connection.cursor() as cursor:
 cursor.execute("SELECT 1")
 logger.info("query executed")
 except Exception as e:
 logger.exception(e)
 }}}

-- 
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/0107018b4a8343fe-6d5998cb-7a85-4223-b8ec-aec6908502cd-00%40eu-central-1.amazonses.com.

Re: [Django] #34881: migrate crashes when renaming model referenced twice by ManyToManyField.through model on SQLite.

2023-10-19 Thread Django

#34881: migrate crashes when renaming model referenced twice by
ManyToManyField.through model on SQLite.
+
Reporter: dennisvang |Owner: Jase Hackman
Type: Bug | Status: assigned
Component: Migrations | Version: dev
Severity: Normal | Resolution:
Keywords: sqlite | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 |UI/UX: 0
+

Comment (by Jase Hackman):

I spent some time digging into this today.

To account for the unique nature of sqlite a `_remake_table()`

[https://github.com/jasehackman/django/blob/2abf417c815c20f41c0868d6f66520b32347106e/django/db/backends/sqlite3/schema.py#L75
link] method was added to recreate the table under the various conditions
under which it is required for table schema changes
[https://www.sqlite.org/lang_altertable.html#caution sqlite docs].

The problem is that the code is not aware of previous calls of
`_remake_table()` or if multiple will be required for a single table.

To fix this I am going to try to aggregate all of the alter statements
into a single call, resulting in a single create statement.

To accomplish this I added an `alter_fields()` method to
`BaseDatabaseSchemaEditor` that is passed a list of tuples to of the
fields to be updated. It then loops over those fields to call the original
`alter_field()` method. So far the new method is only being called in
`RenameModel`.

[https://github.com/django/django/commit/e382a37f1b90bfdac7b22ed1a4e800b7a37cd28a
See commit with current progress]

I next plan override this new method in the sqlite `DatabaseSchemaEditor`
to allow for new logic that aggregates the alter statements into a single
remake of the table. I'm going to continue down this path unless anyone
has feedback, or recommendations towards a different approach.

--
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/0107018b4a706d00-cccfed7a-4124-4740-a489-e1a3de94cee6-00%40eu-central-1.amazonses.com.

Re: [Django] #34914: Postgres connection is not restarted after it's dropped by the server, even if we use CONN_HEALTH_CHECKS=True

2023-10-19 Thread Django

#34914: Postgres connection is not restarted after it's dropped by the server, 
even
if we use CONN_HEALTH_CHECKS=True
-+-
 Reporter:  Vitor Menegat|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 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 Marcelo Frantz):

 * cc: Marcelo Frantz (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/0107018b49c4d81e-193b02f7-994f-47af-b1db-0755bf276191-00%40eu-central-1.amazonses.com.

Re: [Django] #34914: Postgres connection is not restarted after it's dropped by the server, even if we use CONN_HEALTH_CHECKS=True

2023-10-19 Thread Django

#34914: Postgres connection is not restarted after it's dropped by the server, 
even
if we use CONN_HEALTH_CHECKS=True
-+-
 Reporter:  Vitor Menegat|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 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 Vitor Menegat):

 * cc: Vitor Menegat (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/0107018b49bf61e8-0ad464d8-f296-4309-b7e1-022ef2a572f9-00%40eu-central-1.amazonses.com.

Re: [Django] #34913: [Accessibility] Django Admin high contrast mode no clear session

2023-10-19 Thread Django

#34913: [Accessibility] Django Admin high contrast mode no clear session
-+-
 Reporter:  Cheuk Ting Ho|Owner:  Cheuk
 |  Ting Ho
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  forced-colors  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Thibaud Colas):

 * status:  new => assigned
 * owner:  nobody => Cheuk Ting Ho
 * version:  4.2 => dev
 * keywords:   => accessibility, forced-colors
 * type:  Uncategorized => New feature
 * stage:  Unreviewed => Accepted


Old description:

> When in high contrast mode, Django Admin does not have clear session
> boundaries. Potential fix is to add:
>

> {{{
> @media (forced-colors: active) {
>   #changelist-filter {
>   border: 1px solid;
>   }
> }
> }}}
>
> to different sessions.

New description:

 When in high contrast mode, Django Admin does not have clear boundaries
 areas. Potential fix is to add:


 {{{
 @media (forced-colors: active) {
   #changelist-filter {
   border: 1px solid;
   }
 }
 }}}

 to different areas.

--

Comment:

 Thank you @Cheuk Ting Ho! Yes in particular adding borders to help users
 of Windows high contrast mode distinguish between the different areas of
 the page for the following elements:

 - Header
 - Filters
 - Related content blocks

-- 
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/0107018b49b2102a-e1ff6060-58c2-460a-9a45-b08c9539e476-00%40eu-central-1.amazonses.com.

[Django] #34914: Postgres connection is not restarted after it's dropped by the server, even if we use CONN_HEALTH_CHECKS=True

2023-10-19 Thread Django

#34914: Postgres connection is not restarted after it's dropped by the server, 
even
if we use CONN_HEALTH_CHECKS=True
-+-
   Reporter:  Vitor  |  Owner:  nobody
  Menegat|
   Type:  Bug| Status:  new
  Component:  Database   |Version:  4.2
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I'm using a Django management command to start a container that executes
 DB queries (without any transaction scope): `python manage.py `

 These are the relevant database configs I'm using:
 {{{
 DATABASES = {
 "default": env.db("DATABASE_URL"),
 }

 DATABASES["default"]["ATOMIC_REQUESTS"] = True
 DATABASES["default"]["CONN_HEALTH_CHECKS"] = True
 DATABASES["default"]["CONN_MAX_AGE"] = None  ### I've also
 tried setting this to 0. Same issue
 }}}

 When Django loses the DB connection for whatever reason, I see the error
 `server closed the connection unexpectedly`, but then the error
 `psycopg2.InterfaceError: connection already closed` happens over and over
 again, every time it tries to execute a SQL query. This is very annoying
 because the container needs to be re-created in other for the app to
 function properly.

 Investigating this I found here that the connection health check is
 SKIPPED if
 
(https://github.com/django/django/blob/main/django/db/backends/base/base.py#L576-L580):
 * self.connection is None; OR
 * self.health_checks_enabled = False; OR
 * self.health_check_done = True

 I created a test command to understand what was happening with the
 connection, added some logs to see the connection attributes, and found
 that the connection health check is always skipped because
 `self.health_check_done` is never set to False.

 **My question is:** shouldn't the connection be health checked when
 `self.errors_occurred` flips to True?

 Here's the code I used to test:

 {{{
 import logging
 import time

 from django.core.management import BaseCommand
 from django.db import connection


 logger = logging.getLogger(__name__)


 class Command(BaseCommand):
 help = ""

 def handle(self, *args, **kwargs):
 while True:
 time.sleep(1)
 try:
 logger.info(f"health_check_enabled:
 {connection.health_check_enabled}")
 logger.info(f"health_check_done:
 {connection.health_check_done}")
 logger.info(f"errors_occurred:
 {connection.errors_occurred}")
 with connection.cursor() as cursor:
 cursor.execute("SELECT 1")
 logger.info("query executed")
 except Exception as e:
 logger.exception(e)
 }}}

 Here's the relevant part of the logs:

 {{{
 health_check_enabled: False   ## the connect() method was not yet called
 health_check_done: False  ## the connect() method was not yet called
 errors_occurred: False

 query executed

 health_check_enabled: True
 health_check_done: True
 errors_occurred: False

 server closed the connection unexpectedly
 This probably means the server terminated abnormally
 before or while processing the request.
 Traceback (most recent call last):
   File "/usr/local/lib/python3.11/site-
 packages/django/db/backends/utils.py", line 87, in _execute
 return self.cursor.execute(sql)

 psycopg2.OperationalError: server closed the connection unexpectedly
 This probably means the server terminated abnormally
 before or while processing the request.
 [... Traceback omitted ...]

 health_check_enabled: True
 health_check_done: True
 errors_occurred: True ## This is set to True now, as expected

 Traceback (most recent call last):
   File "/usr/local/lib/python3.11/site-
 packages/django/db/backends/base/base.py", line 308, in _cursor
 return self._prepare_cursor(self.create_cursor(name))
 
   File "/usr/local/lib/python3.11/site-packages/django/utils/asyncio.py",
 line 26, in inner
 return func(*args, **kwargs)
^
   File "/usr/local/lib/python3.11/site-
 packages/django/db/backends/postgresql/base.py", line 330, in
 create_cursor
 cursor = self.connection.cursor()
  
 psycopg2.InterfaceError: connection already closed
 [...Traceback omitted ...]

 health_check_enabled: True
 health_check_done: True
 errors_occurred: True

 Traceback (most recent call last):
   File

Re: [Django] #34911: Admindocs index skips from h1 to h3

2023-10-19 Thread Django

#34911: Admindocs index skips from h1 to h3
-+-
 Reporter:  Thibaud Colas|Owner:
 |  laserhyena
 Type:  Bug  |   Status:  assigned
Component:  contrib.admindocs|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  screen reader, headings|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by laserhyena):

 [https://github.com/django/django/pull/17385 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/0107018b49990266-5b973a1e-4908-4e9d-baa3-4e48f32f306c-00%40eu-central-1.amazonses.com.

[Django] #34913: [Accessibility] Django Admin high contrast mode no clear session

2023-10-19 Thread Django

#34913: [Accessibility] Django Admin high contrast mode no clear session
-+
   Reporter:  Cheuk Ting Ho  |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  contrib.admin  |Version:  4.2
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  1  |
-+
 When in high contrast mode, Django Admin does not have clear session
 boundaries. Potential fix is to add:


 {{{
 @media (forced-colors: active) {
   #changelist-filter {
   border: 1px solid;
   }
 }
 }}}

 to different sessions.

-- 
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/0107018b498da754-9e728492-dbe7-40c1-98b1-70f0ef52044d-00%40eu-central-1.amazonses.com.

Re: [Django] #15578: loaddata and processing order of fixtures

2023-10-19 Thread Django

#15578: loaddata and processing order of fixtures
-+-
 Reporter:  Luc Saffre   |Owner:  Leo
 Type:   |  Suarez
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.2
 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 Leo Suarez):

 * owner:  nobody => Leo Suarez
 * status:  new => assigned


Comment:

 Opened PR to address this item.
 https://github.com/django/django/pull/17384

-- 
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/0107018b497b7e96-ca1bccbb-a4d4-4e51-9ad0-fbe42618bc6a-00%40eu-central-1.amazonses.com.

Re: [Django] #34912: Admindocs back-links and bookmarklet help text is too small

2023-10-19 Thread Django

#34912: Admindocs back-links and bookmarklet help text is too small
-+-
 Reporter:  Thibaud Colas|Owner:  Chris
 |  Frisina
 Type:  Bug  |   Status:  assigned
Component:  contrib.admindocs|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility, font  | Triage Stage:  Accepted
  size   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Natalia Bidart):

 * stage:  Unreviewed => Accepted


Comment:

 Accepting following conversations with Thibaud in the Django sprint at
 Durham.

-- 
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/0107018b49794230-1593afe3-4d6e-4e6c-b277-d18944c2014a-00%40eu-central-1.amazonses.com.

Re: [Django] #34912: Admindocs back-links and bookmarklet help text is too small

2023-10-19 Thread Django

#34912: Admindocs back-links and bookmarklet help text is too small
-+-
 Reporter:  Thibaud Colas|Owner:  Chris
 |  Frisina
 Type:  Bug  |   Status:  assigned
Component:  contrib.admindocs|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility, font  | Triage Stage:
  size   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Thibaud Colas):

 * owner:  nobody => Chris Frisina
 * 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/0107018b49737c9f-5f68b089-f82e-4fb6-a74c-f16a7b686312-00%40eu-central-1.amazonses.com.

[Django] #34912: Admindocs back-links and bookmarklet help text is too small

2023-10-19 Thread Django

#34912: Admindocs back-links and bookmarklet help text is too small
-+-
   Reporter:  Thibaud|  Owner:  nobody
  Colas  |
   Type:  Bug| Status:  new
  Component: |Version:  dev
  contrib.admindocs  |   Keywords:  accessibility, font
   Severity:  Normal |  size
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  1  |
-+-
 We use the `.small` class in admindocs for "Back to parent page" links at
 the bottom of three documentation pages: models, views, templates. This
 makes the text too small to be readable, which doesn’t achieve much as the
 text is at the bottom of the page anyway.

 Example: [https://static-django-
 demo.netlify.app/django_admin_tests/v5.0/english/admin/docs/models/demo.track
 Track Model documentation]

 We also use `.help` text on the Documentation Bookmarklet docs, and could
 equally stop because it makes text too small.

 ---

 Let’s remove those three uses of the `.small` class and the use of `.help`
 and make the text more readable.

-- 
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/0107018b496fbfb8-456a745c-d8e2-44f0-9da8-5b9ee8cd9cba-00%40eu-central-1.amazonses.com.

Re: [Django] #27234: Clarify the type of the django.server logger's 'request' extra context

2023-10-19 Thread Django

#27234: Clarify the type of the django.server logger's 'request' extra context
-+-
 Reporter:  Ben Whale|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.10
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  django.request   | Triage Stage:  Accepted
  runserver WSGIRequest socket   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Natalia Bidart):

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


Comment:

 Ticket #34781 was recently filed and fixed and I did not spot this ticket
 in my "duplicate search", but someone mentioned it today during Django
 Sprints in Durham. Closing as dupe of #34781.

-- 
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/0107018b496439d1-a36cf7bf-bed9-4813-a733-4cd9c921536f-00%40eu-central-1.amazonses.com.

Re: [Django] #34911: Admindocs index skips from h1 to h3

2023-10-19 Thread Django

#34911: Admindocs index skips from h1 to h3
-+-
 Reporter:  Thibaud Colas|Owner:
 |  laserhyena
 Type:  Bug  |   Status:  assigned
Component:  contrib.admindocs|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  screen reader, headings|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Mariusz Felisiak):

 * stage:  Unreviewed => Accepted


-- 
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/0107018b495605ec-84b96889-7a54-4b23-b36e-e4e4ef931df3-00%40eu-central-1.amazonses.com.

Re: [Django] #22757: prefetch_related isn't as effecient as it could be with GenericForeignKey and proxy models

2023-10-19 Thread Django

#22757: prefetch_related isn't as effecient as it could be with 
GenericForeignKey
and proxy models
-+-
 Reporter:  gwahl@…  |Owner:  Nolan
 Type:   |  Little
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  prefetch_related | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Nolan Little):

 * owner:  (none) => Nolan Little
 * 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/0107018b4954992b-79532481-0591-4d76-8118-506a0c37c90f-00%40eu-central-1.amazonses.com.

[Django] #34911: Admindocs index skips from h1 to h3

2023-10-19 Thread Django

#34911: Admindocs index skips from h1 to h3
-+-
   Reporter:  Thibaud|  Owner:  laserhyena
  Colas  |
   Type:  Bug| Status:  assigned
  Component: |Version:  dev
  contrib.admindocs  |   Keywords:  accessibility,
   Severity:  Normal |  screen reader, headings
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  1  |
-+-
 On /admin/doc, the index page has a `Documentation`, and then
 skips straight to headings level 3. We should instead have headings level
 2 so as to avoid confusing screen reader users navigating by heading.

 See for example: [https://static-django-
 demo.netlify.app/django_admin_tests/v5.0/english/admin/docs/ /admin/docs/
 on static-django-demo].

-- 
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/0107018b49536e11-1d96ea47-2e9b-42d6-a51f-40d21204253d-00%40eu-central-1.amazonses.com.

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

2023-10-19 Thread Django

#23577: Rename operations should rename indexes, constraints, sequences and
triggers named after their former value
-+
 Reporter:  Chris Woytowitz  |Owner:  vrocha
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  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 vrocha):

 * owner:  (none) => vrocha
 * status:  new => assigned


Comment:

 I am at DjangoCon US sprints trying to get to the bottom of this

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018b48d69c5e-e635da25-7a8c-4715-989e-53b99217afa7-00%40eu-central-1.amazonses.com.

Re: [Django] #34881: migrate crashes when renaming model referenced twice by ManyToManyField.through model on SQLite.

2023-10-19 Thread Django

#34881: migrate crashes when renaming model referenced twice by
ManyToManyField.through model on SQLite.
+---
 Reporter:  dennisvang  |Owner:  jasehackman
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  dev
 Severity:  Normal  |   Resolution:
 Keywords:  sqlite  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+---
Changes (by jasehackman):

 * owner:  nobody => jasehackman
 * status:  new => assigned


Comment:

 I'm taking part in the DjangoCon US Sprints and am going to try and fix
 this issue.

-- 
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/0107018b48c7d552-3a41b57c-1170-4e80-8b15-e6b017af441c-00%40eu-central-1.amazonses.com.

Re: [Django] #34909: Accessible names for Add / Change buttons in Django Admin

2023-10-19 Thread Django

#34909: Accessible names for Add / Change buttons in Django Admin
-+-
 Reporter:  Eliana Rosselli  |Owner:  Eliana
 |  Rosselli
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility| Triage Stage:  Accepted
  accessible name ux |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Eliana Rosselli):

 * owner:  nobody => Eliana Rosselli
 * 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/0107018b48bf3b17-b8bccb5b-e227-4e9e-b81f-6e2b2b208042-00%40eu-central-1.amazonses.com.

Re: [Django] #34910: Color Contrast Admin Plus Icon

2023-10-19 Thread Django

#34910: Color Contrast Admin Plus Icon
-+-
 Reporter:  laserhyena   |Owner:
 |  laserhyena
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  color contrast |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Thibaud Colas):

 * owner:  nobody => laserhyena
 * status:  new => assigned
 * stage:  Unreviewed => Accepted


Comment:

 Thank you @laserhyena!

 Link to technique:
 https://www.w3.org/WAI/WCAG21/Techniques/general/G207.html

 Comparison of before/after color, confirming the proposed shade: https
 ://contrast-grid.eightshapes.com/?version=1.1.0
 colors=%23121212%2CDark%0D%0A%23ff%2CWhite%0D%0A
 colors=83BC47%2CGreen%20as-is%0D%0A5fa225%2CGreen%20new
 form__tile-size=compact__show-contrast=aaa
 form__show-contrast=aa__show-contrast=aa18
 form__show-contrast=dnp

-- 
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/0107018b48bf2348-ee66084a-801e-47ce-8fe9-153e4add03cc-00%40eu-central-1.amazonses.com.

[Django] #34910: Color Contrast Admin Plus Icon

2023-10-19 Thread Django

#34910: Color Contrast Admin Plus Icon
-+-
   Reporter: |  Owner:  nobody
  laserhyena |
   Type:  Bug| Status:  new
  Component: |Version:  dev
  contrib.admin  |   Keywords:  accessibility,
   Severity:  Normal |  color contrast
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  1  |
-+-
 Identified using automated checks with Axe. When in Light Mode/Theme, Axe
 reports a contrast ratio of 2.2:1 for the Django Admin's plus icon. For
 icons, this should be at least 3:1, as seen in the W3C documentation for
 Technique G207.

 To reproduce, visit the Django Admin and locate one of the green plus
 symbols. Potential new value for the green is represented by # 5fa225.

 Please note the new green should result in acceptable color contrast for
 both Light and Dark mode.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018b48bd903b-685a3e78-1d16-4c48-bd25-e22b94939572-00%40eu-central-1.amazonses.com.

Re: [Django] #34909: Accessible names for Add / Change buttons in Django Admin

2023-10-19 Thread Django

* type: Uncategorized => Bug
* component: Uncategorized => contrib.admin
* stage: Unreviewed => Accepted

Comment:

Thank you for the report @Eliana Rosselli! This is a tricky one. As we
dicussed there is the risk to do something that works better for some
users, but potentially at the expense of others. This article comes to
mind: [https://www.smashingmagazine.com/2022/06/voice-control-usability-
considerations-partially-visually-hidden-link-names/ Voice Control
Usability Considerations For Partially Visually Hidden Link Names].

There is clearly room for improvement here so I will accept the ticket now
– but we need a fair bit of research before deciding what to do about
this. My hunch is that an `aria-describedby` might help, but I’d like to
see ourselves reviewing other patterns.

--
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/0107018b48a2ff4e-4bd83dd7-50bf-47f6-bca0-cb4a09c8e4ae-00%40eu-central-1.amazonses.com.

Re: [Django] #16429: Add configurable caching to FilePathField

2023-10-19 Thread Django

#16429: Add configurable caching to FilePathField
-+-
 Reporter:  Daniel Swarbrick |Owner:  James
 |  Walters
 Type:  New feature  |   Status:  assigned
Component:  Forms|  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 James Walters):

 * owner:  nobody => James Walters
 * status:  new => assigned


Comment:

 I've been able to reproduce this, which I wanted to make sure to do given
 the age of this ticket. FilePathField's choices remain stale after
 changing the contents of its specified filepath. Now I'll get to work on
 this.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018b48a1f125-eda283de-f396-4f89-820a-dbc3e9dc580e-00%40eu-central-1.amazonses.com.

[Django] #34909: Accessible names for Add / Change buttons in Django Admin

2023-10-19 Thread Django

#34909: Accessible names for Add / Change buttons in Django Admin
-+-
   Reporter:  erosselli  |  Owner:  nobody
   Type: | Status:  new
  Uncategorized  |
  Component: |Version:  4.2
  Uncategorized  |   Keywords:  accessibility
   Severity:  Normal |  accessible name ux
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  1  |
-+-
 In the Django Admin home screen, all "Add" and "Change" buttons have the
 same accesible name ("Add" and "Change"), which may be confusing for users
 with screen readers. This was checked with the Accessibility Insights for
 the Web extension.

 Changing the accessible names to "Add " and "Change " might be clearer for users with screen readers, but could make it
 confusing for users using voiceover trying to reference the buttons by
 their visible names (Add / Change).

-- 
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/0107018b48970c95-576878e4-1a92-4627-b652-340dfcec285b-00%40eu-central-1.amazonses.com.

Re: [Django] #34905: Main landmark is on the wrong element

2023-10-19 Thread Django

#34905: Main landmark is on the wrong element
-+-
 Reporter:  Tom Carrick  |Owner:  ontowhee
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  5.0
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  accessibility| 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:"31bdf67a9c443c9acfee8eba53e8f7a3f379241f" 31bdf67a]:
 {{{
 #!CommitTicketReference repository=""
 revision="31bdf67a9c443c9acfee8eba53e8f7a3f379241f"
 [5.0.x] Fixed #34905 -- Corrected admin's main content element rendered in
  tag.

 Regression in 91e617c743b21a0ebad01f18623a8b31f6f58500.

 Thanks Tom Carrick for the report.
 Backport of 89d2ae257bfdbe6f32c4671d97bf572623992ace 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/0107018b488bcb6f-b104a111-aefc-41b3-a330-9db27b8cd912-00%40eu-central-1.amazonses.com.

Re: [Django] #34905: Main landmark is on the wrong element

2023-10-19 Thread Django

#34905: Main landmark is on the wrong element
-+-
 Reporter:  Tom Carrick  |Owner:  ontowhee
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  5.0
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  accessibility| 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 GitHub ):

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


Comment:

 In [changeset:"89d2ae257bfdbe6f32c4671d97bf572623992ace" 89d2ae2]:
 {{{
 #!CommitTicketReference repository=""
 revision="89d2ae257bfdbe6f32c4671d97bf572623992ace"
 Fixed #34905 -- Corrected admin's main content element rendered in 
 tag.

 Regression in 91e617c743b21a0ebad01f18623a8b31f6f58500.

 Thanks Tom Carrick for the report.
 }}}

-- 
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/0107018b488b14bf-6b3ada61-0ddb-418c-bdfa-230e13412c84-00%40eu-central-1.amazonses.com.

Re: [Django] #34908: Contrast Failure for Module Table Headers

2023-10-19 Thread Django

#34908: Contrast Failure for Module Table Headers
-+-
 Reporter:  laserhyena   |Owner:
 |  laserhyena
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  accessibility,   | Triage Stage:  Accepted
  color contrast |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Thibaud Colas):

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


Comment:

 My bad, we were testing on a non-latest version of `main`, this has
 already been fixed (whooo!).

-- 
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/0107018b48876ebf-64198c95-e71c-470d-b893-8b973b3accb2-00%40eu-central-1.amazonses.com.

Re: [Django] #34905: Main landmark is on the wrong element

2023-10-19 Thread Django

#34905: Main landmark is on the wrong element
-+-
 Reporter:  Tom Carrick  |Owner:  ontowhee
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  5.0
 Severity:  Release blocker  |   Resolution:
 Keywords:  accessibility| Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * stage:  Accepted => Ready for checkin


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018b485af4c7-9562f52c-5629-4755-92fe-10b5f2f05db2-00%40eu-central-1.amazonses.com.

Re: [Django] #34908: Contrast Failure for Module Table Headers

2023-10-19 Thread Django

#34908: Contrast Failure for Module Table Headers
-+-
 Reporter:  laserhyena   |Owner:
 |  laserhyena
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  color contrast |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by laserhyena):

 * owner:  nobody => laserhyena
 * 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/0107018b483c61e6-287c2b35-c174-4ba8-8d1e-7f44d8ad2275-00%40eu-central-1.amazonses.com.

Re: [Django] #34908: Contrast Failure for Module Table Headers

2023-10-19 Thread Django

#34908: Contrast Failure for Module Table Headers
-+-
 Reporter:  laserhyena   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  color contrast |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Thibaud Colas):

 * stage:  Unreviewed => Accepted


-- 
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/0107018b483be6e1-963d2c0c-bed1-480a-acb4-32cafcfdd4cd-00%40eu-central-1.amazonses.com.

[Django] #34908: Contrast Failure for Module Table Headers

2023-10-19 Thread Django

#34908: Contrast Failure for Module Table Headers
-+-
   Reporter: |  Owner:  nobody
  laserhyena |
   Type:  Bug| Status:  new
  Component: |Version:  dev
  contrib.admin  |   Keywords:  accessibility,
   Severity:  Normal |  color contrast
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  1  |
-+-
 Identified using automated checks with Axe. When in Light Mode/Theme, Axe
 reports a contrast ratio of 2.41:1, which should be at least 4.5:1

 Visit the Django Admin using Light Mode to reproduce.

-- 
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/0107018b483a341b-e7639db1-965d-4172-a196-afdc20db50cc-00%40eu-central-1.amazonses.com.

Re: [Django] #16429: Add configurable caching to FilePathField

2023-10-19 Thread Django

#16429: Add configurable caching to FilePathField
--+
 Reporter:  Daniel Swarbrick  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Forms |  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
--+

Comment (by James Walters):

 At DjangoCon US, taking a look at this.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #34907: OperationalError during loaddata of fixtures with natural keys on multi-db

2023-10-19 Thread Django

#34907: OperationalError during loaddata of fixtures with natural keys on 
multi-db
-+-
 Reporter:  Florian  |Owner:
 |  abidkhan484
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  natural key, multi-  | Triage Stage:
  db, loaddata   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by abidkhan484):

 * owner:  nobody => abidkhan484
 * 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/0107018b480bd467-8beceb7a-4bea-4561-a7a7-626da457cb82-00%40eu-central-1.amazonses.com.

Re: [Django] #34905: Main landmark is on the wrong element

2023-10-19 Thread Django

#34905: Main landmark is on the wrong element
-+
 Reporter:  Tom Carrick  |Owner:  ontowhee
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  5.0
 Severity:  Release blocker  |   Resolution:
 Keywords:  accessibility| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by ontowhee):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/17382 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/0107018b48087720-fb79abb3-db2a-4cad-a15f-2bf6a5b0fd39-00%40eu-central-1.amazonses.com.

Re: [Django] #34905: Main landmark is on the wrong element

2023-10-19 Thread Django

#34905: Main landmark is on the wrong element
-+
 Reporter:  Tom Carrick  |Owner:  ontowhee
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  5.0
 Severity:  Release blocker  |   Resolution:
 Keywords:  accessibility| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by ontowhee):

 * owner:  nobody => ontowhee
 * 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/0107018b47cb48b9-3a00efe7-39ca-48e3-a469-63c09a91cd11-00%40eu-central-1.amazonses.com.

Re: [Django] #34906: Need help with makemigrations

2023-10-19 Thread Django

#34906: Need help with makemigrations
-+-
 Reporter:  Prasad Rao   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 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


Old description:

> I have a codebase that was developed a while back and I am having some
> difficulty bringing it back to life. It might be that I am a bit rusty
> and this is really simple:
>
> The repo is https://github.com/gprlearn/appregister
>
> I ran "python manage.py makemigrations" and I get the following error:
>
> Traceback (most recent call last):
>   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
> packages\django\core\management\base.py", line 323, in run_from_argv
> self.execute(*args, **cmd_options)
>   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
> packages\django\core\management\base.py", line 361, in execute
> self.check()
>   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
> packages\django\core\management\base.py", line 387, in check
> all_issues = self._run_checks(
>  ^
>   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
> packages\django\core\management\base.py", line 377, in _run_checks
> return checks.run_checks(**kwargs)
>^^^
>   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
> packages\django\core\checks\registry.py", line 72, in run_checks
> new_errors = check(app_configs=app_configs)
>  ^^
>   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
> packages\django\core\checks\translation.py", line 17, in
> check_setting_language_code
> if not language_code_re.match(settings.LANGUAGE_CODE):
>   ^^
>   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
> packages\django\conf\__init__.py", line 79, in __getattr__
> self._setup(name)
>   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
> packages\django\conf\__init__.py", line 66, in _setup
> self._wrapped = Settings(settings_module)
> ^
>   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
> packages\django\conf\__init__.py", line 157, in __init__
> mod = importlib.import_module(self.SETTINGS_MODULE)
>   ^
>   File "C:\Program Files\Python312\Lib\importlib\__init__.py", line 90,
> in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>
>   File "", line 1381, in _gcd_import
>   File "", line 1354, in _find_and_load
>   File "", line 1318, in
> _find_and_load_unlocked
> ModuleNotFoundError: No module named 'djangoproject.settings'
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>   File "C:\Users\prao5\appregister\manage.py", line 21, in 
> main()
>   File "C:\Users\prao5\appregister\manage.py", line 17, in main
> execute_from_command_line(sys.argv)
>   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
> packages\django\core\management\__init__.py", line 381, in
> execute_from_command_line
> utility.execute()
>   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
> packages\django\core\management\__init__.py", line 375, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
> packages\django\core\management\base.py", line 336, in run_from_argv
> connections.close_all()
>   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
> packages\django\db\utils.py", line 219, in close_all
> for alias in self:
>   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
> packages\django\db\utils.py", line 213, in __iter__
> return iter(self.databases)
> ^^
>   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
> packages\django\utils\functional.py", line 80, in __get__
> res = instance.__dict__[self.name] = self.func(instance)
>  ^^^
>   File

Re: [Django] #34905: Main landmark is on the wrong element

2023-10-19 Thread Django

#34905: Main landmark is on the wrong element
-+
 Reporter:  Tom Carrick  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  5.0
 Severity:  Release blocker  |   Resolution:
 Keywords:  accessibility| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by Mariusz Felisiak):

 * cc: Sarah Abderemane, Thibaud Colas (added)
 * version:  dev => 5.0
 * severity:  Normal => Release blocker
 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the report! Regression in
 91e617c743b21a0ebad01f18623a8b31f6f58500. We should change the `#content-
 start` `div` to the `main` landmark instead of `#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/0107018b474e4a0f-f194273a-307f-4316-9d4a-dbc13098641c-00%40eu-central-1.amazonses.com.

[Django] #34906: Need help with makemigrations

2023-10-19 Thread Django

#34906: Need help with makemigrations
-+-
   Reporter:  gprlearn   |  Owner:  nobody
   Type: | Status:  new
  Uncategorized  |
  Component:  Database   |Version:  4.2
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I have a codebase that was developed a while back and I am having some
 difficulty bringing it back to life. It might be that I am a bit rusty and
 this is really simple:

 The repo is https://github.com/gprlearn/appregister

 I ran "python manage.py makemigrations" and I get the following error:

 Traceback (most recent call last):
   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
 packages\django\core\management\base.py", line 323, in run_from_argv
 self.execute(*args, **cmd_options)
   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
 packages\django\core\management\base.py", line 361, in execute
 self.check()
   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
 packages\django\core\management\base.py", line 387, in check
 all_issues = self._run_checks(
  ^
   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
 packages\django\core\management\base.py", line 377, in _run_checks
 return checks.run_checks(**kwargs)
^^^
   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
 packages\django\core\checks\registry.py", line 72, in run_checks
 new_errors = check(app_configs=app_configs)
  ^^
   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
 packages\django\core\checks\translation.py", line 17, in
 check_setting_language_code
 if not language_code_re.match(settings.LANGUAGE_CODE):
   ^^
   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
 packages\django\conf\__init__.py", line 79, in __getattr__
 self._setup(name)
   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
 packages\django\conf\__init__.py", line 66, in _setup
 self._wrapped = Settings(settings_module)
 ^
   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
 packages\django\conf\__init__.py", line 157, in __init__
 mod = importlib.import_module(self.SETTINGS_MODULE)
   ^
   File "C:\Program Files\Python312\Lib\importlib\__init__.py", line 90, in
 import_module
 return _bootstrap._gcd_import(name[level:], package, level)

   File "", line 1381, in _gcd_import
   File "", line 1354, in _find_and_load
   File "", line 1318, in
 _find_and_load_unlocked
 ModuleNotFoundError: No module named 'djangoproject.settings'

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File "C:\Users\prao5\appregister\manage.py", line 21, in 
 main()
   File "C:\Users\prao5\appregister\manage.py", line 17, in main
 execute_from_command_line(sys.argv)
   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
 packages\django\core\management\__init__.py", line 381, in
 execute_from_command_line
 utility.execute()
   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
 packages\django\core\management\__init__.py", line 375, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
 packages\django\core\management\base.py", line 336, in run_from_argv
 connections.close_all()
   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
 packages\django\db\utils.py", line 219, in close_all
 for alias in self:
   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
 packages\django\db\utils.py", line 213, in __iter__
 return iter(self.databases)
 ^^
   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
 packages\django\utils\functional.py", line 80, in __get__
 res = instance.__dict__[self.name] = self.func(instance)
  ^^^
   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-
 packages\django\db\utils.py", line 147, in databases
 self._databases = settings.DATABASES
   ^^
   File "C:\Users\prao5\AppData\Roaming\Python\Python312\site-

[Django] #34905: Main landmark is on the wrong element

2023-10-19 Thread Django

#34905: Main landmark is on the wrong element
-+---
   Reporter:  Tom Carrick|  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.admin  |Version:  dev
   Severity:  Normal |   Keywords:  accessibility
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+---
 It's currently wrapping the navbar, but it should be inside. Main element
 should not have repeated content such as navigation that appears on
 multiple pages.

-- 
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/0107018b4729fd8e-c6af7492-d98a-4f43-96f2-236cd3b422b2-00%40eu-central-1.amazonses.com.

Re: [Django] #34904: Changing email object after sending mutates mail in mail.outbox

2023-10-19 Thread Django

#34904: Changing email object after sending mutates mail in mail.outbox
-+-
 Reporter:  CheesyPhoenix|Owner:
 |  CheesyPhoenix
 Type:  Bug  |   Status:  assigned
Component:  Core (Mail)  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  mail.outbox locmem   | Triage Stage:  Accepted
  testing|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  nobody => CheesyPhoenix
 * status:  new => assigned
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the report.

-- 
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/0107018b4702ac2f-c0f4baff-eef0-453a-a2b5-01007c92300f-00%40eu-central-1.amazonses.com.

Re: [Django] #34462: Deletions in admin panel create N + 1 queries

2023-10-19 Thread Django

#34462: Deletions in admin panel create N + 1 queries
-+-
 Reporter:  Mike Lissner |Owner:  Akash
 Type:   |  Kumar Sen
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:  performance  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Akash Kumar Sen):

 * 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/0107018b46e4ac8b-3750638b-f8ff-42d8-aabd-edb7eeedf350-00%40eu-central-1.amazonses.com.

48 matches

Mail list logo