Re: [Django] #32372: Improve consistency in "Related objects reference" docs.

[Django]

#32372: Improve consistency in "Related objects reference" docs.
-+-
 Reporter:  Jack Aitken  |Owner:  Jack
 Type:   |  Aitken
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  3.1
 Severity:  Normal   |   Resolution:  fixed
 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 ):

 In [changeset:"18adc89e50dca63b664a721ea9790279524b6db3" 18adc89e]:
 {{{
 #!CommitTicketReference repository=""
 revision="18adc89e50dca63b664a721ea9790279524b6db3"
 [3.1.x] Refs #32372 -- Updated manager name in related objects reference
 docs.

 Follow up to 725c549ae7a34d83447201da7190f8d71c7fc2fc.
 Backport of 2b4b6c8af0aae8785bc1347cf1be2e8e70fd5ff3 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/068.d629afb1a9c1f8282ab3c16adaa2d275%40djangoproject.com.

Re: [Django] #32372: Improve consistency in "Related objects reference" docs.

[Django]

#32372: Improve consistency in "Related objects reference" docs.
-+-
 Reporter:  Jack Aitken  |Owner:  Jack
 Type:   |  Aitken
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  3.1
 Severity:  Normal   |   Resolution:  fixed
 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 ):

 In [changeset:"c708837a693f0554648b0442827a1e9f3ce67d3f" c708837a]:
 {{{
 #!CommitTicketReference repository=""
 revision="c708837a693f0554648b0442827a1e9f3ce67d3f"
 [3.2.x] Refs #32372 -- Updated manager name in related objects reference
 docs.

 Follow up to 725c549ae7a34d83447201da7190f8d71c7fc2fc.
 Backport of 2b4b6c8af0aae8785bc1347cf1be2e8e70fd5ff3 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/068.4f41d4be6ada45676130243c1d62993a%40djangoproject.com.

Re: [Django] #32372: Improve consistency in "Related objects reference" docs.

[Django]

#32372: Improve consistency in "Related objects reference" docs.
-+-
 Reporter:  Jack Aitken  |Owner:  Jack
 Type:   |  Aitken
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  3.1
 Severity:  Normal   |   Resolution:  fixed
 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 GitHub ):

 In [changeset:"2b4b6c8af0aae8785bc1347cf1be2e8e70fd5ff3" 2b4b6c8a]:
 {{{
 #!CommitTicketReference repository=""
 revision="2b4b6c8af0aae8785bc1347cf1be2e8e70fd5ff3"
 Refs #32372 -- Updated manager name in related objects reference docs.

 Follow up to 725c549ae7a34d83447201da7190f8d71c7fc2fc.
 }}}

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

[Django] #32379: Documentation: hypercorn and static files

[Django]

#32379: Documentation: hypercorn and static files
---+
   Reporter:  Sven R. Kunze|  Owner:  nobody
   Type:  Uncategorized| Status:  new
  Component:  contrib.staticfiles  |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|
---+
 Coming from the age-old problem of service static files, the usual process
 looks like this:

 1) ✅develop and test using {{{ manage.py runserver }}} and everything
 just works fine
 2) ✅ deploy code using WSGI or ASGI as described in the docs
 3) ❌ find out that static files are missing

 Specifically referring to
 https://docs.djangoproject.com/en/3.1/howto/deployment/asgi/hypercorn/

 As there is a dedicated documentation page for hypercorn, it doesn't look
 like there's a need for thinking of serving static files.

 A friend of mine suggested to use whitenoise:
 https://github.com/evansd/whitenoise

 Would it make sense to integrate this into the Django docs?


 To be transparent here, I started also different threads on different
 channels but it seems like nobody really wants to tackle this issue, so I
 thought addressing the issue at least via Django sounds reasonable because
 it's a Web framework:
 here: https://softwarerecs.stackexchange.com/questions/77600/simple-and-
 secure-command-line-http-server
 and there: https://gitlab.com/pgjones/hypercorn/-/issues/173
 from another guy: https://gitlab.com/pgjones/hypercorn/-/issues/45

 As of now, I addressed my real-world setup by setting up a "mini"-nginx
 for now, serving static files and proxying hypercorn, but that does not
 feel like a holistic solution; also when it comes to automated deployment,
 permissions, principles such as "test as you fly, fly as you test" etc.
 it's a lot more brittle.

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

Re: [Django] #32338: Accessibility issues with Django forms RadioSelect and CheckboxSelectMultiple

[Django]

#32338: Accessibility issues with Django forms RadioSelect and
CheckboxSelectMultiple
-+-
 Reporter:  Thibaud Colas|Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  forms, wcag|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by jcoombes):

 * owner:  jcoombes => (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/070.d49e15db7ad9b4892593bf5af525c0ad%40djangoproject.com.

Re: [Django] #28526: Remedy verbose, often unhelpful undefined tempate variable logging

[Django]

#28526: Remedy verbose, often unhelpful undefined tempate variable logging
-+-
 Reporter:  Tim Graham   |Owner:  Tim
 Type:   |  McCurrach
  Cleanup/optimization   |   Status:  assigned
Component:  Template system  |  Version:  master
 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 Tim McCurrach):

 * owner:  nobody => Tim McCurrach
 * 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/067.601c2e2e17a31b0e42bcb2a01a3abc34%40djangoproject.com.

Re: [Django] #32031: Added model instance to app_list context

[Django]

#32031: Added model instance to app_list context
-+-
 Reporter:  Raffaele Salmaso |Owner:  Raffaele
 |  Salmaso
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  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_docs:  1 => 0


Comment:

 `each_context()` is the currently documented way to access this
 functionality, so it strikes me that making updates there should suffice,
 and further documentation improvements could be evaluated separately.

-- 
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.32be28ecd64a7f8b3ec7d1952b20363a%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
-+-

Comment (by Marius Räsener):

 Alright, here is my PR :) https://github.com/django/django/pull/13927

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

Re: [Django] #32360: Add system check that FILE_UPLOAD_TEMP_DIR exists when set

[Django]

#32360: Add system check that FILE_UPLOAD_TEMP_DIR exists when set
-+-
 Reporter:  Tim McCurrach|Owner:  Tim
 Type:   |  McCurrach
  Cleanup/optimization   |   Status:  closed
Component:  Core (Other) |  Version:  4.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"b1821fbad5518c8ae56b7b5c2b1ea2afbbd25c7a" b1821fb]:
 {{{
 #!CommitTicketReference repository=""
 revision="b1821fbad5518c8ae56b7b5c2b1ea2afbbd25c7a"
 Fixed #32360 -- Added system check for FILE_UPLOAD_TEMP_DIR setting.
 }}}

-- 
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.e672dc1a0eb019bd6dd0cf212a29a727%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:  (none)
 Type:  New feature  |   Status:  new
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 Carlton Gibson):

 * cc: Carlton Gibson (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/061.32ec40284c9b34c78e5eb9f57b5aae57%40djangoproject.com.