Re: [Django] #33701: Highlight error location in the technical 500 debug page on Python 3.11+.

[Django]

#33701: Highlight error location in the technical 500 debug page on Python 
3.11+.
-+-
 Reporter:  Adam Johnson |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Error reporting  |  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
-+-
Changes (by Hrushikesh Vaidya):

 * cc: Hrushikesh Vaidya (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/01070180e43fbd00-ac37990b-55c7-4424-b936-2a281ea1b56e-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
-+-

Comment (by Sarah Abderemane):

 Thank you Thibaud for your suggestions and recommendations !

 > 1. Confirm what exactly is needed between a testing tool (write
 assertions, break the build if fails) and a reporting tool (tests a given
 page and reports results)

 My guess was to do both, to be able to test fields separately and also the
 hole admin to view improvements needed for templates of the admin to keep
 the admin accessible. I may be wrong, but not sure how to test correctly
 fields / inputs separately.

 > 2. Check whether there are any restrictions on what can run in CI (I
 can’t see whether Selenium tests run there)

 Actually there are javascript tests run with QUnit and those tests are
 already run in the pipeline, I just add another workflow dedicated for
 accessibility. I started to implement
 
[https://github.com/django/django/compare/main...sabderemane:ticket_33620?expand=1
 Axe with QUnit], may be not the best way. I can go for another solution as
 you have suggested.

 For restrictions it's not a problem, Tom suggest me to use his
 [https://github.com/knyghty/django-admin-demo django admin demo], I can
 run his demo in the pipeline and launch a reporting tool on it. I can show
 result in console and even add a report in a file which will be an
 artifact keep a defined period if we want. I just have to pay attention to
 the duration of the job.


 > 3. Decide whether to use a Python Selenium integration or a JS-based
 tool (looks like ​Django already uses Puppeteer?).
 I think QUnit is run via puppeteer with Grunt, that's why I started my
 implementation based on this tool but we can decide to go for something
 else if it's not relevant.

 ''Since both Pa11y and Lighthouse are built upon Puppeteer, they can be
 used via their JS API so we can first use a Puppeteer script to log in,
 then hand over to those tools.'' => Yes, I think with the use of the
 reporting tool, I can go for it since Puppeteer is already in the project.

 I don't have any particular opinion about 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/01070180e388f370-ec11a68e-c278-4c16-8862-98eab83d0643-00%40eu-central-1.amazonses.com.

Re: [Django] #33728: Tab order should match visual order for admin model forms’ submit buttons

[Django]

#33728: Tab order should match visual order for admin model forms’ submit 
buttons
-+-
 Reporter:  Thibaud Colas|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:
  keyboard, ux   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by Mehrdad Moradizadeh):

 Yes, I agree with you. I have made several mistakes before because of this
 design decision. I think the order should be "save", "save and add
 another", and "save and continue editing" respectively. I would like to
 work on this issue if gets 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/01070180e31787ee-0dff0e4b-7b19-40d9-a234-bf6c2854fc17-00%40eu-central-1.amazonses.com.

[Django] #33731: Updating choices of ChoiceField does not update the underlying widget's choices

[Django]

#33731: Updating choices of ChoiceField does not update the underlying widget's
choices
-+-
   Reporter:  Stefan-|  Owner:  nobody
  Ionut Tarabuta |
   Type:  Bug| Status:  new
  Component:  Forms  |Version:  3.2
   Severity:  Normal |   Keywords:  ChoiceField,
   Triage Stage: |  choices, form
  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 == Issue

 The choices of ChoiceField can be updated by reassigning the choices
 attribute to a new list of choices. For example, the code below will
 append 2 more options to the existing choices.

 {{{
 self.fields["my_field"].choices += (("choice1", "Choice 1"), ("choice2",
 "Choice 2"))
 }}}

 Any operation which involves assignment correctly updates the choices of
 ChoiceField as well as the underlying widget's choices (what gets rendered
 in the browser).

 However, using other list operations, such as insert, will not update the
 underlying widget's choices. These operations are useful when precise
 ordering of choices is desired. For example, the following code will not
 update the underlying widget's choices (what gets rendered in the
 browser), but just the form field's choices:

 {{{
 self.fields["my_field"].choices.insert(5, ("choice1", "Choice 1"))
 }}}

 == Workaround

 The issue can be worked around by performing any assignment on the choices
 of the ChoiceField, but this is by no means a permanent solution. See the
 code below which will cause the widget choices to also be updated.

 {{{
 self.fields["my_field"].choices.insert(5, ("choice1", "Choice 1"))  #
 Insert desired choice. Field is updated, but widget is not.

 self.fields["my_field"].choices = self.fields["my_field"].choices  # Force
 the widget to be updated.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070180e3057a30-e22417a5-931b-4d0b-bf4a-06f44382f45c-00%40eu-central-1.amazonses.com.

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

[Django]

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

Comment (by Mehrdad Moradizadeh):

 I have made a [https://github.com/django/django/pull/15718 PR] 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/01070180e2fe3cc0-3aa98f6b-a551-455b-8d0e-fc6d14e90739-00%40eu-central-1.amazonses.com.

[Django] #33730: FilteredRelation join duplicated when referenced in multiple filter statements

[Django]

#33730: FilteredRelation join duplicated when referenced in multiple filter
statements
-+-
   Reporter:  Ben Nace   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  3.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  |
-+-
 Given the following models
 {{{
 class Grandparent(models.Model):
 tag = models.CharField(max_length=100)
 enabled = models.BooleanField(default=True)


 class Parent(models.Model):
 tag = models.CharField(max_length=100)
 grandparent = models.ForeignKey(Grandparent, on_delete=models.CASCADE)


 class Child(models.Model):
 tag = models.CharField(max_length=100)
 parents = models.ManyToManyField(Parent)
 }}}

 When doing the following query with a filtered relation and a single
 filter statement, the SQL is generated as expected:

 {{{
 Child.objects.alias(a_parents=FilteredRelation('parents',
 condition=Q(tag='a'))).filter(a_parents__grandparent__enabled=True,
 a_parents__grandparent__tag='x')
 }}}

 {{{
 SELECT "test_app_child"."id", "test_app_child"."tag" FROM "test_app_child"
 INNER JOIN "test_app_child_parents" ON ("test_app_child"."id" =
 "test_app_child_parents"."child_id") INNER JOIN "test_app_parent"
 a_parents ON ("test_app_child_parents"."parent_id" = a_parents."id" AND
 ("test_app_child"."tag" = 'a')) INNER JOIN "test_app_grandparent" ON
 (a_parents."grandparent_id" = "test_app_grandparent"."id") WHERE
 ("test_app_grandparent"."enabled" AND "test_app_grandparent"."tag" = 'x')
 }}}

 However, when the filter conditions are split across multiple calls to the
 filter function, say from them being applied in different functions, the
 joins for the filtered relation get duplicated in the SQL.

 {{{
 Child.objects.alias(a_parents=FilteredRelation('parents',
 
condition=Q(tag='a'))).filter(a_parents__isnull=False).filter(a_parents__grandparent__tag='x')
 }}}

 {{{
 SELECT "test_app_child"."id", "test_app_child"."tag" FROM "test_app_child"
 INNER JOIN "test_app_child_parents" ON ("test_app_child"."id" =
 "test_app_child_parents"."child_id") INNER JOIN "test_app_parent"
 a_parents ON ("test_app_child_parents"."parent_id" = a_parents."id" AND
 ("test_app_child"."tag" = 'a')) INNER JOIN "test_app_child_parents" T4 ON
 ("test_app_child"."id" = T4."child_id") INNER JOIN "test_app_parent" T5 ON
 (T4."parent_id" = T5."id" AND ("test_app_child"."tag" = 'a')) INNER JOIN
 "test_app_grandparent" ON (T5."grandparent_id" =
 "test_app_grandparent"."id") WHERE (a_parents."id" IS NOT NULL AND
 "test_app_grandparent"."tag" = 'x')
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070180e2b14936-3bdcb404-7bd6-46e7-b6c9-773f6beb757c-00%40eu-central-1.amazonses.com.

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

[Django]

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

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/15718 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/01070180e2aaef46-b1f36ac3-8120-4a8a-b724-8929206d3b0c-00%40eu-central-1.amazonses.com.

Re: [Django] #15727: Add support for Content-Security-Policy (CSP) to core

[Django]

#15727: Add support for Content-Security-Policy (CSP) to core
---+--
 Reporter:  db.pub.mail@…  |Owner:  Tom Forbes
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Dylan Young):

 One potential snag here is that I don't think Django can currently support
 multiple of the same header currently (aside from Set-Cookie), unless
 there's some API I'm missing...

 Is this something there's interest in adding to core?  It looks like the
 python native wsgiref supports this as well:
 
https://docs.python.org/3/library/wsgiref.html?highlight=headers%20multi%20value
 #module-wsgiref.headers.

 See here:

 https://github.com/w3c/webappsec-
 
csp/issues/215#:~:text=A%20server%20MUST%20NOT%20send,resource%20or%20with%20different%20resources.

 I don't think it's critical, but it'd be nice as it's standards compliant
 behaviour.

-- 
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/01070180e290d7f5-d3a7dac0-9b20-4b3f-a1fc-2d3a85e2658d-00%40eu-central-1.amazonses.com.

Re: [Django] #33729: AutocompleteSelect widget broken after moving from django 2.2 to django 3.2 (was: \AutocompleteSelect widget broken after moving from django 2.2 to django 3.2)

[Django]

#33729: AutocompleteSelect widget broken after moving from django 2.2 to django 
3.2
+--
 Reporter:  exo |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.admin   |  Version:  3.2
 Severity:  Normal  |   Resolution:  invalid
 Keywords:  AutocompleteSelect  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070180e2148b4a-3de97a97-843b-4dbd-9266-d2c7e6f3096b-00%40eu-central-1.amazonses.com.

Re: [Django] #33729: \AutocompleteSelect widget broken after moving from django 2.2 to django 3.2 (was: [BUG] AutocompleteSelect widget broken after moving from django 2.2 to django 3.2)

[Django]

#33729: \AutocompleteSelect widget broken after moving from django 2.2 to django
3.2
+--
 Reporter:  exo |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.admin   |  Version:  3.2
 Severity:  Normal  |   Resolution:  invalid
 Keywords:  AutocompleteSelect  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070180e213fa42-876e37d1-4564-4981-9996-bdcbee7f30b3-00%40eu-central-1.amazonses.com.

Re: [Django] #33729: [BUG] AutocompleteSelect widget broken after moving from django 2.2 to django 3.2

[Django]

#33729: [BUG] AutocompleteSelect widget broken after moving from django 2.2 to
django 3.2
+--
 Reporter:  exo |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.admin   |  Version:  3.2
 Severity:  Normal  |   Resolution:  invalid
 Keywords:  AutocompleteSelect  | 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


Comment:

 Replying to [ticket:33729 exo]:
 > Hello :) After upgrading `Django` version to `3.2`, widget
 `AutocompleteSelect` that I use in `django` admin panel (to have a drop-
 down from which I can choose an object) **is broken**.
 >
 > The error I see is
 > {{{
 > AttributeError at /admin/question/
 > 'QuerySet' object has no attribute 'name'
 >
 > Request Method:   GET
 > Request URL:  http://localhost:8000/admin/question/
 > Django Version:   3.2.13
 > Exception Type:   AttributeError
 > Exception Value:
 > 'QuerySet' object has no attribute 'name'
 > Exception Location:   /home/django-app/env/lib/python3.8/site-
 packages/django/contrib/admin/widgets.py, line 412, in build_attrs
 > Python Executable:/home/django-app/env/bin/python3
 > Python Version:   3.8.10
 > Python Path:
 > ['/home/django-app/testsite',
 >  '/usr/lib/python38.zip',
 >  '/usr/lib/python3.8',
 >  '/usr/lib/python3.8/lib-dynload',
 >  '/home/django-app/env/lib/python3.8/site-packages']
 > Server time:  Fri, 20 May 2022 10:13:27 +
 > Error during template rendering
 > In template /home/django-
 app/testsite/polls/templates/admin/question_export.html, error at line 18
 >
 > 'QuerySet' object has no attribute 'name'
 > 11
 > 12{% block content %}
 > 13
 > 14  Select question to export:
 > 15
 > 16{% csrf_token %}
 > 17
 > 18{{form.as_table}}
 > 19
 > 20
 > 21
 > 22
 > 23
 > 24
 > 25{{form.media}}
 > 26{% endblock %}
 > 27
 > }}}
 > `AutocompleteSelect` inherits from `AutocompleteMixin`
 >
 > When I compare `AutocompleteMixin` for `django 3.2` and `django 2.2`
 >
 
https://github.com/django/django/blob/3.2.13/django/contrib/admin/widgets.py#L410-L412
 >
 
https://github.com/django/django/blob/2.2.7/django/contrib/admin/widgets.py#L411
 >
 > I see that they added new attributes
 > {{{
 > 'data-app-label': self.field.model._meta.app_label,
 > 'data-model-name': self.field.model._meta.model_name,
 > 'data-field-name': self.field.name,
 > }}}
 > in `django 3.2`
 > but there is no `name` on `self.field` and probably that's why I get
 this error.

 `self.field` should be a `Field` instance not a `QuerySet`. Moreover
 autocomplete works for me. It looks like an issue in 3rd-party package
 (see similar reports for autocomplete e.g. #32619 and #32659).

 Closing per TicketClosingReasons/UseSupportChannels.

-- 
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/01070180e213d6db-e40a382f-fa2d-4927-ab82-1abacb9bf80b-00%40eu-central-1.amazonses.com.

Re: [Django] #14092: ImageField should allow SVG

[Django]

#14092: ImageField should allow SVG
-+-
 Reporter:  graeme   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 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 Graeme Pietersz):

 To do it securely we would probably need to add a dependency - there are
 libraries that can do this (e.g. scour) but I do not know which one would
 be best.

 It could be an optional dependency (as PIL/Pillow already is).

-- 
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/01070180e212f1cf-3bd454d0-199a-43e4-9852-3f1a8e640393-00%40eu-central-1.amazonses.com.

Re: [Django] #33721: Add reference to the DE-9IM intersection model.

[Django]

#33721: Add reference to the DE-9IM intersection model.
-+-
 Reporter:  Tobias Schmetzer |Owner:
 Type:   |  Ksenofanex
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  4.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  geos documentation   | 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:"e85ed998d55035b21c37dc4693be3ed94371c8e8" e85ed99]:
 {{{
 #!CommitTicketReference repository=""
 revision="e85ed998d55035b21c37dc4693be3ed94371c8e8"
 [4.0.x] Fixed #33721 -- Added DE-9IM link in GEOS docs.

 Backport of 1be9585d73c50df733eb4d1484651bb8548a1205 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/01070180e1f1a902-3b365b9b-8bb9-4de3-b7ca-de8ae0cbd0d8-00%40eu-central-1.amazonses.com.

Re: [Django] #33721: Add reference to the DE-9IM intersection model.

[Django]

#33721: Add reference to the DE-9IM intersection model.
-+-
 Reporter:  Tobias Schmetzer |Owner:
 Type:   |  Ksenofanex
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  4.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  geos documentation   | 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:"701d78c95ceefeab8cffcc3efb32a65a599ea4fe" 701d78c]:
 {{{
 #!CommitTicketReference repository=""
 revision="701d78c95ceefeab8cffcc3efb32a65a599ea4fe"
 [4.1.x] Fixed #33721 -- Added DE-9IM link in GEOS docs.

 Backport of 1be9585d73c50df733eb4d1484651bb8548a1205 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/01070180e1f14309-99c022f0-f3b0-4263-a4a7-1bb6e4eb6870-00%40eu-central-1.amazonses.com.

Re: [Django] #33721: Add reference to the DE-9IM intersection model.

[Django]

#33721: Add reference to the DE-9IM intersection model.
-+-
 Reporter:  Tobias Schmetzer |Owner:
 Type:   |  Ksenofanex
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  4.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  geos documentation   | 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:"1be9585d73c50df733eb4d1484651bb8548a1205" 1be9585d]:
 {{{
 #!CommitTicketReference repository=""
 revision="1be9585d73c50df733eb4d1484651bb8548a1205"
 Fixed #33721 -- Added DE-9IM link in GEOS docs.
 }}}

-- 
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/01070180e1f02219-c96ee2bc-3d1c-40f5-baaf-3637ac9417c9-00%40eu-central-1.amazonses.com.

Re: [Django] #33725: Admin sidebar’s filter field should not receive focus when sidebar is closed.

[Django]

#33725: Admin sidebar’s filter field should not receive focus when sidebar is
closed.
-+-
 Reporter:  Thibaud Colas|Owner:  Sankalp
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  4.0
 Severity:  Release blocker  |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  keyboard, tab stop |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by Sankalp):

 * 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/01070180e1e66dec-0f52bbba-c8ea-447b-adc0-2322416ef625-00%40eu-central-1.amazonses.com.

Re: [Django] #33725: Admin sidebar’s filter field should not receive focus when sidebar is closed.

[Django]

#33725: Admin sidebar’s filter field should not receive focus when sidebar is
closed.
-+-
 Reporter:  Thibaud Colas|Owner:  Sankalp
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  4.0
 Severity:  Release blocker  |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  keyboard, tab stop |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-

Comment (by Sankalp):

 https://github.com/django/django/pull/15716

-- 
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/01070180e1e336b8-54984137-4fc7-40f2-81a0-2300ff8b3a8b-00%40eu-central-1.amazonses.com.

Re: [Django] #33724: Changing from list to set in `exclude` raises errors, and is not documented.

[Django]

#33724: Changing from list to set in `exclude` raises errors, and is not
documented.
-+-
 Reporter:  אורי |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Carlton Gibson):

 Yes, agreed +1 (since you CC'd me :)

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070180e1b387c3-4c32aba4-2bf0-4060-93a5-a7de6257c4dc-00%40eu-central-1.amazonses.com.

[Django] #33729: [BUG] AutocompleteSelect widget broken after moving from django 2.2 to django 3.2

[Django]

#33729: [BUG] AutocompleteSelect widget broken after moving from django 2.2 to
django 3.2
-+-
   Reporter:  exo|  Owner:  nobody
   Type:  Bug| Status:  new
  Component: |Version:  3.2
  contrib.admin  |
   Severity:  Normal |   Keywords:  AutocompleteSelect
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Hello :) After upgrading `Django` version to `3.2`, widget
 `AutocompleteSelect` that I use in `django` admin panel (to have a drop-
 down from which I can choose an object) **is broken**.

 The error I see is
 {{{
 AttributeError at /admin/question/
 'QuerySet' object has no attribute 'name'

 Request Method: GET
 Request URL:http://localhost:8000/admin/question/
 Django Version: 3.2.13
 Exception Type: AttributeError
 Exception Value:
 'QuerySet' object has no attribute 'name'
 Exception Location: /home/django-app/env/lib/python3.8/site-
 packages/django/contrib/admin/widgets.py, line 412, in build_attrs
 Python Executable:  /home/django-app/env/bin/python3
 Python Version: 3.8.10
 Python Path:
 ['/home/django-app/testsite',
  '/usr/lib/python38.zip',
  '/usr/lib/python3.8',
  '/usr/lib/python3.8/lib-dynload',
  '/home/django-app/env/lib/python3.8/site-packages']
 Server time:Fri, 20 May 2022 10:13:27 +
 Error during template rendering
 In template /home/django-
 app/testsite/polls/templates/admin/question_export.html, error at line 18

 'QuerySet' object has no attribute 'name'
 11
 12  {% block content %}
 13  
 14Select question to export:
 15  
 16  {% csrf_token %}
 17  
 18  {{form.as_table}}
 19  
 20  
 21  
 22  
 23  
 24  
 25  {{form.media}}
 26  {% endblock %}
 27
 }}}
 `AutocompleteSelect` inherits from `AutocompleteMixin`

 When I compare `AutocompleteMixin` for `django 3.2` and `django 2.2`
 
https://github.com/django/django/blob/3.2.13/django/contrib/admin/widgets.py#L410-L412
 
https://github.com/django/django/blob/2.2.7/django/contrib/admin/widgets.py#L411

 I see that they added new attributes
 {{{
 'data-app-label': self.field.model._meta.app_label,
 'data-model-name': self.field.model._meta.model_name,
 'data-field-name': self.field.name,
 }}}
 in `django 3.2`
 but there is no `name` on `self.field` and probably that's why I get this
 error.


 The code looks like this

 view.py
 {{{
 from django.forms import ModelChoiceField
 from django import forms
 from django.contrib import admin
 from django.contrib.admin.widgets import AutocompleteSelect

 class QuestionChoiceField(ModelChoiceField):
 widget = AutocompleteSelect(Question.objects.all(), admin.site)


 class QuestionExportForm(forms.Form):
 question = QuestionChoiceField(queryset=Question.objects.all(),
 required=True)

 def clean_question(self):
 return self.cleaned_data["question"]


 class QuestionExportView(FormView):
 template_name = "admin/question_export.html"
 form_class = QuestionExportForm
 success_url = "/admin/"

 def form_valid(self, form):
 question = form.cleaned_data.get("question")
 return generate_response(question)
 }}}

 models.py
 {{{
 from django.db import models


 class Question(models.Model):
 question_text = models.CharField(max_length=200)
 pub_date = models.DateTimeField('date published')

 }}}
 templates/admin/question_export.html
 {{{
 {% block content %}
 
   Select question to export:
 
 {% csrf_token %}
 
 {{form.as_table}}
 
 
 
 
 
 
 {{form.media}}
 {% endblock %}
 }}}

 How can I approach this issue? Any help would be appreciated :)!

-- 
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

Re: [Django] #33724: Changing from list to set in `exclude` raises errors, and is not documented.

[Django]

#33724: Changing from list to set in `exclude` raises errors, and is not
documented.
-+-
 Reporter:  אורי |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz):

 > All built-in methods do exactly the same number of conversion as before
 1ea7e3157d1f9b4db71e768d75ea57e47dbd49f9 just using set(...) instead of
 list(...).

 The problem is not in Django code, the problem is in user code when you
 have to do smart custom things with exclude, and you don't know if you get
 a list or a set, so you are forced to cast the variable each time before
 starting to manipulate it. If different sort of types in the same category
 (typically iterables) can be seen as a feature, I don't like the
 `list`/`set` potential mix.

 > IMO we can document set as the preferable option, e.g.

 +1, I think this is going in the right direction.

-- 
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/01070180e16f2ffb-588b83bd-75fb-4466-a5c5-b93bba21c3d7-00%40eu-central-1.amazonses.com.

Re: [Django] #33727: Color contrast issues in admin header area

[Django]

#33727: Color contrast issues in admin header area
-+-
 Reporter:  Thibaud Colas|Owner:  Mohammed
 |  Y. Alnajdi
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  color contrast |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  1
-+-
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/01070180e13eff96-be16b693-3bde-4648-9ec5-c0e781cf3461-00%40eu-central-1.amazonses.com.

Re: [Django] #33721: Add reference to the DE-9IM intersection model.

[Django]

#33721: Add reference to the DE-9IM intersection model.
-+-
 Reporter:  Tobias Schmetzer |Owner:
 Type:   |  Ksenofanex
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:  geos documentation   | 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/01070180e1022ad1-7655fbe0-9559-41dc-bfb2-67e1596191b8-00%40eu-central-1.amazonses.com.

Re: [Django] #33727: Color contrast issues in admin header area

[Django]

#33727: Color contrast issues in admin header area
-+-
 Reporter:  Thibaud Colas|Owner:  Mohammed
 |  Y. Alnajdi
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  color contrast |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by Mariusz Felisiak):

 * 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/01070180e0dfb801-57bc331b-f562-4754-b947-0e9263e4bab0-00%40eu-central-1.amazonses.com.

Re: [Django] #33721: Add reference to the DE-9IM intersection model.

[Django]

#33721: Add reference to the DE-9IM intersection model.
-+-
 Reporter:  Tobias Schmetzer |Owner:
 Type:   |  Ksenofanex
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:  geos documentation   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  nobody => Ksenofanex
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/15714 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/01070180e0d7bb8d-4aee1149-fafb-4dfc-8288-4bff05159738-00%40eu-central-1.amazonses.com.

Re: [Django] #33727: Color contrast issues in admin header area

[Django]

#33727: Color contrast issues in admin header area
-+-
 Reporter:  Thibaud Colas|Owner:  Mohammed
 |  Y. Alnajdi
 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:  1|UI/UX:  1
-+-

Comment (by Mohammed Y. Alnajdi):

 https://github.com/django/django/pull/15715

-- 
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/01070180e0d4843c-5ffc7042-6648-4032-9951-77fd811b7400-00%40eu-central-1.amazonses.com.

Re: [Django] #33725: Admin sidebar’s filter field should not receive focus when sidebar is closed.

[Django]

#33725: Admin sidebar’s filter field should not receive focus when sidebar is
closed.
-+-
 Reporter:  Thibaud Colas|Owner:  Sankalp
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  4.0
 Severity:  Release blocker  |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  keyboard, tab stop |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-

Comment (by Mariusz Felisiak):

 Toggling `tabIndex` on `` should do the trick
 here (see a similar solution for links in the sidebar,
 780473d75625d014cbe9b0acdea40b7a5970d5d8.)

-- 
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/01070180e0d4667c-8040871e-f63b-4d6f-9708-d56707a792e2-00%40eu-central-1.amazonses.com.

Re: [Django] #33724: Changing from list to set in `exclude` raises errors, and is not documented.

[Django]

#33724: Changing from list to set in `exclude` raises errors, and is not
documented.
-+-
 Reporter:  אורי |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * cc: Carlton Gibson (added)


Comment:

 Replying to [comment:6 Claude Paroz]:
 > Still I wonder if the performance gain is worth the loss of consistency.
 I wouldn't mind if exclude was defined to always be a set, but having to
 code defensively by expecting list or set is a loss in my point of view.

 All built-in methods do exactly the same number of conversion as before
 1ea7e3157d1f9b4db71e768d75ea57e47dbd49f9 just using `set(...)` instead of
 `list(...)`. IMO we can document `set` as the preferable option, e.g.
 {{{#!diff
 diff --git a/docs/ref/models/instances.txt b/docs/ref/models/instances.txt
 index 9aa9486f4a..8601a19e64 100644
 --- a/docs/ref/models/instances.txt
 +++ b/docs/ref/models/instances.txt
 @@ -252,9 +252,9 @@ The first step ``full_clean()`` performs is to clean
 each individual field.
  .. method:: Model.clean_fields(exclude=None)

  This method will validate all fields on your model. The optional
 ``exclude``
 -argument lets you provide a list of field names to exclude from
 validation. It
 -will raise a :exc:`~django.core.exceptions.ValidationError` if any fields
 fail
 -validation.
 +argument lets you provide a ``set`` of field names to exclude from
 validation.
 +It will raise a :exc:`~django.core.exceptions.ValidationError` if any
 fields
 +fail validation.

  The second step ``full_clean()`` performs is to call
 :meth:`Model.clean()`.
  This method should be overridden to perform custom validation on your
 model.
 @@ -355,8 +355,8 @@ uniqueness constraints defined via
 :attr:`.Field.unique`,
  :attr:`.Field.unique_for_date`, :attr:`.Field.unique_for_month`,
  :attr:`.Field.unique_for_year`, or :attr:`Meta.unique_together
  ` on your model instead of
 individual
 -field values. The optional ``exclude`` argument allows you to provide a
 list of
 -field names to exclude from validation. It will raise a
 +field values. The optional ``exclude`` argument allows you to provide a
 ``set``
 +of field names to exclude from validation. It will raise a
  :exc:`~django.core.exceptions.ValidationError` if any fields fail
 validation.

  :class:`~django.db.models.UniqueConstraint`\s defined in the
 @@ -380,7 +380,7 @@ Finally, ``full_clean()`` will check any other
 constraints on your model.

  This method validates all constraints defined in
  :attr:`Meta.constraints `. The
 -optional ``exclude`` argument allows you to provide a list of field names
 to
 +optional ``exclude`` argument allows you to provide a ``set`` of field
 names to
  exclude from validation. It will raise a
  :exc:`~django.core.exceptions.ValidationError` if any constraints fail
  validation.
 diff --git a/docs/releases/4.1.txt b/docs/releases/4.1.txt
 index 7b922256ec..a1ec53e2ac 100644
 --- a/docs/releases/4.1.txt
 +++ b/docs/releases/4.1.txt
 @@ -561,6 +561,10 @@ Miscellaneous
``URLResolver._callback_strs``, and ``URLPattern.lookup_str()`` are
moved to ``django.contrib.admindocs.utils``.

 +* Custom :meth:`.Model.clean_fields`, :meth:`.Model.validate_unique`, and
 +  :meth:`.Model.validate_constraints` methods now convert an ``exclude``
 +  value to the ``set``.
 +
  .. _deprecated-features-4.1:

 }}}
 Also, passing lists still works, but would not be documented anymore. What
 do you think?

-- 
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/01070180e0ccf889-0512b872-e3c8-4b8b-9a49-b0155b3d1f67-00%40eu-central-1.amazonses.com.

Re: [Django] #33725: Admin sidebar’s filter field should not receive focus when sidebar is closed.

[Django]

#33725: Admin sidebar’s filter field should not receive focus when sidebar is
closed.
-+-
 Reporter:  Thibaud Colas|Owner:  Sankalp
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  4.0
 Severity:  Release blocker  |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  keyboard, tab stop |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by Sankalp):

 * owner:  nobody => Sankalp
 * 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/01070180e0cc6b19-aa004c5d-567c-4a7a-8ef5-00dca401c059-00%40eu-central-1.amazonses.com.

Re: [Django] #33727: Color contrast issues in admin header area

[Django]

#33727: Color contrast issues in admin header area
-+-
 Reporter:  Thibaud Colas|Owner:  Mohammed
 |  Y. Alnajdi
 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:  1|UI/UX:  1
-+-
Changes (by Mohammed Y. Alnajdi):

 * owner:  nobody => Mohammed Y. Alnajdi
 * 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/01070180e0b0de29-2ffcd0f2-c7be-4f08-b1bf-71fc7d9f32c1-00%40eu-central-1.amazonses.com.

Re: [Django] #22078: views.Feed methods cannot be decorated

[Django]

#22078: views.Feed methods cannot be decorated
-+-
 Reporter:  Germano Gabbianelli  |Owner:  Marcelo
 |  Galigniana
 Type:  Bug  |   Status:  assigned
Component:  contrib.syndication  |  Version:  1.6
 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 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/01070180e08cff80-5ed11522-2cfa-4e2e-b7f4-1538c24715c1-00%40eu-central-1.amazonses.com.