Re: [Django] #33618: Wrong behavior on queryset update when multiple inheritance

[Django]

#33618: Wrong behavior on queryset update when multiple inheritance
-+-
 Reporter:  Sonicold |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  queryset update  | Triage Stage:  Ready for
  mutiple inheritance|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * stage:  Accepted => Ready for checkin


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018002978ed5-06f544d9-81d1-45bc-9210-015c94062864-00%40eu-central-1.amazonses.com.

Re: [Django] #33618: Wrong behavior on queryset update when multiple inheritance

[Django]

#33618: Wrong behavior on queryset update when multiple inheritance
-+-
 Reporter:  Sonicold |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  queryset update  | Triage Stage:  Accepted
  mutiple inheritance|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 > I'll let Mariusz and Carlton chime in here. This is a data loss issue so
 [https://docs.djangoproject.com/en/4.0/internals/release-process/ it
 should theoretically qualify] but the issue has been around forever and
 only happens for uncommon model structures so I'd be wary of introducing a
 regression via a minor version if this was backported and possibly cause a
 different kind of data loss issue.

 IMO, the risk of introducing another regression is too great. Moreover it
 was reported after Django 2.2 EOL (April, 1st) so it wouldn't be
 backported regardless of our decision.

-- 
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/0107018002775180-d7b9bc8a-7c4a-41b0-927c-804d52bfabcf-00%40eu-central-1.amazonses.com.

Re: [Django] #33611: Allow View subclasses to define async method handlers.

[Django]

#33611: Allow View subclasses to define async method handlers.
-+-
 Reporter:  Carlton Gibson   |Owner:  Carlton
 |  Gibson
 Type:  New feature  |   Status:  closed
Component:  Generic views|  Version:  4.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  async, asgi, views   | 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 GitHub ):

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


Comment:

 In [changeset:"9ffd4eae2ce7a7100c98f681e2b6ab818df384a4" 9ffd4ea]:
 {{{
 #!CommitTicketReference repository=""
 revision="9ffd4eae2ce7a7100c98f681e2b6ab818df384a4"
 Fixed #33611 -- Allowed View subclasses to define async method handlers.
 }}}

-- 
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/01070180026a8cf7-d9e81183-60cd-4193-bf56-7ca4bdc5eb06-00%40eu-central-1.amazonses.com.

Re: [Django] #33173: Python 3.11 compatibility

[Django]

#33173: Python 3.11 compatibility
-+-
 Reporter:  Mariusz Felisiak |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Other) |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by GitHub ):

 In [changeset:"2ee4caf56b8e000cabbb73ad81ff05738d6d0a35" 2ee4caf5]:
 {{{
 #!CommitTicketReference repository=""
 revision="2ee4caf56b8e000cabbb73ad81ff05738d6d0a35"
 Refs #33173 -- Fixed test_runner/test_utils tests on Python 3.11+.

 Python 3.11 uses fully qualified test name in unittest output. See
 
https://github.com/python/cpython/commit/755be9b1505af591b9f2ee424a6525b6c2b65ce9
 }}}

-- 
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/0107018002678af2-6621915a-edf7-4785-b8b8-37b27a8973a6-00%40eu-central-1.amazonses.com.

Re: [Django] #33619: Proxy model does not inherite indexes and constraints from base model

[Django]

#33619: Proxy model does not inherite indexes and constraints from base model
-+-
 Reporter:  Jaska Lee|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  contrib.admin|  Version:  3.2
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  multiple model   | Triage Stage:
  admin  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jaska Lee):

 * resolution:  invalid => wontfix


Comment:

 hello,

 Specific meta inheritance on the proxy model does not solve the problem.
 The indexes and constraints from the base model are still missing in the
 proxy model, while other attributes seem to be successfully inherited. The
 Django version is 3.2.2.

 I am not necessarily looking for a solution for a use case here. The
 solution is clear. I was just trying to indicate how the problem occurred.

 The issue seems be rather platform related which might be worth of looking
 into.

 thanks

-- 
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/0107018002587973-924e30c2-de48-4ef3-b413-afb3ae9fcc48-00%40eu-central-1.amazonses.com.

Re: [Django] #33621: Remove "alternate" and change "schema" in sitemaps. (was: update in sitemap.xml the "xmlns:xhtml" shema.)

[Django]

#33621: Remove "alternate" and change "schema" in sitemaps.
--+--
 Reporter:  Maxim Danilov |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.sitemaps  |  Version:  4.0
 Severity:  Normal|   Resolution:  invalid
 Keywords:  sitemap.xml   | Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by Mariusz Felisiak):

 * cc: Florian Demmer (added)
 * status:  new => closed
 * has_patch:  1 => 0
 * resolution:   => invalid


Comment:

 `alternate` is required for sitemaps that specify alternate language
 pages. As far as I'm aware the current implementation is in line with the
 [https://developers.google.com/search/docs/advanced/crawling/localized-
 versions#sitemap Google guidelines]. Moreover sitemaps doesn't need to be
 human-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/01070180025281ff-28f2781a-b5c9-4d9e-99b5-9e3e36f50757-00%40eu-central-1.amazonses.com.

Re: [Django] #33622: Allow overriding FormSet's error messages for too few and too many forms. (was: Allow overriding `too_few_forms` and `too_many_forms` validation errors in `FormSet`s)

[Django]

#33622: Allow overriding FormSet's error messages for too few and too many 
forms.
-+
 Reporter:  Christoph Schindler  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  4.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 Mariusz Felisiak):

 * has_patch:  1 => 0
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the ticket, sounds reasonable. Please submit PR via GitHub.
 Tests and release notes are required.

-- 
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/010701800242d386-63b0fa98-5719-4f3f-985d-7266961b3259-00%40eu-central-1.amazonses.com.

Re: [Django] #33622: Allow overriding `too_few_forms` and `too_many_forms` validation errors in `FormSet`s

[Django]

#33622: Allow overriding `too_few_forms` and `too_many_forms` validation errors 
in
`FormSet`s
-+-
 Reporter:  Christoph Schindler  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Christoph Schindler):

 * Attachment "patch.diff" 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/01070180021ac68b-56b53e76-227c-43cb-b686-a8b2ea96a6cf-00%40eu-central-1.amazonses.com.

[Django] #33622: Allow overriding `too_few_forms` and `too_many_forms` validation errors in `FormSet`s

[Django]

#33622: Allow overriding `too_few_forms` and `too_many_forms` validation errors 
in
`FormSet`s
---+
   Reporter:  Christoph Schindler  |  Owner:  nobody
   Type:  New feature  | Status:  new
  Component:  Forms|Version:  4.0
   Severity:  Normal   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  1
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 Moving the messages to `default_error_messages` enables overriding them
 via the `error_messages` argument when instantiating the `FormSet`.

 I would prefer being able to override them via `inlineformset_factory`,
 but that is for another day.

-- 
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/01070180021a8313-3eabec2b-dd58-4c10-bcb2-b8f5a043bc93-00%40eu-central-1.amazonses.com.

[Django] #33621: update in sitemap.xml the "xmlns:xhtml" shema.

[Django]

#33621: update in sitemap.xml the "xmlns:xhtml" shema.
+-
   Reporter:  Maxim Danilov |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  contrib.sitemaps  |Version:  4.0
   Severity:  Normal|   Keywords:  sitemap.xml
   Triage Stage:  Unreviewed|  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+-
 default sitemap.xml
 in case if i have multilanguage sitemap with:

 
 

 Browser shows plain text. For example, google sitemap.xml
 "https://www.google.com/nonprofits/sitemap.xml";.
 
[[Image(https://habrastorage.org/webt/1f/jz/ii/1fjziijky8a0ptaolhrrzvcjx8c.png)]]

 Without rel="alternate" all is human-readable.
 
[[Image(https://habrastorage.org/webt/bq/up/hq/bquphqekr3lvcxy2bxu_fllicye.png)]]

 It happens only if i have rel="alternate".

 I found, that we should update in
 django.contrib.sitemaps\templates\sitemap.xml
 {{{
 xmlns:xhtml="http://www.w3.org/1999/xhtml";
 }}}
 to
 {{{
 xmlns:xhtml="http://www.w3.org/TR/xhtml11/xhtml11_schema.html";
 }}}

 I found the similar issue https://code.djangoproject.com/ticket/33117, but
 there probably was wrong idea, about "invalid xml"

-- 
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/0107018000421a41-7e689d09-539e-4be0-abe1-0724247acbe0-00%40eu-central-1.amazonses.com.

Re: [Django] #32125: Added basic support for elements for suggestions in Input widgets

[Django]

#32125: Added basic support for  elements for suggestions in Input
widgets
-+-
 Reporter:  Volodymyr|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  dev
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  datalist, forms, | Triage Stage:
  html5  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by Michael):

 Replying to [comment:2 Carlton Gibson]:
 > There was some discussion when adding autocomplete to the admin as to
 whether to include a datalist widget. (ref #14370 and
 [https://groups.google.com/g/django-
 developers/c/jGgZngTq3Gw/m/VEFcxUEJAwAJ mailing list discussion].) Perhaps
 support is better now but, conclusion was more or less that browser
 support wasn't really good enough to use there.
 >
 > I'm going to close as wontfix for now. The custom widget is exactly the
 right way to go.
 >
 > For an addition like this, I would suggest wrapping it into a small
 third-party library so that people can try it out and then approaching the
 DevelopersMailingList to see if there's an appetite to bring such into
 core. Thanks.


 Support for it is looking pretty good now: https://caniuse.com/datalist
 I think this is going to become more and more necessary. This along with
 JavaScript modules really makes Django show its age.

-- 
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/0107017fffdb595a-a54177f0-8ebb-4867-bad1-8b31d15bac98-00%40eu-central-1.amazonses.com.

Re: [Django] #33618: Wrong behavior on queryset update when multiple inheritance

[Django]

#33618: Wrong behavior on queryset update when multiple inheritance
-+-
 Reporter:  Sonicold |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  queryset update  | Triage Stage:  Accepted
  mutiple inheritance|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 > Do you know if this patch will be backported in older django versions ?

 I'll let Mariusz and Carlton chime in here. This is a data loss issue so
 [https://docs.djangoproject.com/en/4.0/internals/release-process/ it
 should theoretically qualify] but the issue has been around forever and
 only happens for uncommon model structures so I'd be wary of introducing a
 regression via a minor version if this was backported and possibly cause a
 different kind of data loss 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/0107017fff9936c0-f282a60c-d06f-4c06-b1fc-c8fa2f13a02b-00%40eu-central-1.amazonses.com.

Re: [Django] #33471: AlterField operation should be noop when adding/changing choices on SQLite.

[Django]

#33471: AlterField operation should be noop when adding/changing choices on 
SQLite.
-+-
 Reporter:  David Szotten|Owner:  Sarah
 Type:   |  Boyce
  Cleanup/optimization   |   Status:  closed
Component:  Migrations   |  Version:  4.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"65effbdb101714ac98b3f143eaccadd8e4f08361" 65effbdb]:
 {{{
 #!CommitTicketReference repository=""
 revision="65effbdb101714ac98b3f143eaccadd8e4f08361"
 Fixed #33471 -- Made AlterField operation a noop when changing "choices".

 This also allows customizing attributes of fields that don't affect
 a column definition.
 }}}

-- 
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/0107017fff5bb7a1-cbb63255-4dc3-492e-8008-852e29b35f6c-00%40eu-central-1.amazonses.com.

Re: [Django] #30352: Error al ejecutar python manage.py sin sealizar cambios

[Django]

#30352: Error al ejecutar python manage.py sin sealizar cambios
-+-
 Reporter:  irv-ro-j |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (System |  Version:  2.2
  checks)|
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  Reload Django| Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by JudgeGregg):

 See https://github.com/encode/django-rest-framework/issues/7078

 Upgrading django-rest-framework to >= 3.11 should mitigate 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/0107017fff3094fd-0b3897dc-b57f-4fa5-a91c-8b13cecd8d5d-00%40eu-central-1.amazonses.com.

Re: [Django] #31617: Improve overall admin accessibility.

[Django]

#31617: Improve overall admin accessibility.
-+-
 Reporter:  Gustavo Siñovsky |Owner:  Saugat
 |  Rajbhandari
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility, ui,   | Triage Stage:
  ux, admin  |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-

Comment (by Carlton Gibson ):

 In [changeset:"6991880109e35c879b71b7d9d9c154baeec12b89" 69918801]:
 {{{
 #!CommitTicketReference repository=""
 revision="6991880109e35c879b71b7d9d9c154baeec12b89"
 Refs #31617 -- Added an id for helptext in admin forms.
 }}}

-- 
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/0107017ffe78d724-7a9d0567-684a-4509-9613-57d2d10a5f79-00%40eu-central-1.amazonses.com.

Re: [Django] #33471: AlterField operation should be noop when adding/changing choices on SQLite.

[Django]

#33471: AlterField operation should be noop when adding/changing choices on 
SQLite.
-+-
 Reporter:  David Szotten|Owner:  Sarah
 Type:   |  Boyce
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * 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/0107017ffe4ab171-01c791e6-f57e-4cff-9745-7855c0e182ab-00%40eu-central-1.amazonses.com.

Re: [Django] #33618: Wrong behavior on queryset update when multiple inheritance

[Django]

#33618: Wrong behavior on queryset update when multiple inheritance
-+-
 Reporter:  Sonicold |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  queryset update  | Triage Stage:  Accepted
  mutiple inheritance|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Sonicold):

 Replying to [comment:3 Simon Charette]:
 > I think https://github.com/django/django/pull/15563 should do. Could you
 confirm Sonicold.

 Thank you Simon Charette for your quick answer and fix. It works well with
 the example I have posted and also with a more complex model with many
 more inheritances.

 Do you know if this patch will be backported in older django versions ?

-- 
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/0107017ffe429141-16f4c875-d9f1-4796-819c-795913af144b-00%40eu-central-1.amazonses.com.

Re: [Django] #33611: Allow View subclasses to define async method handlers.

[Django]

#33611: Allow View subclasses to define async method handlers.
-+-
 Reporter:  Carlton Gibson   |Owner:  Carlton
 |  Gibson
 Type:  New feature  |   Status:  assigned
Component:  Generic views|  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:  async, asgi, views   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107017ffe0da215-879369f4-fd97-43e3-983c-73388c5d56ed-00%40eu-central-1.amazonses.com.

Re: [Django] #33620: Accessibility in pipeline

[Django]

#33620: Accessibility in pipeline
-+-
 Reporter:  Sarah Abderemane |Owner:  Sarah
 |  Abderemane
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility, ux,   | Triage Stage:  Accepted
  ui, admin  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Mariusz Felisiak):

 * status:  closed => new
 * resolution:  duplicate =>
 * stage:  Unreviewed => Accepted


Comment:

 Fine, a separate ticket works for me too :D

-- 
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/0107017ffe0bc119-10cad6b0-cf37-404b-9efd-963c6a620dd1-00%40eu-central-1.amazonses.com.

Re: [Django] #33618: Wrong behavior on queryset update when multiple inheritance

[Django]

#33618: Wrong behavior on queryset update when multiple inheritance
-+-
 Reporter:  Sonicold |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  queryset update  | Triage Stage:  Accepted
  mutiple inheritance|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * needs_docs:  1 => 0
 * has_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/0107017ffdfb804c-30f3b9d3-cc1e-40c7-92ef-4cb901c0cf95-00%40eu-central-1.amazonses.com.

Re: [Django] #33620: Accessibility in pipeline

[Django]

#33620: Accessibility in pipeline
-+-
 Reporter:  Sarah Abderemane |Owner:  Sarah
 |  Abderemane
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  accessibility, ux,   | Triage Stage:
  ui, admin  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by Carlton Gibson):

 Ooops. I asked Sarah to open a separate ticket, because the multiple
 conversations around the large scope accessibility tickets were getting
 too hard to follow. Sorry 😬

 Either way, thanks for picking this up Sarah. Yes, adding the CI tools is
 a good step to help us move forward.

-- 
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/0107017ffdf85225-bb793030-5ab5-476b-ab5e-a3651206aa3d-00%40eu-central-1.amazonses.com.

Re: [Django] #33620: Accessibility in pipeline

[Django]

#33620: Accessibility in pipeline
-+-
 Reporter:  Sarah Abderemane |Owner:  Sarah
 |  Abderemane
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  accessibility, ux,   | Triage Stage:
  ui, admin  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Mariusz Felisiak):

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


Comment:

 IMO a separate ticket is not needed, please use `Refs #31617 --` in your
 patch.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107017ffdf63a78-06ba361c-069f-4f33-badc-0f884c3f96bf-00%40eu-central-1.amazonses.com.

Re: [Django] #33619: Proxy model does not inherite indexes and constraints from base model

[Django]

#33619: Proxy model does not inherite indexes and constraints from base model
-+-
 Reporter:  Jaska Lee|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  contrib.admin|  Version:  3.2
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  multiple model   | Triage Stage:
  admin  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Jaska Lee):

 alright, thanks

-- 
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/0107017ffdd89d5b-cf78376e-b6b9-434d-a81a-1f41671a2ec9-00%40eu-central-1.amazonses.com.

[Django] #33620: Accessibility in pipeline

[Django]

#33620: Accessibility in pipeline
-+-
   Reporter:  Sarah  |  Owner:  Sarah Abderemane
  Abderemane |
   Type:  New| Status:  assigned
  feature|
  Component: |Version:  dev
  contrib.admin  |   Keywords:  accessibility, ux,
   Severity:  Normal |  ui, admin
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  1  |
-+-
 Automate part of the process by including tools such as aXe into the CI
 pipeline, to make sure new changes come with at least the very basic
 accessibility considerations.

 This is a part of the ticket #31617

-- 
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/0107017ffdc20412-f30b3779-76c9-4e3d-a9c3-36a92db95fb2-00%40eu-central-1.amazonses.com.