[Django] #31179: Using the "forgot password" mechanism doesn't invalidate other sessions

[Django]

#31179: Using the "forgot password" mechanism doesn't invalidate other sessions
+
   Reporter:  Mike Lissner  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  contrib.auth  |Version:  master
   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 |
+
 (I don't think this is enough of a vuln to not file publicly, since no way
 to really take advantage of it.)


 We just received a vulnerability report that when a user learns that their
 account has been hijacked, forgets their password, and uses the "Forgot
 Password" link, Django doesn't invalidate the hijacked cookies, despite
 the user just changing their password.

 Django *does* invalidate cookies when passwords are reset via other
 mechanisms, but not when they're done this way.

 I haven't tested this, but I think a one-line patch could be added here:

 
https://github.com/django/django/blob/master/django/contrib/auth/views.py#L300-L305

 I *think* we just need to add:


 {{{
 update_session_auth_hash(self.request, form.user)
 }}}


 And that might do it?

-- 
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/051.07e55ee7a2ff1094862f980ac51f489e%40djangoproject.com.

[Django] #31178: Filing a new bug when you're logged in is *extremely* difficult

[Django]

#31178: Filing a new bug when you're logged in is *extremely* difficult
-+
   Reporter:  Mike Lissner   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Uncategorized  |Version:
   Severity:  Normal |   Keywords:  trak
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 I just spent ten minutes trying to figure out where the "New Ticket"
 button is. Alas, it only shows up if you're logged in and I didn't realize
 I wasn't logged in.

 There's a lot of documentation about how to file new bugs, but at a skim
 it just talks about things to do first, how to handle security bugs, etc.
 Where's the darned link‽ :)

 If there's a way to add a "New Ticket" link that redirects you to the
 login page, that'd be very helpful.

-- 
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/051.069af195b4d846566fafa30912f8bb33%40djangoproject.com.

Re: [Django] #31177: Use "raise from" where appropriate

[Django]

#31177: Use "raise from" where appropriate
-+-
 Reporter:  Ram Rachum   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  3.0
 Severity:  Normal   |   Resolution:  wontfix
 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 Shai Berger):

 * cc: Shai Berger (added)
 * status:  new => closed
 * resolution:   => wontfix


Comment:

 Hi Ram,

 I appreciate the good intentions here. However, unlike #31166 which was a
 local modification, what you're suggesting here is basically a code-style
 policy change. It is inappropriate to do something like that without a
 discussion on the DevelopersMailingList, so I am closing this with wontfix
 -- which essentially just means "you need to convince people about this,
 and it should not progress until you do".

-- 
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.c0ba93af66cd5004d277ce3e9d1bb65e%40djangoproject.com.

Re: [Django] #31177: Use "raise from" where appropriate

[Django]

#31177: Use "raise from" where appropriate
-+-
 Reporter:  Ram Rachum   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  3.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
-+-
Description changed by Ram Rachum:

Old description:

> Following #31166 , I made a regex search to find 90% of places where we
> use "raise" and should use "raise from".
>
> If this is too big for one PR, I could split it to smaller chunks.

New description:

 Following #31166 , I made a regex search to find 90% of places where we
 use "raise" and should use "raise from".

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

 If this is too big for one PR, I could split it to smaller chunks.

--

-- 
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.0da07135625db281922b3e92deffce08%40djangoproject.com.

[Django] #31177: Use "raise from" where appropriate

[Django]

#31177: Use "raise from" where appropriate
+
   Reporter:  Ram Rachum|  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Core (Other)  |Version:  3.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 |
+
 Following #31166 , I made a regex search to find 90% of places where we
 use "raise" and should use "raise from".

 If this is too big for one PR, I could split it to smaller chunks.

-- 
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.6b58cf45d5b449847eeea7fb0db3e8fd%40djangoproject.com.

[Django] #31176: `manage.py migrate` should wrap all migrations into a single transaction

[Django]

#31176: `manage.py migrate` should wrap all migrations into a single transaction
-+-
   Reporter:  Andrew |  Owner:  nobody
  Badr   |
   Type: | Status:  new
  Cleanup/optimization   |
  Component:  Database   |Version:  3.0
  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  |
-+-
 Currently, `manage.py migrate` executes each migration in turn within its
 own transaction. This can break things in the following situation:
 1. Attempt to deploy a change that includes multiple unapplied migrations
 2. Some of the migrations get applied, then one fails (like a check
 constraint)
 3. Code deploy is rolled back, but database is left in an inconsistent
 state.

 To avoid this problem, if the user is attempting to apply a set of
 migrations all at once, they should all be wrapped into a single
 transaction.

-- 
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/053.e006b98dad0ae01a91adec58f0174893%40djangoproject.com.

Re: [Django] #30752: Allow using ExceptionReporter subclass in django.views.debug.technical_500_response

[Django]

#30752: Allow using ExceptionReporter subclass in
django.views.debug.technical_500_response
-+-
 Reporter:  Carlton Gibson   |Owner:  Pavel
 |  Lysak
 Type:  New feature  |   Status:  closed
Component:  Error reporting  |  Version:  master
 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
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"56071826bbb741b6ca04aa517a26acd335fc24d7" 56071826]:
 {{{
 #!CommitTicketReference repository=""
 revision="56071826bbb741b6ca04aa517a26acd335fc24d7"
 Refs #30752 -- Doc'd error reporting related optional request attributes.
 }}}

-- 
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.890194954a2d62d52140461e4762b984%40djangoproject.com.

Re: [Django] #21961: Add support for database-level cascading options

[Django]

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Nick
 |  Stefan
 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:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * 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/061.221d042d3b4018b57ce0723a2abe50d2%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

[Django]

#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Ahsan
 Type:   |  Shafiq
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by felixxm):

 * needs_docs:  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/066.047659a75d336be2beaea4d58865e6dd%40djangoproject.com.

Re: [Django] #31175: Remove newline in Textarea widget. (was: Extra spaces in textarea widget template)

[Django]

#31175: Remove newline in Textarea widget.
-+-
 Reporter:   |Owner:  nobody
  python2and3developer   |
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  template, forms, | Triage Stage:
  textarea   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  new => closed
 * resolution:   => wontfix
 * version:  3.0 => master
 * type:  Bug => Cleanup/optimization


Old description:

> The template of textarea widget has some extra spaces that are added
> directily inside the textarea when its rendering on the browser.
> https://github.com/django/django/blob/master/django/forms/templates/django/forms/widgets/textarea.html
>
> {{{
>  "django/forms/widgets/attrs.html" %}>
> {% if widget.value %}{{ widget.value }}{% endif %}
> }}}
>
> The porposal is to change that to this (only one line, instead of two):
> {{{
>  "django/forms/widgets/attrs.html" %}>{% if widget.value %}{{ widget.value
> }}{% endif %}
> }}}

New description:

 The template of textarea widget has some extra spaces that are added
 directly inside the textarea when its rendering on the browser.
 
https://github.com/django/django/blob/master/django/forms/templates/django/forms/widgets/textarea.html

 {{{
 
 {% if widget.value %}{{ widget.value }}{% endif %}
 }}}

 The proposal is to change that to this (only one line, instead of two):
 {{{
 {% if widget.value %}{{ widget.value
 }}{% endif %}
 }}}

--

Comment:

 This newline is required to fix #8627.

-- 
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/078.4e21a36e36a1b650c13a3652240a637e%40djangoproject.com.

[Django] #31175: Extra spaces in textarea widget template

[Django]

#31175: Extra spaces in textarea widget template
-+-
   Reporter: |  Owner:  nobody
  python2and3developer   |
   Type: | Status:  new
  Uncategorized  |
  Component:  Forms  |Version:  3.0
   Severity:  Normal |   Keywords:  template, forms,
   Triage Stage: |  textarea
  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 The template of textarea widget has some extra spaces that are added
 directily inside the textarea when its rendering on the browser.
 
https://github.com/django/django/blob/master/django/forms/templates/django/forms/widgets/textarea.html

 {{{
 
 {% if widget.value %}{{ widget.value }}{% endif %}
 }}}

 The porposal is to change that to this (only one line, instead of two):
 {{{
 {% if widget.value %}{{ widget.value
 }}{% endif %}
 }}}

-- 
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.8ab8b65bc91aced11e242fe3b5ee4c16%40djangoproject.com.

Re: [Django] #31175: Extra spaces in textarea widget template

[Django]

#31175: Extra spaces in textarea widget template
-+-
 Reporter:   |Owner:  nobody
  python2and3developer   |
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  3.0
 Severity:  Normal   |   Resolution:
 Keywords:  template, forms, | Triage Stage:
  textarea   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by python2and3developer):

 * type:  Uncategorized => Bug


-- 
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/078.c739cf7a61d841224ee8a1edbd2dd61a%40djangoproject.com.

Re: [Django] #31166: Provide context for ImproperlyConfigured exceptions in URL resolver.

[Django]

#31166: Provide context for ImproperlyConfigured exceptions in URL resolver.
-+-
 Reporter:  Ram Rachum   |Owner:  Ram
 Type:   |  Rachum
  Cleanup/optimization   |   Status:  closed
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"bf3e8227a902ca0828c9a66130064a23d5f75163" bf3e822]:
 {{{
 #!CommitTicketReference repository=""
 revision="bf3e8227a902ca0828c9a66130064a23d5f75163"
 Fixed #31166 -- Used "raise from" when raising ImproperlyConfigured
 exceptions in django.urls.resolvers.

 This change sets the __cause__ attribute to raised exceptions and makes
 small cleanups in error messages.
 }}}

-- 
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.bab80e21c4bf0319bc5b873f7ebb3a7a%40djangoproject.com.

Re: [Django] #29789: Support nested relations in FilteredRelation's condition

[Django]

#29789: Support nested relations in FilteredRelation's condition
-+-
 Reporter:  Thomas Riccardi  |Owner:  Noumbissi
 |  Valere Gille Geovan
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  FilteredRelation | Triage Stage:  Accepted
  nested relations   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/12333 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/073.ca6faffd08b566889f5fe68679f82f00%40djangoproject.com.

Re: [Django] #31166: Provide context for ImproperlyConfigured exceptions in URL resolver.

[Django]

#31166: Provide context for ImproperlyConfigured exceptions in URL resolver.
-+-
 Reporter:  Ram Rachum   |Owner:  Ram
 Type:   |  Rachum
  Cleanup/optimization   |   Status:  assigned
Component:  Core (URLs)  |  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 Shai Berger):

 * cc: Shai Berger (added)
 * 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/064.ac6488463e6d13250e26153aff78ee2d%40djangoproject.com.

Re: [Django] #31173: Testing with PickleSerializer and Mock objects breaks. (was: Testing with PickleSerializer and Mock objects breaks)

[Django]

#31173: Testing with PickleSerializer and Mock objects breaks.
-+-
 Reporter:  Mmadu Manasseh   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.sessions |  Version:  3.0
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  Pickle, Mock,| Triage Stage:
  Session|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  new => closed
 * resolution:   => invalid
 * component:  Testing framework => contrib.sessions


Comment:

 This is a known limitation of `pickle`, and I don't see how we could
 handle this in Django. You can always use [https://github.com/testing-
 cabal/mock/issues/139#issuecomment-122128815 a custom Mock subclass],
 which will work with `pickle`.

-- 
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.a4327f94aeecc744c87560d13043e7c2%40djangoproject.com.

Re: [Django] #27785: Log request.body (or part of it) in the 500 debug content

[Django]

#27785: Log request.body (or part of it) in the 500 debug content
-+-
 Reporter:  Claude Paroz |Owner:  (none)
 Type:  New feature  |   Status:  closed
Component:  Error reporting  |  Version:  master
 Severity:  Normal   |   Resolution:  duplicate
 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):

 Agreed. Alwasy happy to look at these things if there’s a patch in play.
 :)

-- 
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.cf26852de96b652ebfb413c00aaa61f1%40djangoproject.com.

Re: [Django] #31174: The inline original text area can not display full. (was: The inline original text area can not display full)

[Django]

#31174: The inline original text area can not display full.
-+-
 Reporter:  Jian Dai |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  3.0
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  form inline  | Triage Stage:
  original css style |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by felixxm):

 * status:  new => closed
 * resolution:   => invalid
 * component:  Forms => contrib.admin


Comment:

 Thanks for this report, however I cannot reproduce it locally (see
 
[https://code.djangoproject.com/attachment/ticket/31174/Screenshot_20200117_093715.png
 screenshot]) and CSS looks good for me. Changing `height` shouldn't affect
 
[https://code.djangoproject.com/attachment/ticket/31174/%E6%88%AA%E5%B1%8F2020-01-17%E4%B8%8A%E5%8D%8810.53.23.png
 this behavior]. This may be a local font issue, it's hard to tell.

 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/066.0729fb55c1e4295fa2fce54b1b353330%40djangoproject.com.

Re: [Django] #31174: The inline original text area can not display full

[Django]

#31174: The inline original text area can not display full
-+-
 Reporter:  Jian Dai |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  3.0
 Severity:  Normal   |   Resolution:
 Keywords:  form inline  | Triage Stage:
  original css style |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by felixxm):

 * Attachment "Screenshot_20200117_093715.png" added.


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

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

Re: [Django] #31171: Misleading wording in custom template tags docs.

[Django]

#31171: Misleading wording in custom template tags docs.
-+-
 Reporter:  Takayuki Hirayama|Owner:  Takayuki
 Type:   |  Hirayama
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"f0e1a69c99c43a812c647811265b2345dda4ba04" f0e1a69c]:
 {{{
 #!CommitTicketReference repository=""
 revision="f0e1a69c99c43a812c647811265b2345dda4ba04"
 [3.0.x] Fixed #31171 -- Fixed wording in auto-escaping section of custom
 template tags docs.

 Backport of 73563183c2ea92e9ef1d3a1f790a503acc14ade2 from master
 }}}

-- 
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.8188c8542ad61899face0c679d109006%40djangoproject.com.

Re: [Django] #31171: Misleading wording in custom template tags docs.

[Django]

#31171: Misleading wording in custom template tags docs.
-+-
 Reporter:  Takayuki Hirayama|Owner:  Takayuki
 Type:   |  Hirayama
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"73563183c2ea92e9ef1d3a1f790a503acc14ade2" 7356318]:
 {{{
 #!CommitTicketReference repository=""
 revision="73563183c2ea92e9ef1d3a1f790a503acc14ade2"
 Fixed #31171 -- Fixed wording in auto-escaping section of custom template
 tags 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/070.72c4c9874f0d17ab34697c6aaf548f34%40djangoproject.com.

Re: [Django] #31097: StringAgg And ArrayAgg with filtering in subquery generates invalid string_agg() SQL function call

[Django]

#31097: StringAgg And ArrayAgg with filtering in subquery generates invalid
string_agg() SQL function call
-+-
 Reporter:  Laurent Tramoy   |Owner:  David
 |  Wobrock
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  3.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"5b6778b8b98a3999d15ec3560ad605cdd302e23b" 5b6778b8]:
 {{{
 #!CommitTicketReference repository=""
 revision="5b6778b8b98a3999d15ec3560ad605cdd302e23b"
 [3.0.x] Refs #31097 -- Added django.db.models.Q import to contrib.postgres
 aggregates tests.
 }}}

-- 
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.597a6e9cea3089eb6502772267a527d8%40djangoproject.com.