Re: [Django] #32045: Document that GenericRelation.remove()/clear() delete objects.

[Django]

#32045: Document that GenericRelation.remove()/clear() delete objects.
-+-
 Reporter:  chgad|Owner:  Craig
 Type:   |  Smith
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  3.1
 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 Mariusz Felisiak):

 Thanks, reviewers will comment on PR, it can take few days.

-- 
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/063.f4c3b5a6feda5b43f126ecec801bb69c%40djangoproject.com.

Re: [Django] #29606: Validate the type of ALLOWED_HOSTS

[Django]

#29606: Validate the type of ALLOWED_HOSTS
-+-
 Reporter:  rafis|Owner:  Octavio
 |  Peri
 Type:  New feature  |   Status:  assigned
Component:  Core (System |  Version:  master
  checks)|
 Severity:  Normal   |   Resolution:
 Keywords:  allowed_hosts| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Octavio Peri):

 * owner:  (none) => Octavio Peri
 * 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/063.d915276e45f4ce240701bcf8c9f5363f%40djangoproject.com.

Re: [Django] #27452: Add Postgres serial field to contrib.postgres

[Django]

#27452: Add Postgres serial field to contrib.postgres
-+-
 Reporter:  Johannes Hoppe   |Owner:
 |  InvalidInterrupt
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by InvalidInterrupt):

 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0


Comment:

 [https://github.com/django/django/pull/13580 New PR for Default
 Expression]

-- 
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/067.2bd3af480ad2b6013d6aa6f9be279b62%40djangoproject.com.

Re: [Django] #32045: Document that GenericRelation.remove()/clear() delete objects.

[Django]

#32045: Document that GenericRelation.remove()/clear() delete objects.
-+-
 Reporter:  chgad|Owner:  Craig
 Type:   |  Smith
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  3.1
 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 Craig Smith):

 Hi Mariusz, I have linked a PR above. It has a couple extra tests. Please
 let me know if there are any further changes that are necessary. For
 instance, should the mention about the difference in {{{remove()}}} and
 {{{clear()}}} on the {{{RelatedManager}}} be made into an
 {{{admonition}}}?

-- 
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/063.293e5ac84b00422f200ae22727950186%40djangoproject.com.

Re: [Django] #29867: Allow cache.get_or_set() to cache a None result

[Django]

#29867: Allow cache.get_or_set() to cache a None result
-+-
 Reporter:  Phill Tornroth   |Owner:  Ahsan
 |  Shafiq
 Type:  Bug  |   Status:  assigned
Component:  Core (Cache system)  |  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jacob Walls):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/11812 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/072.628dc3095b2179260b8d61f6a299eaab%40djangoproject.com.

Re: [Django] #24141: contains() method for QuerySets

[Django]

#24141: contains() method for QuerySets
-+-
 Reporter:  gormster |Owner:  Johan
 |  Schiff
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Simon Charette):

 Looks like the patch still needs improvements regarding invalid model type
 handling and the fact the `_result_cache` scanning is O(n).

-- 
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/066.fcc7f0dca2669959d6b6c65f5158917c%40djangoproject.com.

Re: [Django] #30348: Add superuser_required decorator

[Django]

#30348: Add superuser_required decorator
--+---
 Reporter:  Sultan Iman   |Owner:  Sultan Iman
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+---
Changes (by Jacob Walls):

 * owner:  (none) => Sultan Iman
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/10640 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/069.784031e77ddad310d274b73e049d5ea0%40djangoproject.com.

Re: [Django] #24141: contains() method for QuerySets

[Django]

#24141: contains() method for QuerySets
-+-
 Reporter:  gormster |Owner:  Johan
 |  Schiff
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Jacob Walls):

 * needs_docs:  1 => 0


Comment:

 Author added release notes.

-- 
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/066.86f0c4868c3abebbcaab259b1f2bd973%40djangoproject.com.

Re: [Django] #17990: DISTINCT querysets with RANDOM ordering crash with DatabaseError in Postgres (was: Distinct + Random + Postgres = Bug)

[Django]

#17990: DISTINCT querysets with RANDOM ordering crash with DatabaseError in
Postgres
-+-
 Reporter:  pizzapanther |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 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 Étienne Beaulé):

 * cc: Étienne Beaulé (added)
 * status:  new => closed
 * resolution:   => fixed


Comment:

 Fixed in 0c7633178fa9410f102e4708cef979b873bccb76

-- 
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/070.59bd000c2d88fb2633260bbd7ed6beba%40djangoproject.com.

Re: [Django] #26615: Changing user's email could invalidate password reset tokens

[Django]

#26615: Changing user's email could invalidate password reset tokens
-+-
 Reporter:  Alex Gaynor  |Owner:  Jacob
 Type:   |  Walls
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * 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/062.abb8e7769917f9c594163e9bbd306f6d%40djangoproject.com.

Re: [Django] #32126: Empty Case() annotation crashes when used with GROUP BY

[Django]

#32126: Empty Case() annotation crashes when used with GROUP BY
-+-
 Reporter:  Hannes Ljungberg |Owner:  Hannes
 |  Ljungberg
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * stage:  Accepted => Ready for checkin


Comment:

 Patch LGTM assuming it passes the suite on Oracle.

-- 
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/067.4fcd1fbd0cc4ef54f5a1da23395bc5df%40djangoproject.com.

Re: [Django] #29606: Validate the type of ALLOWED_HOSTS

[Django]

#29606: Validate the type of ALLOWED_HOSTS
--+
 Reporter:  rafis |Owner:  (none)
 Type:  New feature   |   Status:  new
Component:  Core (System checks)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  allowed_hosts | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Mariusz Felisiak):

 * owner:  Tomasz Kluczkowski => (none)
 * status:  assigned => new
 * easy:  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/063.f87515bbc361ccc45120d870f7a079d0%40djangoproject.com.

Re: [Django] #32126: Empty Case() annotation crashes when used with GROUP BY

[Django]

#32126: Empty Case() annotation crashes when used with GROUP BY
-+-
 Reporter:  Hannes Ljungberg |Owner:  Hannes
 |  Ljungberg
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * 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/067.85de29bb58d8d0cfac1892a1e1a2c196%40djangoproject.com.

Re: [Django] #32126: Empty Case() annotation crashes when used with GROUP BY

[Django]

#32126: Empty Case() annotation crashes when used with GROUP BY
-+-
 Reporter:  Hannes Ljungberg |Owner:  Hannes
 |  Ljungberg
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 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 Hannes Ljungberg):

 * has_patch:  0 => 1


Comment:

 PR: https://github.com/django/django/pull/13576

-- 
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/067.6dd1e18e05c1f48a442f4dc4700d7ed7%40djangoproject.com.

[Django] #32126: Empty Case() annotation crashes when used with GROUP BY

[Django]

#32126: Empty Case() annotation crashes when used with GROUP BY
-+-
   Reporter:  Hannes |  Owner:  Hannes Ljungberg
  Ljungberg  |
   Type:  Bug| Status:  assigned
  Component:  Database   |Version:  3.1
  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  |
-+-
 Annotating a queryset with a `Case` without any cases will generate an
 invalid query when used with a `GROUP BY`.

 Example:

 {{{
 qs = (
 CaseTestModel.objects.values('string')
 .annotate(test=Case(output_field=IntegerField()),
 integer_sum=Sum('integer'))
 .order_by('string')
 )
 }}}

 Executing this queryset generates the following SQL:

 {{{
 SELECT "expressions_case_casetestmodel"."string", NULL AS "test",
 SUM("expressions_case_casetestmodel"."integer") AS "integer_sum" FROM
 "expressions_case_casetestmodel" GROUP BY
 "expressions_case_casetestmodel"."string", NULL ORDER BY
 "expressions_case_casetestmodel"."string" ASC
 }}}

 Causing the following error:

 {{{
 django.db.utils.ProgrammingError: non-integer constant in GROUP BY
 LINE 1: ...OUP BY "expressions_case_casetestmodel"."string", NULL ORDER...
 }}}

 The  `Case` annotation should be excluded from the `GROUP BY` if it
 contains no cases.

-- 
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/052.e50dacd9e9c5993ddae7a19947c03a53%40djangoproject.com.

Re: [Django] #26615: Changing user's email could invalidate password reset tokens

[Django]

#26615: Changing user's email could invalidate password reset tokens
-+-
 Reporter:  Alex Gaynor  |Owner:  Jacob
 Type:   |  Walls
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jacob Walls):

 * needs_better_patch:  1 => 0
 * needs_tests:  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/062.b56e325a24579d60861bc24fac1269c9%40djangoproject.com.

Re: [Django] #32119: Broken admin interface after 3.1 update

[Django]

#32119: Broken admin interface after 3.1 update
---+--
 Reporter:  Zvi Baratz |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  3.1
 Severity:  Normal |   Resolution:  duplicate
 Keywords:  Admin CSS  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Zvi Baratz):

 Unfortunately, I already tried both to force-refresh and manually clear
 the cache. I also validated the relevant settings:

 {{{
 MIDDLEWARE = [
 "whitenoise.middleware.WhiteNoiseMiddleware",
 "django.contrib.sessions.middleware.SessionMiddleware",
 "corsheaders.middleware.CorsMiddleware",
 "django.middleware.common.CommonMiddleware",
 "django.middleware.csrf.CsrfViewMiddleware",
 "django.contrib.auth.middleware.AuthenticationMiddleware",
 "django.contrib.messages.middleware.MessageMiddleware",
 "django.middleware.clickjacking.XFrameOptionsMiddleware",
 ]

 TEMPLATES = [
 {
 "BACKEND": "django.template.backends.django.DjangoTemplates",
 "DIRS": [os.path.join(BASE_DIR, "templates")],
 "APP_DIRS": True,
 "OPTIONS": {
 "context_processors": [
 "django.template.context_processors.debug",
 "django.template.context_processors.request",
 "django.contrib.auth.context_processors.auth",
 "django.contrib.messages.context_processors.messages",
 "django.template.context_processors.media",
 ]
 },
 }
 ]
 }}}
 As far as I understand everything seems to be OK but I'm still getting the
 same result.

-- 
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/067.fd1265c0ad6226c579a5fe218f47a22d%40djangoproject.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:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 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
-+-
Description changed by Volodymyr:

Old description:

> HTML5 introduces a support for {{{}}} '''HTML5''' elements for
> suggestions in '''input''' tag
>
> To do this in Django currently, you have to do something like:
>
> '''django/forms/widgets/datalist.html'''
> {{{
> {% include "django/forms/widgets/input.html" %}
>  "django/forms/widgets/attrs.html" %}>{% for group_name, group_choices,
> group_index in widget.optgroups %}{% if group_name %}
>   {% endif %}{% for option in
> group_choices %}
>   {% include option.template_name with widget=option %}{% endfor %}{% if
> group_name %}
>   {% endif %}{% endfor %}
> 
> }}}
>
> '''django/forms/widgets/datalist_option.html'''
> {{{
>  "django/forms/widgets/attrs.html" %}>
> }}}
>
> '''django/forms/widgets.py'''
> {{{#!python
> class Datalist(Select):
> input_type = 'text'
> template_name = 'django/forms/widgets/datalist.html'
> option_template_name = 'django/forms/widgets/datalist_option.html'
> add_id_index = False
> checked_attribute = {'selected': True}
> option_inherits_attrs = False
> }}}
>
> '''django/forms/fields.py'''
> {{{#!python
> class DatalistField(ChoiceField):
> widget = Datalist
> default_error_messages = {
> 'invalid_choice': _('Select a valid choice. %(value)s is not one
> of the available choices.'),
> }
>
> def __init__(self, *, choices='', **kwargs):
> super().__init__(**kwargs)
> self.choices = choices
> }}}

New description:

 HTML5 introduces a support for {{{}}} '''HTML5''' elements for
 suggestions in '''input''' tag

 To do this in Django currently, you have to do something like:

 '''django/forms/widgets/datalist.html'''
 {{{
 {% include "django/forms/widgets/input.html" %}
 {% for group_name, group_choices, group_index in widget.optgroups %}{%
 if group_name %}
   {% endif %}{% for option in
 group_choices %}
   {% include option.template_name with widget=option %}{% endfor %}{% if
 group_name %}
   {% endif %}{% endfor %}
 
 }}}

 '''django/forms/widgets/datalist_option.html'''
 {{{
 
 }}}

 '''django/forms/widgets.py'''
 {{{#!python
 class Datalist(Select):
 input_type = 'text'
 template_name = 'django/forms/widgets/datalist.html'
 option_template_name = 'django/forms/widgets/datalist_option.html'
 add_id_index = False
 checked_attribute = {'selected': True}
 option_inherits_attrs = False
 }}}

 '''django/forms/fields.py'''
 {{{#!python
 class DatalistField(ChoiceField):
 widget = Datalist
 default_error_messages = {
 'invalid_choice': _('Select a valid choice. %(value)s is not one
 of the available choices.'),
 }

 def __init__(self, *, choices='', **kwargs):
 super().__init__(**kwargs)
 self.choices = choices
 }}}

--

-- 
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/064.99868a9da4c6bbe420020dea3c956075%40djangoproject.com.

[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| Status:  new
  feature|
  Component:  Forms  |Version:  master
   Severity:  Normal |   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  |
-+-
 HTML5 introduces a support for {{{}}} '''HTML5''' elements for
 suggestions in '''input''' tag

 To do this in Django currently, you have to do something like:

 '''django/forms/widgets/datalist.html'''
 {{{
 {% include "django/forms/widgets/input.html" %}
 {% for group_name, group_choices,
 group_index in widget.optgroups %}{% if group_name %}
   {% endif %}{% for option in
 group_choices %}
   {% include option.template_name with widget=option %}{% endfor %}{% if
 group_name %}
   {% endif %}{% endfor %}
 
 }}}

 '''django/forms/widgets/datalist_option.html'''
 {{{
 
 }}}

 '''django/forms/widgets.py'''
 {{{#!python
 class Datalist(Select):
 input_type = 'text'
 template_name = 'django/forms/widgets/datalist.html'
 option_template_name = 'django/forms/widgets/datalist_option.html'
 add_id_index = False
 checked_attribute = {'selected': True}
 option_inherits_attrs = False
 }}}

 '''django/forms/fields.py'''
 {{{#!python
 class DatalistField(ChoiceField):
 widget = Datalist
 default_error_messages = {
 'invalid_choice': _('Select a valid choice. %(value)s is not one
 of the available choices.'),
 }

 def __init__(self, *, choices='', **kwargs):
 super().__init__(**kwargs)
 self.choices = choices
 }}}

-- 
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/049.53cf9e75f234d99c1b00089331e40cc9%40djangoproject.com.

Re: [Django] #29122: Add a better font for Persian/Farsi to the admin

[Django]

#29122: Add a better font for Persian/Farsi to the admin
-+-
 Reporter:  Mohammad Hossein |Owner:  SaNjU
  Mojtahedi  |  Saini
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  Persian, font,   | Triage Stage:
  Farsi  |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by SaNjU Saini):

 * owner:  (none) => SaNjU Saini
 * 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/065.46a3c3135d32f267519f4bce2d72bfc9%40djangoproject.com.

Re: [Django] #26615: Changing user's email could invalidate password reset tokens

[Django]

#26615: Changing user's email could invalidate password reset tokens
-+-
 Reporter:  Alex Gaynor  |Owner:  Jacob
 Type:   |  Walls
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1
 * needs_tests:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.66219b3ce852383f03425e1771c9f156%40djangoproject.com.

Re: [Django] #26962: docs: Missing Information about Transaction in Operations (migrations)

[Django]

#26962: docs: Missing Information about Transaction in Operations (migrations)
-+-
 Reporter:  Thomas Güttler   |Owner:  Caio
 Type:   |  Ariede
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Caio Ariede):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/13567 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/065.1bfa97c9f63d5491938451decab3b734%40djangoproject.com.

Re: [Django] #32124: Allow individual views to opt-out of APPEND_SLASH behaviour.

[Django]

#32124: Allow individual views to opt-out of APPEND_SLASH behaviour.
+--
 Reporter:  Carlton Gibson  |Owner:  Carlton Gibson
 Type:  New feature |   Status:  assigned
Component:  HTTP handling   |  Version:  3.1
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Carlton Gibson):

 >  I would use `should_append_slash`

 No problem. I had in mind `do_not_call_in_templates` (but, looking it up,
 it doesn't have an underscore.)

-- 
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/071.1473d04998d19b1ef5419ad7aa72a5fa%40djangoproject.com.

Re: [Django] #32124: Allow individual views to opt-out of APPEND_SLASH behaviour.

[Django]

#32124: Allow individual views to opt-out of APPEND_SLASH behaviour.
+--
 Reporter:  Carlton Gibson  |Owner:  Carlton Gibson
 Type:  New feature |   Status:  assigned
Component:  HTTP handling   |  Version:  3.1
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by Mariusz Felisiak):

 * stage:  Unreviewed => Accepted


Comment:

 Agreed. I would use `should_append_slash` (without a leading underscore)
 and probably add and document only a view decorator (similar to
 `csrf_exempt()`).

-- 
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/071.ffbb84785e3d77dee6c9985f9a7f1240%40djangoproject.com.

Re: [Django] #32046: Add a postgres operation to create collations.

[Django]

#32046: Add a postgres operation to create collations.
-+-
 Reporter:  Tom Carrick  |Owner:  Tom
 |  Carrick
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * 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/065.f67793831914ba3b05bf010cbd94d25b%40djangoproject.com.

Re: [Django] #32124: Allow individual views to opt-out of APPEND_SLASH behaviour.

[Django]

#32124: Allow individual views to opt-out of APPEND_SLASH behaviour.
+--
 Reporter:  Carlton Gibson  |Owner:  Carlton Gibson
 Type:  New feature |   Status:  assigned
Component:  HTTP handling   |  Version:  3.1
 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 Carlton Gibson):

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


Comment:

 [https://github.com/django/django/pull/13575 PR]

 Related to #31747

-- 
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/071.2f7b59fbe1347169c02eaee62fcc01fa%40djangoproject.com.

[Django] #32124: Allow individual views to opt-out of APPEND_SLASH behaviour.

[Django]

#32124: Allow individual views to opt-out of APPEND_SLASH behaviour.
--+
   Reporter:  Carlton Gibson  |  Owner:  nobody
   Type:  New feature | Status:  new
  Component:  HTTP handling   |Version:  3.1
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
 The URL normalisation given by APPEND_SLASH is useful.

 I may wish to retain that but also have a sensitive view that opts-out of
 that behavior, to avoid it being revealed in a potential URL enumeration.

 I propose adjusting `CommonMiddleware` to detect a `_should_append_slash`
 boolean attribute on the view itself, to allow such an opt-out.

-- 
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/056.99cea0b6dbf7db3fe76238ae83554a84%40djangoproject.com.

Re: [Django] #25370: Error display when makemigrations' field serializing fails with ValueError

[Django]

#25370: Error display when makemigrations' field serializing fails with 
ValueError
-+-
 Reporter:  torstenrudolf|Owner:  Tameesh
 Type:   |  Biswas
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Craig Smith):

 [https://github.com/django/django/pull/13570/ 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/071.e8badb091bc758f17c2632910b7e9706%40djangoproject.com.

Re: [Django] #32109: Cannot add content to admin sidebar without breaking layout

[Django]

#32109: Cannot add content to admin sidebar without breaking layout
-+-
 Reporter:  Ben Davis|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  3.1
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  admin sidebar| Triage Stage:
  template   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Carlton Gibson):

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


Comment:

 I'm going to close as wontfix for the moment. Go with Option 1 ''Just use
 CSS and a clearing div to put it in the right place.''
 Happy to discuss more if you (or anyone wants to follow up)
 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/068.60039d91f24930aede0c57b538213fef%40djangoproject.com.

Re: [Django] #32114: Workaround for subtest issue with parallel test runner

[Django]

#32114: Workaround for subtest issue with parallel test runner
-+-
 Reporter:  Jordan Ephron|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Testing framework|  Version:  3.1
 Severity:  Normal   |   Resolution:
 Keywords:  Test subtest | Triage Stage:  Accepted
  parallel   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * stage:  Unreviewed => Accepted


Comment:

 HI Jordan. Thanks for the report.

 Sounds like it's definitely worth looking at a patch. It would be a nice
 improvement if there aren't any issues.
 Would you be able to prepare a PR?

 Ref also #27301 (and loosely #29023)

-- 
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/065.70d78a8c096ccd07a24ff334ffab9a9b%40djangoproject.com.