Re: [Django] #32776: Support Array subqueries on PostgreSQL

[Django]

#32776: Support Array subqueries on PostgreSQL
-+-
 Reporter:  Hannes Ljungberg |Owner:  Hannes
 |  Ljungberg
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  dev
 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/067.d49fac2a77fcc315216db9f2063b7977%40djangoproject.com.

Re: [Django] #32905: Add `nonform` CSS class for non form errors in FormSets

[Django]

#32905: Add `nonform` CSS class for non form errors in FormSets
-+-
 Reporter:  Ties Jan Hefting |Owner:  Ties Jan
 |  Hefting
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * type:  Cleanup/optimization => New feature
 * easy:  1 => 0
 * stage:  Unreviewed => Accepted


Comment:

 Seems reasonable (similar to #11776).

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

Re: [Django] #32903: admin page in Google-Chrome does not show the columns like in Firefox or Chrome

[Django]

#32903: admin page in Google-Chrome does not show the columns like in Firefox or
Chrome
---+--
 Reporter:  elnikej|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  3.2
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Mariusz Felisiak):

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


Comment:

 Thanks for the screenshots, however I cannot reproduce this issue. It
 looks like a problem with refreshing CSS files, I don't think that Django
 is at fault. Can you try to use CTRL+F5?

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

Re: [Django] #32899: enhance JSONResponse safe=True kwarg docs

[Django]

#32899: enhance JSONResponse safe=True kwarg docs
-+-
 Reporter:  Thomas Grainger  |Owner:  Hasan
 Type:   |  Ramezani
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1


Comment:

 You've added a note to the docstring, which is fine, but we should also
 add a note to the [https://docs.djangoproject.com/en/3.2/ref/request-
 response/#serializing-non-dictionary-objects warning] in the 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/067.3ec8d67dde3a59f2df2b8556d6d97604%40djangoproject.com.

Re: [Django] #32902: CsrfViewMiddleware.process_response()'s csrf_cookie_needs_reset and csrf_cookie_set logic isn't right

[Django]

#32902: CsrfViewMiddleware.process_response()'s csrf_cookie_needs_reset and
csrf_cookie_set logic isn't right
+--
 Reporter:  Chris Jerdonek  |Owner:  Chris Jerdonek
 Type:  Bug |   Status:  assigned
Component:  CSRF|  Version:  dev
 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 Chris Jerdonek):

 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #28333: Filter and subquery for window expressions

[Django]

#28333: Filter and subquery for window expressions
-+-
 Reporter:  Mads Jensen  |Owner:  (none)
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  window orm filter| Triage Stage:  Accepted
  subquery GSoC  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Alex Scott):

 * cc: Alex Scott (added)


Comment:

 Is there a recommend workaround for not being able to filter on a window
 function result? Can you wrap it somehow manually?

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

Re: [Django] #32899: enhance JSONResponse safe=True kwarg docs

[Django]

#32899: enhance JSONResponse safe=True kwarg docs
-+-
 Reporter:  Thomas Grainger  |Owner:  Hasan
 Type:   |  Ramezani
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  3.2
 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 Hasan Ramezani):

 * owner:  (none) => Hasan Ramezani
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

 I added a small sentence to mention that object response makes the
 expansion of response simpler.

 @Mariusz, I think is about the `safe=True kwarg docs` but you mentioned to
 `enhance the warning`. which warning do you mean?

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

Re: [Django] #32508: Raise proper exceptions instead of using "assert".

[Django]

#32508: Raise proper exceptions instead of using "assert".
-+-
 Reporter:  Adam Johnson |Owner:  Daniyal
 Type:   |  Abbasi
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  dev
 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):

 * owner:  nobody => Daniyal Abbasi
 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1
 * status:  new => assigned


Comment:

 Once [https://github.com/django/django/pull/14173 Daniyal's patch] lands
 for `django.db.models` I think this will be resolved.

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

Re: [Django] #32776: Support Array subqueries on PostgreSQL

[Django]

#32776: Support Array subqueries on PostgreSQL
-+-
 Reporter:  Hannes Ljungberg |Owner:  Hannes
 |  Ljungberg
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  dev
 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 Hannes Ljungberg):

 * needs_better_patch:  1 => 0


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

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

Re: [Django] #32905: Add `nonform` CSS class for non form errors in FormSets

[Django]

#32905: Add `nonform` CSS class for non form errors in FormSets
-+-
 Reporter:  Ties Jan Hefting |Owner:  Ties Jan
 Type:   |  Hefting
  Cleanup/optimization   |   Status:  assigned
Component:  Forms|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Ties Jan Hefting):

 * owner:  nobody => Ties Jan Hefting


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

[Django] #32905: Add `nonform` CSS class for non form errors in FormSets

[Django]

#32905: Add `nonform` CSS class for non form errors in FormSets
+--
   Reporter:  Ties Jan Hefting  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  assigned
  Component:  Forms |Version:  dev
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+--
 Forms add the `nonfield` CSS class for non field errors in ErrorClass
 instances. This is documented in a section on
 [https://docs.djangoproject.com/en/dev/topics/forms/#rendering-form-error-
 messages rendering form error messages]. Similarly, in FormSets I'd expect
 to see the `nonform` CSS class added for non form errors. This would allow
 a custom ErrorClass to make a distinction in form field errors, non field
 errors (forms) and non form errors (FormSets) when rendering error
 messages. Therefore I'd suggest to add this `nonform` CSS class and
 document it for developers to use.

-- 
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/050.e6065d94937dccd395dfd080c63bef78%40djangoproject.com.

Re: [Django] #13217: LocaleMiddleware breaks caching. (Vary: Cookie)

[Django]

#13217: LocaleMiddleware  breaks caching.  (Vary: Cookie)
-+-
 Reporter:  harm |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Uncategorized|  Version:  1.2-beta
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  session accessed | Triage Stage:
  vary cookie|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Jerome Leclanche):

 Replying to [comment:14 Aymeric Augustin]:
 > If you're using `i18n_patterns` (introduced in Django 1.4) and the URL
 contains a language prefix, `get_language_from_request` will select the
 active language without reading the session.
 >
 > So, in practice, this is fixed.

 @Aymeric Augustin -- I believe there's an unhandled edge case if
 i18n_patterns receives ``prefix_default_language=False``: accept-language
 will still be set, even though the language of the page in question is
 static. I can't investigate more right now, and I know that
 ``prefix_default_language`` is fairly new, but leaving this here for
 posterity.

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

Re: [Django] #25264: Misleading list of options available for manage.py commands

[Django]

#25264: Misleading list of options available for manage.py commands
-+-
 Reporter:  Maxime Lorant|Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Management |  Version:  dev
  commands)  |
 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
-+-
Changes (by Edald123):

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


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

Re: [Django] #32903: admin page in Google-Chrome does not show the columns like in Firefox or Chrome

[Django]

#32903: admin page in Google-Chrome does not show the columns like in Firefox or
Chrome
---+--
 Reporter:  elnikej|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  3.2
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by elnikej):

 * Attachment "django32_poll-tutorial_firefox__2021-07-05_OK.png" added.

 Firefox menu in left side is visible

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

Re: [Django] #32903: admin page in Google-Chrome does not show the columns like in Firefox or Chrome

[Django]

#32903: admin page in Google-Chrome does not show the columns like in Firefox or
Chrome
---+--
 Reporter:  elnikej|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  3.2
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by elnikej):

 * Attachment "django32_poll-tutorial_Google-Chrome__2021-07-05_NOK.png"
 added.

 Google-Chrome not visible menu in left side

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

Re: [Django] #32904: Tighten up the regular expression used by parse_time to accept less 'invalid' options.

[Django]

#32904: Tighten up the regular expression used by parse_time to accept less
'invalid' options.
-+-
 Reporter:  Keryn Knight |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Utilities|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Keryn Knight):

 Here, for example, is one which parses into a `datetime.time` but I
 wouldn't really expect it to, and whilst the input is nonsense, doesn't
 cause an error like `ValueError: second must be in 0..59` which ''would''
 match my expectations:
 {{{
 >>> from django.utils.dateparse import parse_time
 >>> parse_time('4:18:101')
 datetime.time(4, 18, 10)
 # captured data was {'hour': '4', 'minute': '18', 'second': '10',
 'microsecond': None}
 }}}

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

Re: [Django] #30420: Do not reload runserver during debugging / request processing

[Django]

#30420: Do not reload runserver during debugging / request processing
-+-
 Reporter:  Daniel Hahler|Owner:  Rohith P
 |  R
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  dev
  commands)  |
 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 Rohith P R):

 * needs_better_patch:  1 => 0


Comment:

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

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

[Django] #32904: Tighten up the regular expression used by parse_time to accept less 'invalid' options.

[Django]

#32904: Tighten up the regular expression used by parse_time to accept less
'invalid' options.
+
   Reporter:  Keryn Knight  |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Utilities |Version:  dev
   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 |
+
 As per discussion in the ticket #32892 and on the Github comments for
 same, currently the `time_re` allows for some variations which it arguably
 shouldn't.

 For the historical record's sake, the current regex is:
 
`(?P\d{1,2}):(?P\d{1,2})(?::(?P\d{1,2})(?:[\.,](?P\d{1,6})\d{0,6})?)?`
 where you can see a whole lot of it ends up optional, and there are some
 ways in which that can be made to accept what we'd probably call 'invalid'
 (though strictly speaking the result is correct for the input portions):

 {{{
 >>> from django.utils.dateparse import parse_time
 >>> parse_time('0:5: ')
 datetime.time(0, 5)
 }}}

 If possible, we should derive examples of which strings might current pass
 and decide which, if any of them, shouldn't be accepted. It's probably
 also fine to leave the whole thing as-is (be liberal in what you accept
 etc) and just add them as necessary to the examples of valid inputs, so in
 future it doesn't come up again beyond "thats just an accepted quirk"

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

Re: [Django] #32901: BaseForm.__getitem__() does unneeded work in the happy path

[Django]

#32901: BaseForm.__getitem__() does unneeded work in the happy path
-+-
 Reporter:  Chris Jerdonek   |Owner:  Chris
 Type:   |  Jerdonek
  Cleanup/optimization   |   Status:  closed
Component:  Forms|  Version:  dev
 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 GitHub ):

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


Comment:

 In [changeset:"edde2a069929c93e37835dc3f7c9a229040058e2" edde2a0]:
 {{{
 #!CommitTicketReference repository=""
 revision="edde2a069929c93e37835dc3f7c9a229040058e2"
 Fixed #32901 -- Optimized BaseForm.__getitem__().
 }}}

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

Re: [Django] #32508: Raise proper exceptions instead of using "assert".

[Django]

#32508: Raise proper exceptions instead of using "assert".
--+
 Reporter:  Adam Johnson  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Mariusz Felisiak ):

 In [changeset:"2231429991ee17987e3897238f9e5551c5c7ab2e" 22314299]:
 {{{
 #!CommitTicketReference repository=""
 revision="2231429991ee17987e3897238f9e5551c5c7ab2e"
 Refs #32508 -- Raised ImproperlyConfigured/TypeError instead of using
 "assert".
 }}}

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

Re: [Django] #32903: admin page in Google-Chrome does not show the columns like in Firefox or Chrome

[Django]

#32903: admin page in Google-Chrome does not show the columns like in Firefox or
Chrome
---+--
 Reporter:  elnikej|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  3.2
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by Tim Graham):

 It seems doubtful that Django is at fault but could you attach a
 screenshot that demonstrates the issue? I took a quick look and don't see
 a difference between Firefox and Chrome.

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

[Django] #32903: admin page in Google-Chrome does not show the columns like in Firefox or Chrome

[Django]

#32903: admin page in Google-Chrome does not show the columns like in Firefox or
Chrome
-+
   Reporter:  elnikej|  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.admin  |Version:  3.2
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 using Google Chrome // 91.0.4472.114 (Official Build) (64-bit) the admin
 page (/admin/polls/question/) from Tutorial looks very strange as the left
 column is not visible. (In other projects with filter the filters on the
 right side are also not visible).
 - Firefox (89.0.2 (64-bit)) looks good
 - Chromium (Version 91.0.4472.114 (Official Build) snap (64-bit)) looks
 good
 - I using Ubuntu 18.04.

-- 
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/050.aa4c7b30edc9bc22baa02e1359d4b0ba%40djangoproject.com.

Re: [Django] #32901: BaseForm.__getitem__() does unneeded work in the happy path

[Django]

#32901: BaseForm.__getitem__() does unneeded work in the happy path
-+-
 Reporter:  Chris Jerdonek   |Owner:  Chris
 Type:   |  Jerdonek
  Cleanup/optimization   |   Status:  assigned
Component:  Forms|  Version:  dev
 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/067.06cec32018e8f8faba0ffb07e7aee116%40djangoproject.com.

Re: [Django] #32901: BaseForm.__getitem__() does unneeded work in the happy path

[Django]

#32901: BaseForm.__getitem__() does unneeded work in the happy path
-+-
 Reporter:  Chris Jerdonek   |Owner:  Chris
 Type:   |  Jerdonek
  Cleanup/optimization   |   Status:  assigned
Component:  Forms|  Version:  dev
 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 Chris Jerdonek):

 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #30420: Do not reload runserver during debugging / request processing

[Django]

#30420: Do not reload runserver during debugging / request processing
-+-
 Reporter:  Daniel Hahler|Owner:  Rohith P
 |  R
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  dev
  commands)  |
 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 Rohith P R):

 * owner:  Kim Namjun => Rohith P R


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

Re: [Django] #28574: Add a QuerySet.explain() method

[Django]

#28574: Add a QuerySet.explain() method
-+-
 Reporter:  Tom Forbes   |Owner:  Tom
 |  Forbes
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 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
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"b3b04ad2111f1e3eb0640cd5d51d4391655317ce" b3b04ad2]:
 {{{
 #!CommitTicketReference repository=""
 revision="b3b04ad2111f1e3eb0640cd5d51d4391655317ce"
 Refs #28574 -- Added test for XML format output to Queryset.explain().
 }}}

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

Re: [Django] #32226: QuerySet.explain(format='json') outputs repr'd JSON on PostgreSQL

[Django]

#32226: QuerySet.explain(format='json') outputs repr'd JSON on PostgreSQL
-+-
 Reporter:  Adam Johnson |Owner:  Wu
 |  Haotian
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 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:"aba9c2de669dcc0278c7ffde7981be91801be00b" aba9c2de]:
 {{{
 #!CommitTicketReference repository=""
 revision="aba9c2de669dcc0278c7ffde7981be91801be00b"
 Fixed #32226 -- Fixed JSON format of QuerySet.explain() on PostgreSQL.
 }}}

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

Re: [Django] #32776: Support Array subqueries on PostgreSQL

[Django]

#32776: Support Array subqueries on PostgreSQL
-+-
 Reporter:  Hannes Ljungberg |Owner:  Hannes
 |  Ljungberg
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  dev
 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/067.6aef51ba9275d5bd467453a7d3cf31c9%40djangoproject.com.

Re: [Django] #32891: runserver serve static files cached in debug

[Django]

#32891: runserver serve static files cached in debug
-+-
 Reporter:  TZanke   |Owner:  TZanke
 Type:  Bug  |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Wu Haotian):

 * owner:  nobody => TZanke
 * 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/064.7b90ec29d858e1b443a6af5f31a2cd08%40djangoproject.com.

Re: [Django] #24121: Provide a better repr() experience

[Django]

#24121: Provide a better repr() experience
--+
 Reporter:  Keryn Knight  |Owner:  Nicolás Restrepo
 Type:  New feature   |   Status:  assigned
Component:  Core (Other)  |  Version:  dev
 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
--+
Description changed by Mariusz Felisiak:

Old description:

> For a long time, Django has shipped with the debug 500 handler, which
> defaults to a view where "local vars" for every stack frame can be
> expanded and inspected to see the internal state at the various points in
> the stack trace.
>
> Between that renderer, the heavy usage of `django-debug-toolbar`, which
> ships with a template context inspector, and my preference throwing `pdb`
> everywhere, there is a notable lack of a good `repr()` experience in much
> of Django, both in debugging public API (that is, the bits a user will
> use and encounter), and internals that might be exposed, or could
> otherwise be served better by having a repr that says something more than
> it's address/id.
>
> A couple of previous tickets have addressed this in minor, one off ways -
> #23167, #22906, #22531 - but as I've begun collecting places they could
> supply useful info as I spot them in my stuff, they've become a
> hodgepodge across a number of modules.
>
> For example, a couple I've got implemented:
> {{{
> 
>
>  loadname=admin/change_list.html>
>
> 
> }}}
> All of which, IMHO, provide a more useful context in which to evaluate
> state.
>
> The branch I have implemented my reprs in is in no way merge ready yet,
> partially because there's no tests, and it'd need rebasing & squashing,
> but also because there are some parts I'd like to see reprs on but
> haven't landed on a good way to do so.
> An example being the concept of a `Loader`, which currently has no repr()
> and thus shows up as `` which at least
> tells us which loader is being referenced. Given the convention so far
> for reprs() is just the class name (rather than module + class), the fact
> all Loaders (and now Engines) all share the same class name means in
> exposing more useful internal state we lose knowledge of the loader in
> question's module namespace.
>
> As I write this, I've got at least rudimentary (as in, it was possibly to
> replace the 0x... with at least one object-state variable) reprs for:
> * ~~`StaticNode`~~ added in e6406853c326ea9210d07766138d2b193c6d1fba
> * ~~`BlockTranslateNode`~~ added in
> 66ed03e7c9ae4cd754aa918c6f4c9227cf424141
> * ~~`URLNode`~~ added in d3ecef26b9fda02b88f925a800ae38dd5873c878
> * ~~`Token`~~ added in 179ee13eb37348cd87169a198aec18fedccc8668
> * ~~`Lexer`~~ added in 179ee13eb37348cd87169a198aec18fedccc8668
> * ~~`Parser`~~ added in 179ee13eb37348cd87169a198aec18fedccc8668
> * ~~`FilterExpression`~~ added in
> 179ee13eb37348cd87169a198aec18fedccc8668
> * ~~`MiddlewareMixin`, `RedirectFallbackMiddleware`, `MessageMiddleware`,
> `RemoteUserMiddleware`, `CsrfViewMiddleware`~~ added in
> dc86a25a677d05703e0bb021b178e44412cea7e9
> * ~~`Col`~~ added in 7171bf755b0c4be85ddbcc164eaf87164c131021
> * ~~`Lookup`~~ added in d3d95d645fc9f36355d27598475612de43587db1
> * `BaseDatabaseWrapper` [https://github.com/django/django/pull/14111 PR]
> * `SQLCompiler` [https://github.com/django/django/pull/14111 PR]
> * `JoinPromoter` [https://github.com/django/django/pull/14111 PR]
> * ~~`HttpResponse`, `HttpResponseRedirect`, `HttpResponseNotAllowed`~~
> added in c96f11257baf43188ff9daeddab3221992925c85
> * ~~`LazySettings`, `Settings`, and `UserSettingsHolder`~~ added in
> 9c40f01a66bd15457e10a0bbf28c803968b5dabb
> * ~~`GeoIP2`~~ added in d4b10a725614322769a419180039771634a06571
> * ~~`PermWrapper`~~ added in 22da686ca93e99f8091334f66d7199bc29b85c83
> * ~~`BaseStorage`~~ added in 7dd502b0e1e7d3e7fa2c5a2d54bbc926dbcf5f92
> * ~~`ChangeList`~~ added in 7dd502b0e1e7d3e7fa2c5a2d54bbc926dbcf5f92
> * ~~`AdminForm`~~ added in 66ed03e7c9ae4cd754aa918c6f4c9227cf424141
> * ~~`SimpleTemplateResponse`~~ added in
> c96f11257baf43188ff9daeddab3221992925c85
> * ~~`TemplateResponse`~~ added in
> c96f11257baf43188ff9daeddab3221992925c85
> * `AdminSite` [https://github.com/django/django/pull/14417 PR]
> * `ModelAdmin` [https://github.com/django/django/pull/14417 PR]
> * ~~`Origin`~~ added in 4f4f770f77c5d720484c0a71f6a19b9affcc7e28
> * ~~`Template`~~ added in 4f4f770f77c5d720484c0a71f6a19b9affcc7e28
> * ~~`BlockContext`~~ added in 66ed03e7c9ae4cd754aa918c6f4c9227cf424141
> * ~~`IncludeNode`~~ added in 66ed03e7c9ae4cd754aa918c6f4c9227cf424141
> * ~~`Engine`~~ added in 

Re: [Django] #24121: Provide a better repr() experience

[Django]

#24121: Provide a better repr() experience
--+
 Reporter:  Keryn Knight  |Owner:  Nicolás Restrepo
 Type:  New feature   |   Status:  assigned
Component:  Core (Other)  |  Version:  dev
 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 Mariusz Felisiak ):

 In [changeset:"e4da3654367cd5f5c06ab109ece0042631faaa02" e4da3654]:
 {{{
 #!CommitTicketReference repository=""
 revision="e4da3654367cd5f5c06ab109ece0042631faaa02"
 Refs #24121 -- Added __repr__() to AdminSite, DefaultAdminSite, and
 ModelAdmin.

 Thanks tlebrize for the initial patch.
 }}}

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

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