Re: [Django] #30729: Add support for the RFC 7239 Forwarded header

[Django]

#30729: Add support for the RFC 7239 Forwarded header
---+-
 Reporter:  Ben Stähli |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  2.2
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Someday/Maybe
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e313e6e17-56d68401-706c-4cbc-a728-64fcae9164b4-00%40eu-central-1.amazonses.com.

Re: [Django] #30950: Replace __file__ with importlib.resources

[Django]

#30950: Replace __file__ with importlib.resources
-+-
 Reporter:  John Vandenberg  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  freezers | Triage Stage:  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e313e2c7d-dd3bcfa0-48e1-412f-8882-cdc3f220f240-00%40eu-central-1.amazonses.com.

Re: [Django] #24810: Reopen database connection automatically when no transaction is active

[Django]

#24810: Reopen database connection automatically when no transaction is active
-+-
 Reporter:  Aymeric Augustin |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (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 Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e313db65c-4791b3b7-4693-4f4a-8474-0f0c44efbcc8-00%40eu-central-1.amazonses.com.

Re: [Django] #34917: Links in the Django admin should be underlined.

[Django]

#34917: Links in the Django admin should be underlined.
-+-
 Reporter:  Dmitriy Chukhin  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  anchor |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e313c693a-7bf69b18-7396-42f3-b4eb-aa953c273a74-00%40eu-central-1.amazonses.com.

Re: [Django] #23746: Allow assertNumQueries to clear caches before it runs

[Django]

#23746: Allow assertNumQueries to clear caches before it runs
+
 Reporter:  Wojtek Ruszczewski  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Testing framework   |  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 Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e3138e161-88def316-a5d3-42b7-a856-cff7cd3961a5-00%40eu-central-1.amazonses.com.

Re: [Django] #24213: RFC 2231 Section 4.1 is not implemented

[Django]

#24213: RFC 2231 Section 4.1 is not implemented
---+
 Reporter:  Raúl Cumplido  |Owner:  (none)
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  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 Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e31380635-d3851e05-bc1a-478c-8a2e-712eac071b71-00%40eu-central-1.amazonses.com.

Re: [Django] #30637: SearchVectorField and SearchVector should be combinable.

[Django]

#30637: SearchVectorField and SearchVector should be combinable.
-+-
 Reporter:  Dani Hodovic |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  contrib.postgres |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  db, postgres, full-  | Triage Stage:  Accepted
  text, search   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e31357ef3-ddb0d1ad-df7a-45d1-8239-ca035e2f820e-00%40eu-central-1.amazonses.com.

Re: [Django] #30963: Admin list_editable not suitable for multi-user environment.

[Django]

#30963: Admin list_editable not suitable for multi-user environment.
-+-
 Reporter:  Leonardo Arroyo  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e312d493d-d4f1ad49-8691-4873-9575-807fdde05eab-00%40eu-central-1.amazonses.com.

Re: [Django] #34981: Promote `--pair` and `--bisect` from `runtest.py` to be available as flags for the Django `test` command

[Django]

#34981: Promote `--pair` and `--bisect` from `runtest.py` to be available as 
flags
for the Django `test` command
-+-
 Reporter:  Natalia Bidart   |Owner:  Sulabh
 |  Katila
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  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/0107018e3110c39f-4a3cfa6e-5b8a-45d5-ac7f-2382d3cdf75f-00%40eu-central-1.amazonses.com.

Re: [Django] #33548: Use -> operator to implement KeyTransform on SQLite 3.38+

[Django]

#33548: Use -> operator to implement KeyTransform on SQLite 3.38+
-+-
 Reporter:  Sage Abdullah|Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sqlite jsonfield | Triage Stage:  Accepted
  keytransform   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

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

Comment:

 13 months after an assignee last commented, I guess we can assume it is
 open to anyone willing to work on 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/0107018e2f6012d0-6c0ee6b9-eb00-4b18-ad89-cb96ed72ac1c-00%40eu-central-1.amazonses.com.

Re: [Django] #35284: PositiveIntegerField description is confusing

[Django]

#35284: PositiveIntegerField description is confusing
-+-
 Reporter:  Jon Ribbens  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  5.0
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Comment (by Natalia Bidart):

 Replying to [comment:11 Jon Ribbens]:
 > [...] the sentence I'm suggesting be removed, which says that this is
 "for backward compatibility reasons", ''doesn't'' make it clear that this
 will behaviour will remain "for the foreseeable future". That's my entire
 point!

 I fully understand your point, but I disagree. Deprecation notices are
 documented quite clearly and they follow a strict procedure of when they
 can be introduced and when they occur. So until these docs explicitly say
 "Deprecated in Django version X.Y", the value `0` will be allowed for the
 foreseeable future.

 > Actually it conveys the precise opposite information, it suggests that
 it is foreseen that in the future, the behaviour may change so that zero
 will not be accepted, and so if you want to store zeroes you should not be
 using this field type. It is saying "we don't think this field should
 accept zeroes, but we haven't been able to fix it yet because of backwards
 compatibility considerations, so that change is still on the to-do list".

 I understand that this is how ''you'' read the sentence, but we disagree
 on what it means. Saying ''The value 0 is accepted for backward
 compatibility reasons.'' is just an **explanation**, is not a heads-up
 that is going to be changed (as mentioned before, deprecation notices are
 handled quite differently). The sentence only explains **why** it is the
 way it is. Otherwise we'd regularly get new tickets saying
 "PositiveIntegerField should not accept 0 because 0 is not a positive
 number". In order to manage expectations from Django users, the
 clarification is there saying "we know this is weird but it's there for a
 reason".

 > Would anyone be interested in a patch to make it so that it was
 `PositiveIntegerField(allow_zero=True)` (and similarly for the other two
 "Positive" fields)? i.e. it maintains backwards compatibility, but the
 programmer can choose whether they want zeroes allowed or not? I might
 find that an interesting little project, but only if there was a
 reasonable chance the patch would get accepted (I was expecting this one
 to be a shoo-in!)

 You are welcomed to share the idea with the Django community, following
 the [https://docs.djangoproject.com/en/stable/internals/contributing/bugs-
 and-features/#requesting-features the documented guidelines for requesting
 features]. I, personally, don't think this is worth adding since by just
 using a custom and trivial validator (or just using `MinValueValidator`)
 the need of not allowing `0` in the field is solved, and in my experience,
 allowing for 0 is the less surprising semantic.
-- 
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/0107018e2f291788-acbe5c74-7b56-4bfe-8b3f-0b2a19e5a010-00%40eu-central-1.amazonses.com.

Re: [Django] #35284: PositiveIntegerField description is confusing

[Django]

#35284: PositiveIntegerField description is confusing
-+-
 Reporter:  Jon Ribbens  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  5.0
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Comment (by Jon Ribbens):

 Replying to [comment:10 Natalia Bidart]:
 > Hey Jon, I beg to differ. Both bcail and myself are answering to your
 argument: while there is ''not'' a proposal to deprecate allowing 0 in the
 field, the sentence warns the users about potential unexpected outcomes.
 It's easy to assume that a `PositiveIntegerField` would not allow 0, so
 the note in the docs is making it clear that 0 ''is allowed'' and it will
 be for the foreseeable future due to the backward compatibility goal.

 Sorry, that just confirms that you're missing what I'm trying to say. As I
 said right at the start, the change to explicitly say that zero is allowed
 was clearly a good and beneficial change. Everyone is agreed on that. But
 the sentence I'm suggesting be removed, which says that this is "for
 backward compatibility reasons", ''doesn't'' make it clear that this will
 behaviour will remain "for the foreseeable future". That's my entire
 point!

 Actually it conveys the precise opposite information, it suggests that it
 is foreseen that in the future, the behaviour may change so that zero will
 not be accepted, and so if you want to store zeroes you should not be
 using this field type. It is saying "we don't think this field should
 accept zeroes, but we haven't been able to fix it yet because of backwards
 compatibility considerations, so that change is still on the to-do list".

 That's why I think the wording should change, because it does ''not''
 convey the message you think it does (which is not, frankly, a message
 that needs conveying in the first place).

 Would anyone be interested in a patch to make it so that it was
 `PositiveIntegerField(allow_zero=True)` (and similarly for the other two
 "Positive" fields)? i.e. it maintains backwards compatibility, but the
 programmer can choose whether they want zeroes allowed or not? I might
 find that an interesting little project, but only if there was a
 reasonable chance the patch would get accepted (I was expecting this one
 to be a shoo-in!)
-- 
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/0107018e2ed7ebe2-d2f8f35f-30cd-4aa0-8e4c-04aabc8028ca-00%40eu-central-1.amazonses.com.

Re: [Django] #35289: Chunked transfer encoding is not handled correctly by MultiPartParser

[Django]

#35289: Chunked transfer encoding is not handled correctly by MultiPartParser
-+-
 Reporter:  Kyle Agronick|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  transfer-encoding,   | Triage Stage:
  chunked, multi-part|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Kyle Agronick):

 I can confirm that just by making a middleware that does
 {{{
 if request.headers["Transfer-Encoding"] == "chunked" and
 "CONTENT_LENGTH" not in request.META:
 request.META["CONTENT_LENGTH"] = "1"
 }}}
 everything gets parsed correctly even though the `CONTENT_LENGTH` is much
 more than 1.

 Maybe this issue went undetected for so long because WSGI does not have
 good support for chunked transfer encoding. But ASGI does.
-- 
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/0107018e2ed66c59-a15689b0-3510-4c91-916d-9706a1444bbc-00%40eu-central-1.amazonses.com.

[Django] #35289: Chunked transfer encoding is not handled correctly by MultiPartParser

[Django]

#35289: Chunked transfer encoding is not handled correctly by MultiPartParser
-+-
   Reporter:  Kyle   |  Owner:  nobody
  Agronick   |
   Type:  Bug| Status:  new
  Component:  HTTP   |Version:  5.0
  handling   |   Keywords:  transfer-encoding,
   Severity:  Normal |  chunked, multi-part
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I am trying to post large files from C#. The C# implementation conforms to
 the HTTP1.1 protocol and does not allow chunked transfer encoding and a
 content-length to be set at the same time.

 {{{
 Messages MUST NOT include both a Content-Length header field and a non-
 identity transfer-coding. If the message does include a non-identity
 transfer-coding, the Content-Length MUST be ignored." (RFC 2616, Section
 4.4)
 }}}

 In the `MultiPartParser` a non-existent content-length header is treated
 as 0:
 https://github.com/django/django/blob/main/django/http/multipartparser.py#L96

 When the 0 length is read, nothing gets parsed:
 https://github.com/django/django/blob/main/django/http/multipartparser.py#L147

 If you remove the check in the second link, everything works correctly. It
 works fine without an explicit content-length.

 With Nginx to turn off request buffering for a single request you need to
 use chunked transfer encoding.
-- 
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/0107018e2ec5acc9-bdbb3a38-4e8e-46d8-a0dd-6172730fcd7f-00%40eu-central-1.amazonses.com.

Re: [Django] #34977: Turn link to change password form in admin user change form into a button

[Django]

#34977: Turn link to change password form in admin user change form into a 
button
-+-
 Reporter:  Fabian Braun |Owner:  Fabian
 Type:   |  Braun
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.auth |  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by Fabian Braun):

 * 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/0107018e2e9c1e83-57d9dbaf-0b19-4f54-83fd-1d92acb4f6b1-00%40eu-central-1.amazonses.com.

Re: [Django] #28900: QuerySet.values() and values_list() for compound queries fails with annotation.

[Django]

#28900: QuerySet.values() and values_list() for compound queries fails with
annotation.
-+-
 Reporter:  elliott-omosheye |Owner:  ontowhee
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  union, values| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Dan LaManna):

 * cc: Dan LaManna (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/0107018e2e7a980d-5e905799-1ab5-4a8e-b757-77573cc0fe63-00%40eu-central-1.amazonses.com.

Re: [Django] #33548: Use -> operator to implement KeyTransform on SQLite 3.38+

[Django]

#33548: Use -> operator to implement KeyTransform on SQLite 3.38+
-+-
 Reporter:  Sage Abdullah|Owner:
 Type:   |  rajdesai24
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sqlite jsonfield | Triage Stage:  Accepted
  keytransform   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by bcail):

 @rajdesai24, are you planning to open a PR for this?
-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018e2e2d0064-0d60d35d-7ec2-45c4-9b85-f0e959455823-00%40eu-central-1.amazonses.com.

Re: [Django] #34533: OuterRef not resolved as part oh ORDER BY clause

[Django]

#34533: OuterRef not resolved as part oh ORDER BY clause
-+-
 Reporter:  REGNIER Guillaume|Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  OuterRef, OrderBy| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Comment (by bcail):

 @HeejunShin, you can try running the example from the ticket Description -
 see if that works with the main branch. I don't think this issue has been
 fixed, though.
-- 
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/0107018e2e21b07f-2fb78502-7142-4ad3-a911-7bc3993033f6-00%40eu-central-1.amazonses.com.

Re: [Django] #35278: `ngettext` result can be possibly undefined.

[Django]

#35278: `ngettext` result can be possibly undefined.
-+-
 Reporter:  Piotr Kawula |Owner:  Piotr
 |  Kawula
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  5.0
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  ngettext,catalog,i18n,internationalization,|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Natalia Bidart):

 * stage:  Unreviewed => Accepted
 * 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/0107018e2db20ff6-7fd6d5d7-c307-4f4e-b53c-51ecb697bfb8-00%40eu-central-1.amazonses.com.

Re: [Django] #35278: `ngettext` result can be possibly undefined.

[Django]

#35278: `ngettext` result can be possibly undefined.
-+-
 Reporter:  Piotr Kawula |Owner:  Piotr
 |  Kawula
 Type:  Uncategorized|   Status:  assigned
Component:   |  Version:  5.0
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
  ngettext,catalog,i18n,internationalization,|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Natalia Bidart):

 Tentatively accepting.
-- 
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/0107018e2db1cf9d-b789e431-0ff2-4b35-9dda-cc3fafd90e8c-00%40eu-central-1.amazonses.com.

Re: [Django] #35288: login_required / user_passes_test redirects back to POST-only view

[Django]

#35288: login_required / user_passes_test redirects back to POST-only view
--+--
 Reporter:  Patrick Rauscher  |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  contrib.auth  |  Version:  5.0
 Severity:  Normal|   Resolution:  wontfix
 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 Natalia Bidart):

 * resolution:   => wontfix
 * status:  new => closed
 * type:  Bug => New feature

Comment:

 Hello Patrick, thanks for your report and for helping making Django
 better.

 I do understand your issue though it seems a bit of a niche problem to me.
 I believe you could fix this by providing a custom view for the
 `login_url` param of the `user_passes_test` method that would redirect the
 user to whatever view is more appropriate than the POST-only view,
 particularly a view that could handle GET requests and provide a way of
 refreshing the session and taking the user to a suitable page to redo the
 POST. Also, your POST-only view could be tweaked so GET requests are
 allowed only when coming from a login operation, and the view itself could
 raise 405 for every other situation.

 In summary, I don't think this is a bug in Django, and I don't think the
 outlined issue applies to the broader ecosystem. Django is a framework
 designed to offer robust and accurate solutions for common scenarios, so
 I'll close the ticket accordingly, but if you disagree, you can consider
 starting a new conversation on the
 [https://forum.djangoproject.com/c/internals/5 Django Forum], where you'll
 reach a wider audience and likely get extra feedback. More information in
 [https://docs.djangoproject.com/en/stable/internals/contributing/bugs-and-
 features/#requesting-features the documented guidelines for requesting
 features].
-- 
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/0107018e2da910d1-868609a2-ab67-4494-8f5e-950d8562c4a1-00%40eu-central-1.amazonses.com.

Re: [Django] #15059: Additional Documentation for the objects in the admin templates

[Django]

#15059: Additional Documentation for the objects in the admin templates
-+-
 Reporter:  mlakewood|Owner:  Ryan
 |  Cheley
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:  admin templates  | Triage Stage:  Accepted
  override   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ryan Cheley):

 * owner:  nobody => Ryan Cheley
 * 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/0107018e2d9165fe-9dcef9db-35d9-4139-a825-705150fa95f4-00%40eu-central-1.amazonses.com.

Re: [Django] #35284: PositiveIntegerField description is confusing

[Django]

#35284: PositiveIntegerField description is confusing
-+-
 Reporter:  Jon Ribbens  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  5.0
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Comment (by Natalia Bidart):

 Replying to [comment:9 Jon Ribbens]:
 > I rather think you're missing the point completely - the sentence
 doesn't "provide a clarification", it misleads people and makes things
 less clear, as I explained in my argument above that nobody has provided a
 response to. But obviously I can't force you to improve your product. Oh
 well.

 Hey Jon, I beg to differ. Both bcail and myself are answering to your
 argument: while there is ''not'' a proposal to deprecate allowing 0 in the
 field, the sentence warns the users about potential unexpected outcomes.
 It's easy to assume that a `PositiveIntegerField` would not allow 0, so
 the note in the docs is making it clear that 0 ''is allowed'' and it will
 be for the foreseeable future due to the backward compatibility goal.

 I hope that helps!
-- 
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/0107018e2d890a5d-5a487fc8-fcd6-40a3-b8e4-4090a758e4d7-00%40eu-central-1.amazonses.com.

Re: [Django] #26412: createsupseruser with email login instead of username

[Django]

#26412: createsupseruser with email login instead of username
-+-
 Reporter:  Adam |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.9
  commands)  |
 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
-+-
Comment (by Natalia Bidart):

 #35287 was a duplicate of this one.
-- 
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/0107018e2d76f011-46ca09c2-6789-4ac1-81df-8ca7c1aca456-00%40eu-central-1.amazonses.com.

Re: [Django] #14831: Django Template Style Guide

[Django]

#14831: Django Template Style Guide
-+-
 Reporter:  Simon Meers  |Owner:  Ryan
 |  Cheley
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:  1.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  template, style, | Triage Stage:  Ready for
  format |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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

Comment:

 In [changeset:"f2c35249591d202ee544eadcaa9de4c255045692" f2c35249]:
 {{{#!CommitTicketReference repository=""
 revision="f2c35249591d202ee544eadcaa9de4c255045692"
 Fixed #14831 -- Extended template style guide in 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/0107018e2d74bf3c-52abf02d-9425-4181-a898-acdf08e97c05-00%40eu-central-1.amazonses.com.

Re: [Django] #27460: Allow declaring a GenericRelation from an abstract model to another abstract model

[Django]

#27460: Allow declaring a GenericRelation from an abstract model to another
abstract model
-+-
 Reporter:  Wolfgang Grim|Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  GenericRelation, | Triage Stage:  Accepted
  Abstract, ContentFramework |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sage Abdullah):

 * cc: Sage Abdullah (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/0107018e2d6be973-f84ee084-5d68-4aaa-b0e6-a40fc7984d97-00%40eu-central-1.amazonses.com.

[Django] #35288: login_required / user_passes_test redirects back to POST-only view

[Django]

#35288: login_required / user_passes_test redirects back to POST-only view
+
   Reporter:  Patrick Rauscher  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  contrib.auth  |Version:  5.0
   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 |
+
 Assume an application with session timeout and a login restricted area. In
 this area there is a form, POSTing its content to a view which has
 `@require_http_methods(["POST"])` as a security percaution.

 A valid user visits the site with the form, stays there long enough for
 the session to time out and submits the form. Django will check if the
 user is logged in, which leads to `user_passes_test` evaluating to false
 and redirecting the user back to login while setting the next-url-
 parameter to the submit-view. After login, the user is redirected to the
 view which returns error 405 due to `@require_http_methods(["POST"])`.

 I'm quite sure this is a bug, as 405 would not be the error he
 anticipates, but I'm not too sure about a possible fix. One solution would
 be to check in `user_passes_test` if we have a POST/PUT/...-Request and
 try to use Referer in that case?
-- 
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/0107018e2d475163-9f04f066-d1ff-4b31-a711-a7630ce7451c-00%40eu-central-1.amazonses.com.

Re: [Django] #14831: Django Template Style Guide

[Django]

#14831: Django Template Style Guide
-+-
 Reporter:  Simon Meers  |Owner:  Ryan
 |  Cheley
 Type:  New feature  |   Status:  assigned
Component:  Documentation|  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:  template, style, | Triage Stage:  Ready for
  format |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  1 => 0
 * 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/0107018e2ca15fbf-578c8121-5b0c-4483-86dc-1dd70bd16f73-00%40eu-central-1.amazonses.com.

Re: [Django] #25595: Invalid regexp in URLValidator can't handle file:// schemes

[Django]

#25595: Invalid regexp in URLValidator can't handle file:// schemes
-+-
 Reporter:  Marcin Nowak |Owner:  Adam
 |  Zapletal
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  1.8
 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:"710ca576816fe90c15a7e62f95074ff0bbd77f0e" 710ca576]:
 {{{#!CommitTicketReference repository=""
 revision="710ca576816fe90c15a7e62f95074ff0bbd77f0e"
 [5.0.x] Fixed #25595 -- Doc'd that URLValidator rejects file:// URIs
 without a host.

 Backport of 7326513a8f5d4d4e0aeec28540f9451b939b1dda from main
 }}}
-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018e2c9d904b-721fc4fb-5fde-4f16-b15f-84176bb80ec3-00%40eu-central-1.amazonses.com.

Re: [Django] #25595: Invalid regexp in URLValidator can't handle file:// schemes

[Django]

#25595: Invalid regexp in URLValidator can't handle file:// schemes
-+-
 Reporter:  Marcin Nowak |Owner:  Adam
 |  Zapletal
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  1.8
 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 ):

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

Comment:

 In [changeset:"7326513a8f5d4d4e0aeec28540f9451b939b1dda" 7326513a]:
 {{{#!CommitTicketReference repository=""
 revision="7326513a8f5d4d4e0aeec28540f9451b939b1dda"
 Fixed #25595 -- Doc'd that URLValidator rejects file:// URIs without a
 host.
 }}}
-- 
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/0107018e2c9cddff-3583b70b-0e26-496d-ae78-1c1006370b4f-00%40eu-central-1.amazonses.com.

Re: [Django] #25595: Invalid regexp in URLValidator can't handle file:// schemes

[Django]

#25595: Invalid regexp in URLValidator can't handle file:// schemes
-+-
 Reporter:  Marcin Nowak |Owner:  Adam
 |  Zapletal
 Type:  Bug  |   Status:  assigned
Component:  Core (Other) |  Version:  1.8
 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/0107018e2c6078ed-4cad7868-800b-4745-9d5f-3d03b081007f-00%40eu-central-1.amazonses.com.

Re: [Django] #35285: Optimize ForeignObject._check_unique_target

[Django]

#35285: Optimize ForeignObject._check_unique_target
-+-
 Reporter:  Adam Johnson |Owner:  Adam
 Type:   |  Johnson
  Cleanup/optimization   |   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
-+-
Changes (by Mariusz Felisiak ):

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

Comment:

 In [changeset:"e5ec11a84d6f3725220360e893050cb00403a22e" e5ec11a]:
 {{{#!CommitTicketReference repository=""
 revision="e5ec11a84d6f3725220360e893050cb00403a22e"
 Fixed #35285 -- Optimized ForeignObject._check_unique_target().
 }}}
-- 
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/0107018e2c459651-27b0daa9-cca3-415d-8762-915b3f16fbfc-00%40eu-central-1.amazonses.com.