date:20240318

Re: [Django] #34479: Support "watchfiles" in the autoreloader

2024-03-18 Thread Django

#34479: Support "watchfiles" in the autoreloader
--+
 Reporter:  Tom Forbes|Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Utilities |  Version:  4.2
 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 Ülgen Sarıkavak):

 Got it, thanks again. I'll do my best at least a couple of them :)
-- 
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/0107018e5534a134-f6f9ca7c-a13b-4abb-9d78-04a3fbc99df5-00%40eu-central-1.amazonses.com.

Re: [Django] #34479: Support "watchfiles" in the autoreloader

2024-03-18 Thread Django

#34479: Support "watchfiles" in the autoreloader
--+
 Reporter:  Tom Forbes|Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Utilities |  Version:  4.2
 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):

 Replying to [comment:6 Ülgen Sarıkavak]:
 > According to my notes, it shouldn't be more than 50 issues so far,

 120 :) I think it's more than enough for GSoC and Djangonaut space.
 Crossing fingers that they will be fixed by you.
-- 
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/0107018e552afbb8-8be43c72-f71d-4e35-b10b-5be39733-00%40eu-central-1.amazonses.com.

Re: [Django] #34479: Support "watchfiles" in the autoreloader

2024-03-18 Thread Django

Replying to [comment:5 Mariusz Felisiak]:
> Ülgen, Can I ask why you added yourself to CC in hundreds of tickets in
the last way days? You can use a [https://groups.google.com/g/django-
updates django-updates mailing list] or follow the
[https://code.djangoproject.com/timeline timeline] to track updates on all
tickets.

Hey Maurizs. I was checking issues before the second session of
djangonaut-space and GSoC. According to my notes, it shouldn't be more
than 50 issues so far, and I did go over almost 600 issues to select a
small portion of them that interests me and the people I work with. I
believe this is a proper use of the CC feature, but if it is creating
notifications for all those other people and no way to disable it on my
end, I'll be more careful about it. Thanks for the comment and the
direction.
--
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/0107018e551f100b-e52886c4-a83a-415a-a428-654718da6773-00%40eu-central-1.amazonses.com.

Re: [Django] #34479: Support "watchfiles" in the autoreloader

2024-03-18 Thread Django

#34479: Support "watchfiles" in the autoreloader
--+
 Reporter:  Tom Forbes|Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Utilities |  Version:  4.2
 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):

 Ülgen, Can I ask why you added yourself to CC in hundreds of tickets in
 the last way days? You can use a [https://groups.google.com/g/django-
 updates django-updates mailing list] or follow the
 [https://code.djangoproject.com/timeline timeline] to track updates on all
 tickets.
-- 
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/0107018e55175733-39456cf0-5f97-4cdd-acd3-90a126b5143b-00%40eu-central-1.amazonses.com.

Re: [Django] #34479: Support "watchfiles" in the autoreloader

2024-03-18 Thread Django

#34479: Support "watchfiles" in the autoreloader
--+
 Reporter:  Tom Forbes|Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Utilities |  Version:  4.2
 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/0107018e5511965c-9d41085b-071a-4d5a-8b00-c7efb661ecc2-00%40eu-central-1.amazonses.com.

Re: [Django] #33650: Update startproject template with config directory

2024-03-18 Thread Django

#33650: Update startproject template with config directory
-+-
 Reporter:  Timothy Allen|Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Management |  Version:  dev
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  startproject,| Triage Stage:
  template   |  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/0107018e550df8a1-9739ebec-506b-4501-91eb-27ea362e629d-00%40eu-central-1.amazonses.com.

Re: [Django] #32472: runserver prematurely closes connection for large response body

2024-03-18 Thread Django

#32472: runserver prematurely closes connection for large response body
---+
 Reporter:  David Sanders  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  HTTP handling  |  Version:  3.1
 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/0107018e550aca3c-d4cf59c7-f40f-4aa6-9093-774e86b95523-00%40eu-central-1.amazonses.com.

Re: [Django] #35316: Support scalars as query parameters in admin changelist filters (for backward compatibility).

2024-03-18 Thread Django

#35316: Support scalars as query parameters in admin changelist filters (for
backward compatibility).
-+-
 Reporter:  Manolis  |Owner:  nobody
  Stamatogiannakis   |
 Type:  Uncategorized|   Status:  closed
Component:  contrib.admin|  Version:  5.0
 Severity:  Normal   |   Resolution:  wontfix
 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 Mariusz Felisiak):

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

Comment:

 Are you maintaining a 3rd-party package? it's rather rare that you have to
 support multiple Django versions in a project. Moreover,
 `prepare_lookup_value()` is another private API that you don't have to
 use. Why don't you set a value directly?
 {{{#!python
 self.used_parameters[self.lookup_kwarg] = True
 }}}

 Please don't reopen closed ticket. You can
 [https://docs.djangoproject.com/en/stable/internals/contributing/triaging-
 tickets/#closing-tickets follow the triaging guidelines with regards to
 wontfix tickets] and take this to DevelopersMailingList, if you don't
 agree.
-- 
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/0107018e54fb4813-79d7f84b-d52e-4e06-b13e-950b52bd02ec-00%40eu-central-1.amazonses.com.

Re: [Django] #28519: Add filter(), exclude(), and other base QuerySet methods to combined QuerySets (union(), etc.)

2024-03-18 Thread Django

#28519: Add filter(), exclude(), and other base QuerySet methods to combined
QuerySets (union(), etc.)
-+-
 Reporter:  Stanislav Karpov |Owner:  Damir
 |  Nafikov
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  union,   | Triage Stage:  Accepted
  intersection, difference   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Damir Nafikov):

 * owner:  nobody => Damir Nafikov
 * 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/0107018e5499d68a-983c98d1-70c4-4ae3-b88a-bbfcbcd5604d-00%40eu-central-1.amazonses.com.

Re: [Django] #35312: staticurl_urlpatterns incorrectly uses STATIC_URL that prefixed using SCRIPT_NAME

2024-03-18 Thread Django

#35312: staticurl_urlpatterns incorrectly uses STATIC_URL that prefixed using
SCRIPT_NAME
-+-
 Reporter:  yudhiwidyatama   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.staticfiles  |  Version:  5.0
 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 yudhiwidyatama):

 I am not proposing to remove SCRIPT_NAME from the STATIC_URL, but only to
 adjust the url pattern generated by staticfiles_urlpatterns. If I may ask,
 for what condition the staticfiles_urlpatterns needs SCRIPT_NAME prefix ?
-- 
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/0107018e53dd7b5a-f88e4909-a89f-4b22-bf49-da5c89f6955c-00%40eu-central-1.amazonses.com.

Re: [Django] #35316: Support scalars as query parameters in admin changelist filters (for backward compatibility).

2024-03-18 Thread Django

#35316: Support scalars as query parameters in admin changelist filters (for
backward compatibility).
-+-
 Reporter:  Manolis  |Owner:  nobody
  Stamatogiannakis   |
 Type:  Uncategorized|   Status:  new
Component:  contrib.admin|  Version:  5.0
 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 Manolis Stamatogiannakis):

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

Comment:

 Replying to [comment:1 Mariusz Felisiak]:
 > `build_q_object_from_lookup_parameters()` is a private API and all
 built-in filter use `GET.lists()` so I don't see anything breaking in the
 #1873. If you extend built-in filters and really want to use
 `build_q_object_from_lookup_parameters()` you should also use
 `GET.lists()`.


 I believe you may have misunderstood the case described. Of course
 `build_q_object_from_lookup_parameters()` is not directly used, since I am
 referring to code that pre-dates Django 5, when the function was
 introduced. The problem is that this code now needs version conditionals
 in order to work with both Django 4.x and Django 5.x.

 This isn't anything super fancy. Just a subclass of BooleanFieldListFilter
 that needs to have True as the default selection instead of All. It looks
 like this ATM:

 {{{
 class BooleanDefaultTrueFilter(BooleanFieldListFilter):
  def __init__(self, *args, **kwargs):
  super().__init__(*args, **kwargs)
  if self.lookup_kwarg2 not in self.used_parameters and
 self.lookup_kwarg not in self.used_parameters:
  self.`[self.lookup_kwarg] = prepare_lookup_value(
  self.lookup_kwarg,
  True if django.VERSION < (5,0) else (True,)
  )
  self.lookup_val = '1'
 }}}

 Without the conditional, an exception will be raised in
 `build_q_object_from_lookup_parameters()`, which is why the specific
 function was updated.

 Of course one may still argue that `used_parameters` is internal state.
 But overriding `__init__()` like above is still the most elegant way I
 could find to achive the desired effect (see [1]). Is there a
 better/"sanctioned" way to achieve this effect? The documentation for
 BooleanFieldListFilter/FieldListFilter is pretty sparse.

 Also, a quick GH search shows a number of repositories modifying
 `used_parameters` [2]. So, although not thorougly documented, this is not
 something super-exotic for users customizing admin filters, and one would
 expect that there will be more codebases that will have to implement
 similar workarounds.

 Overall, the sparse documentation for
 BooleanFieldListFilter/FieldListFilter should not be a reason for
 breakage, when that is easily avoidable.

 Along this line, I think that updating
 `build_q_object_from_lookup_parameters()` as proposed in PR #17990 will be
 a useful addition, as long as there are no side-effects that I missed and
 would outweigh the benefits.



 [1] https://forum.djangoproject.com/t/django-admin-filter-how-to-default-
 to-no-or-yes-rather-than-all/6684
 [2]
 https://github.com/search?q=self.used_parameters%5B+lang%3APython+=code
-- 
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/0107018e53dd43a7-857311fa-74c5-4f9d-bef4-3097de1c3749-00%40eu-central-1.amazonses.com.

Re: [Django] #35314: Django 5 breaks value of Date field rendering correctly in template

2024-03-18 Thread Django

#35314: Django 5 breaks value of Date field rendering correctly in template
---+--
 Reporter:  Michael|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Forms  |  Version:  5.0
 Severity:  Normal |   Resolution:  duplicate
 Keywords:  form date  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Comment (by Michael):

 Replying to [comment:8 Natalia Bidart]:
 > Replying to [comment:7 Michael]:
 > > Seems a bit counter intuitive to have a broken date input format by
 default.
 >
 > This feels a bit of a over statement, since Django does not support
 (yet) `type="date"` input (see #21470). Were you able to read the related
 issues I linked? This conversation is also quite relevant:
 https://groups.google.com/g/django-developers/c/wp-pnzcB25o/m/D5gEOzPIAQAJ

 Sorry, I should have toned it down and said the value being passed into
 the date widgets is what doesn't work. The pattern that Django forms has
 is quite a close relationship with HTML widgets. It's arguabley unexpected
 the way that the `DateInput` is not an HTML ``. Thank
 you for linking those conversations, sorry by the time I had answered the
 question I forgot there were linked issues (kids handing off
 arms/legs/calling for dinner time) and I lost track. Will checkout the
 issues thanks!
-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018e5350277a-7ddcfb11-c645-45ef-8ff1-584dbcbc8fff-00%40eu-central-1.amazonses.com.

Re: [Django] #34853: Accept-Language Header takes precedence over cookie for format localization

2024-03-18 Thread Django

Replying to [comment:14 Claude Paroz]:
> I had a look at your issue. This is an issue with the `` widgets. And this is exactly why Django doesn't use
`type="date"` by default. With those inputs, browsers are forcing their
content to the format of the current active browser locale, whatever the
language of the page language. So Django cannot do anything to change
that.
>
> Read the last comment of #34660 and the tickets/discussion it
references.

Correct me if I am understanding you incorrectly, but what I think you are
saying is Django does not provide a `` because the
`value` should be set according to the active browser's locale, which
Django doesn't know server side? If that is what you are saying, I
disagree, it is always in the format "-MM-DD", see:
Date input on MDN: https://developer.mozilla.org/en-
US/docs/Web/HTML/Element/input/date
Date Time Format on MDN: https://developer.mozilla.org/en-
US/docs/Web/HTML/Date_and_time_formats#date_strings

> HTML uses a variation of the ISO 8601 standard for its date and time
strings.

It would be very simple to have Django render date value's server side
such that it works correctly with ``, it just has to do
less like in Django 4, instead of forcing the default language's
DATE_INPUT_FORMAT to the settings language.

I opened an issue about this recently:
https://code.djangoproject.com/ticket/35314?replyto=8#comment
--
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/0107018e534a376a-a8b7ca61-a19b-47f8-9fe1-53ace4271af7-00%40eu-central-1.amazonses.com.

Re: [Django] #17235: Multipartparser shouldn't leave request.POST/request.FILES mutable

2024-03-18 Thread Django

#17235: Multipartparser shouldn't leave request.POST/request.FILES mutable
---+
 Reporter:  Florian Apolloner  |Owner:  bcail
 Type:  Bug|   Status:  assigned
Component:  HTTP handling  |  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 bcail):

 * cc: bcail (added)
 * needs_better_patch:  1 => 0
 * owner:  vinay karanam => bcail

Comment:

 I opened a [https://github.com/django/django/pull/17991 new PR], based on
 the previous one. I updated the code to make `MultiValueDict` able to be
 mutable or immutable, like `QueryDict`. Is that a good direction to go?
-- 
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/0107018e53008f12-71418ef1-fd66-44a4-a0bb-dca460e4122f-00%40eu-central-1.amazonses.com.

Re: [Django] #35314: Django 5 breaks value of Date field rendering correctly in template

2024-03-18 Thread Django

#35314: Django 5 breaks value of Date field rendering correctly in template
---+--
 Reporter:  Michael|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Forms  |  Version:  5.0
 Severity:  Normal |   Resolution:  duplicate
 Keywords:  form date  | 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):

 Replying to [comment:7 Michael]:
 > Seems a bit counter intuitive to have a broken date input format by
 default.

 This feels a bit of a over statement, since Django does not support (yet)
 `type="date"` input (see #21470). Were you able to read the related issues
 I linked? This conversation is also quite relevant:
 https://groups.google.com/g/django-developers/c/wp-pnzcB25o/m/D5gEOzPIAQAJ
-- 
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/0107018e52f5aa76-adf9926b-e6df-4922-9c27-eeac0f06ff4c-00%40eu-central-1.amazonses.com.

Re: [Django] #35316: Support scalars as query parameters in admin changelist filters (for backward compatibility).

2024-03-18 Thread Django

#35316: Support scalars as query parameters in admin changelist filters (for
backward compatibility).
---+--
 Reporter:  m000   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.admin  |  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
---+--
Changes (by Mariusz Felisiak):

 * cc: Sarah Boyce (added)
 * resolution:   => invalid
 * status:  new => closed

Comment:

 `build_q_object_from_lookup_parameters()` is a private API and all built-
 in filter use `GET.lists()` so I don't see anything breaking in the #1873.
 If you extend built-in filters and really want to use
 `build_q_object_from_lookup_parameters()` you should also use
 `GET.lists()`.
-- 
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/0107018e52d8e8a7-2576d8fa-02f3-4259-a044-a26368e404c6-00%40eu-central-1.amazonses.com.

Re: [Django] #35314: Django 5 breaks value of Date field rendering correctly in template

2024-03-18 Thread Django

#35314: Django 5 breaks value of Date field rendering correctly in template
---+--
 Reporter:  Michael|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Forms  |  Version:  5.0
 Severity:  Normal |   Resolution:  duplicate
 Keywords:  form date  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Comment (by Michael):

 Hi Natalia, thanks for the comment, I am using it like this (which used to
 work in Django 4):

 {{{
 class FooForm(forms.ModelForm):
 class Meta:
 model = Foo
 exclude = [...]
 widgets = {
   `'bar_date': forms.DateInput(attrs={'type':'date'}),`
 }
 }}}

 But I made the following changes to do it working:
   `'bar_date': forms.DateInput(format='%Y-%m-%d',
 attrs={'type':'date'}),`

 Seems a bit counter intuitive to have a broken date input format by
 default.
-- 
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/0107018e52bec407-ff6f664c-7c3f-488a-abcb-c230327276cd-00%40eu-central-1.amazonses.com.

[Django] #35316: Support scalars as query parameters in admin changelist filters (for backward compatibility).

2024-03-18 Thread Django

#35316: Support scalars as query parameters in admin changelist filters (for
backward compatibility).
-+
Reporter: m000 | Owner: nobody
Type: Uncategorized | Status: new
Component: contrib.admin |Version: 5.0
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Needs documentation: 0 |Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
-+
Ticket #1873 added support for multi-valued query parameters in admin
changelist filters. Because only list types are supported, older code that
e.g. extends SimpleListFilter or BooleanFieldListFilter will break.

The latter (extending BooleanFieldListFilter) may even be completely
unsupported. See notes in PR for #1873.

Overall, user code needs to introduce version conditionals if it is
required to support both Django 4.x and Django 5. The reason is that
Django 4.x only supports scalar types as query parameter values, while
Django 5 only supports lists.

Since supporting both scalars and lists should be possible without adding
complexity to the Django codebase, it would be good to continue supporting
scalars, perhaps with a deprecation warning, if necessary.
--
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/0107018e52bb0113-7ee71bb9-72b4-43c1-bbee-73b5bbd662c6-00%40eu-central-1.amazonses.com.

Re: [Django] #35306: Improve documentation for the various date format settings

2024-03-18 Thread Django

#35306: Improve documentation for the various date format settings
-+-
 Reporter:  Richard  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:   |  Version:  5.0
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  LANGUAGE_CODE,   | Triage Stage:  Accepted
  DATE_FORMAT|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Natalia Bidart):

 * type:  Bug => Cleanup/optimization

-- 
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/0107018e5279a42a-f4dadc9c-102b-4f0e-80d0-b87aead90d0d-00%40eu-central-1.amazonses.com.

Re: [Django] #35306: Improve documentation for the various date format settings (was: Localisation of dates very confusing - why can't it be turned off anymore?)

2024-03-18 Thread Django

#35306: Improve documentation for the various date format settings
-+-
 Reporter:  Richard  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  5.0
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  LANGUAGE_CODE,   | Triage Stage:  Accepted
  DATE_FORMAT|
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
 * summary:
 Localisation of dates very confusing - why can't it be turned off
 anymore?
 => Improve documentation for the various date format settings

Comment:

 Accepting for the documentation improvements pending feedback from Claude.
-- 
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/0107018e52796bcf-31daff8f-1542-445a-aea9-3be107bde013-00%40eu-central-1.amazonses.com.

Re: [Django] #35314: Django 5 breaks value of Date field rendering correctly in template

2024-03-18 Thread Django

#35314: Django 5 breaks value of Date field rendering correctly in template
---+--
 Reporter:  Michael|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Forms  |  Version:  5.0
 Severity:  Normal |   Resolution:  duplicate
 Keywords:  form date  | 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):

 Hey Michael, in one of your comments, you describe your field as: ``. But Django doesn't use `type="date"` by
 default (see as further reference #35293,  #34853, #34660, #33113 and
 more).

 How are you generating this field?
-- 
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/0107018e526a0ff8-af460f35-8d45-4203-86d7-10615acd2762-00%40eu-central-1.amazonses.com.

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

2024-03-18 Thread Django

Replying to [comment:11 bcail]:
>
[https://github.com/django/django/blob/main/django/core/handlers/asgi.py#L260
The ASGI handler] might be relevant.

That is interesting. So it seems like it could be optimized even further.
In my use case with the 6GB upload it would create two 6GB files on disk.
`_load_post_and_files` seems like it should be hooked into that directly
with the `MultiPartParser` instead of buffering it all to disk and then
reading it out but that seems even more ambitious. Another problem I see
there is that once it spools to disk it is going to block the event loop
because it is doing blocking IO. It should be doing something like
asgiref's `sync_to_async`.
--
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/0107018e525c1f61-c74dc223-f499-41d4-b1f8-ab686da3eb75-00%40eu-central-1.amazonses.com.

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

2024-03-18 Thread Django

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

 [https://github.com/django/django/blob/main/django/core/handlers/asgi.py#L260
 The ASGI handler] might be relevant.
-- 
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/0107018e5246f838-0cdf6b43-8539-4d27-a3b3-deb61d064d4c-00%40eu-central-1.amazonses.com.

Re: [Django] #34059: Validation of check constraints on JSONField key transforms with None produces invalid SQL on PostgreSQL.

2024-03-18 Thread Django

#34059: Validation of check constraints on JSONField key transforms with None
produces invalid SQL on PostgreSQL.
-+-
 Reporter:  Dan LaManna  |Owner:  David
 |  Sanders
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Comment (by GitHub ):

 In [changeset:"9c17010358891c73417ec569df4f568c0671c099" 9c17010]:
 {{{#!CommitTicketReference repository=""
 revision="9c17010358891c73417ec569df4f568c0671c099"
 Refs #34059, Refs #34060 -- Removed outdated warning about validation of
 JSONField constraints.

 Known issues have been fixed in:
 - 0d8fbe2ade29f1b7bd9e6ba7a0281f5478603a43,
 - c991602ce5798385261381025c06698d7fd30dc5, and
 - 26aae5614487f58ddb1df5726224393887373ecd.
 }}}
-- 
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/0107018e521e6158-b55f4255-abfa-44d7-b5bd-9bdd7c792959-00%40eu-central-1.amazonses.com.

Re: [Django] #34060: Creating CheckConstraint on JSONField with __exact lookup on key transforms crashes on Oracle.

2024-03-18 Thread Django

#34060: Creating CheckConstraint on JSONField with __exact lookup on key 
transforms
crashes on Oracle.
-+-
 Reporter:  Mariusz Felisiak |Owner:  raydeal
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Oracle   | 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 GitHub ):

 In [changeset:"9c17010358891c73417ec569df4f568c0671c099" 9c17010]:
 {{{#!CommitTicketReference repository=""
 revision="9c17010358891c73417ec569df4f568c0671c099"
 Refs #34059, Refs #34060 -- Removed outdated warning about validation of
 JSONField constraints.

 Known issues have been fixed in:
 - 0d8fbe2ade29f1b7bd9e6ba7a0281f5478603a43,
 - c991602ce5798385261381025c06698d7fd30dc5, and
 - 26aae5614487f58ddb1df5726224393887373ecd.
 }}}
-- 
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/0107018e521e61de-fffd9972-4c2a-45af-aaaf-e75b28b8e036-00%40eu-central-1.amazonses.com.

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

2024-03-18 Thread Django

I can make a patch. There are a few ways to fix this. I think the best way
should be a new upload file handler that is the default which uses
`SpooledTemporaryFile` so it can cleanly fall back if there is too much
data while being fast for small requests. I think we also need to check
`DATA_UPLOAD_MAX_MEMORY_SIZE` as we are reading the stream into the temp
file and throw a `SuspiciousOperation` if we read too much. Looking at the
docs it seems `FILE_UPLOAD_MAX_MEMORY_SIZE` and
`DATA_UPLOAD_MAX_MEMORY_SIZE` are named similarly but one controls if we
write to disk and one controls if we abort the request.

That is a bit ambitious considering I've never contributed to Django and
would probably require deprecating the current handlers. If we don't want
to do the ambitious approach, the check in `MemoryFileUploadHandler` that
does `self.activated = content_length <=
settings.FILE_UPLOAD_MAX_MEMORY_SIZE` could be `self.activated =
content_length and content_length <= settings.FILE_UPLOAD_MAX_MEMORY_SIZE`
and cause all requests that don't have a content-length to fall back to
`TemporaryFileUploadHandler` in the default configuration. That would mean
`MemoryFileUploadHandler` won't work with chunked transfer-encoding
without a content-length. Perhaps add a note in the docs since reading an
unspecified content-length into memory is dangerous anyways.

Thoughts?
--
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/0107018e521de332-7c8a59c5-6f3c-4502-aebf-ff7db655a1d5-00%40eu-central-1.amazonses.com.

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

2024-03-18 Thread Django

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

 > request body is correctly dechunked before being passed off to Django
 If a request body is dechunked, should the Transfer-Encoding header still
 be set to "chunked" and the Content-Length header be missing? Would it
 make sense to change those if the request body is dechunked?
-- 
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/0107018e52187ce4-db9c9145-70b3-4325-a159-b5b22d13d215-00%40eu-central-1.amazonses.com.

Re: [Django] #35306: Localisation of dates very confusing - why can't it be turned off anymore?

2024-03-18 Thread Django

* cc: Claude Paroz (added)

Comment:

(Adding Claude as cc.) Claude, do you have any pointers on how to make use
of the `DATE_FORMAT` and related settings? Specifically, how to have them
honored in templates.
As an example, I tried using the `date` template tag, and the settings
seem ignored, having the format from LANGUAGE_CODE taking precedence. I
know this is mentioned in the docs:

> Note that the corresponding locale-dictated format has higher precedence
and will be applied instead.

But since LANGUAGE_CODE can not be unset (afaik), it seems unclear when
the `DATE_FORMAT` and related settings are used (outside of the
`formats.py` approach). Just for clarity's sake, I don't think there is a
bug in Django, I think we could add some clarifications to the docs to be
more explicit about this particular usage.

(Another data point: even using `{% localize off %}` does not honor the
settings values. This feels unexpected to me...)
--
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/0107018e5212598a-9766ba8c-39d5-4da1-a451-82a96f39b9ce-00%40eu-central-1.amazonses.com.

Re: [Django] #35315: 5.0.3: pytest fails with tons of ImportErrors

2024-03-18 Thread Django

#35315: 5.0.3: pytest fails with tons of ImportErrors
+--
 Reporter:  Tomasz Kłoczko  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Uncategorized   |  Version:  5.0
 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 Jacob Walls):

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

Comment:

 Django 5.0 [https://docs.djangoproject.com/en/5.0/releases/5.0/ does not
 support python 3.9].
-- 
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/0107018e520dbcbc-c02dbf84-2167-44ee-b639-723b58ba9aa0-00%40eu-central-1.amazonses.com.

Re: [Django] #35306: Localisation of dates very confusing - why can't it be turned off anymore?

2024-03-18 Thread Django

#35306: Localisation of dates very confusing - why can't it be turned off 
anymore?
-+-
 Reporter:  Richard  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  5.0
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  LANGUAGE_CODE,   | Triage Stage:
  DATE_FORMAT|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Richard):

 Replying to [comment:3 Natalia Bidart]:
 > Have you tried using the `formats.py` approach to solve your need?

 Hi Natalia - I've just tried this and it has worked - thanks! I guess
 you're right and this can be solved with doc updates.

 Personally I would still like the option to just turn this off, i.e.
 reinstate USE_L10N. You can turn translation off so why not allow
 localisation to be turned off too? I really don't understand the rationale
 for removing this setting in the first place.

 Best wishes.
-- 
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/0107018e520c8d0d-34375e9b-8137-44a3-91c0-9083b2eb6816-00%40eu-central-1.amazonses.com.

Re: [Django] #35306: Localisation of dates very confusing - why can't it be turned off anymore?

2024-03-18 Thread Django

#35306: Localisation of dates very confusing - why can't it be turned off 
anymore?
-+-
 Reporter:  Richard  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  5.0
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  LANGUAGE_CODE,   | Triage Stage:
  DATE_FORMAT|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Michael):

 Replying to [comment:2 Natalia Bidart]:
 > Thank you for your comment Michael, though it seems that your may be
 mixing `USE_L10N` with `USE_I18N`?

 Hi Natalia, oh apologies, thank you for clearing that up, cheers!
-- 
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/0107018e520934cb-32c6ee7e-c586-42f4-a1b6-e7b3a63c0900-00%40eu-central-1.amazonses.com.

Re: [Django] #35315: 5.0.3: pytest fails with tons of ImportErrors

2024-03-18 Thread Django

#35315: 5.0.3: pytest fails with tons of ImportErrors
+--
 Reporter:  Tomasz Kłoczko  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Uncategorized   |  Version:  5.0
 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 Tomasz Kłoczko):

 * Attachment "python-django.FAIL.txt.gz" added.

 Full pytest log
-- 
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/0107018e52063461-512e1bd7-e6c2-4b4e-8372-40cde66258e5-00%40eu-central-1.amazonses.com.

Re: [Django] #35314: Django 5 breaks value of Date field rendering correctly in template

2024-03-18 Thread Django

#35314: Django 5 breaks value of Date field rendering correctly in template
---+--
 Reporter:  Michael|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Forms  |  Version:  5.0
 Severity:  Normal |   Resolution:  duplicate
 Keywords:  form date  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Comment (by Michael):

 Replying to [comment:4 David Sanders]:
 > Yep you need to read the full comment:
 >
 > > Have you tried setting the DATE_FORMAT in your custom language format
 file as per: https://docs.djangoproject.com/en/5.0/topics/i18n/formatting
 /#creating-custom-format-files ?
 >
 > whereas you're using settings

 Thanks for the elaborating so I can try see it from your perspective. I
 can set a custom language format file, but surely when it comes to the
 HTML date value on forms, it should not depend on the language code, it
 should *always* be `/MM/DD`, anything else is invalid. So is it not a
 bug to make it depend on a custom format language code?
-- 
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/0107018e52014547-ffc98ca1-0f57-4962-a7f0-6ea68cc3e518-00%40eu-central-1.amazonses.com.

[Django] #35315: 5.0.3: pytest fails with tons of ImportErrors

2024-03-18 Thread Django

#35315: 5.0.3: pytest fails with tons of ImportErrors
--+
   Reporter:  Tomasz Kłoczko  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Uncategorized   |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   |
--+
 On testing I'm using python 3.9.18 and pytest 8.1.1.
 Looks like on scanning units pytest fails +500 errors like below

 {{{
  ERRORS
 
  ERROR collecting tests/admin_changelist/test_date_hierarchy.py
 
 ImportError while importing test module
 
'/home/tkloczko/rpmbuild/BUILD/django-5.0.3/tests/admin_changelist/test_date_hierarchy.py'.
 Hint: make sure your test modules/packages have valid Python names.
 Traceback:
 /usr/lib64/python3.9/importlib/__init__.py:127: in import_module
 return _bootstrap._gcd_import(name[level:], package, level)
 tests/admin_changelist/test_date_hierarchy.py:3: in 
 from django.contrib.admin.options import IncorrectLookupParameters
 ../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-
 packages/django/contrib/admin/__init__.py:2: in 
 from django.contrib.admin.filters import (
 ../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-
 packages/django/contrib/admin/filters.py:12: in 
 from django.contrib.admin.options import IncorrectLookupParameters
 ../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-
 packages/django/contrib/admin/options.py:10: in 
 from django import forms
 ../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-
 packages/django/forms/__init__.py:6: in 
 from django.forms.boundfield import *  # NOQA
 ../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-
 packages/django/forms/boundfield.py:4: in 
 from django.forms.utils import RenderableFieldMixin, pretty_name
 ../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-
 packages/django/forms/utils.py:6: in 
 from django.forms.renderers import get_default_renderer
 ../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-
 packages/django/forms/renderers.py:6: in 
 from django.template.backends.django import DjangoTemplates
 ../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-
 packages/django/template/__init__.py:44: in 
 from .engine import Engine
 ../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-
 packages/django/template/engine.py:7: in 
 from .base import Template
 ../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-
 packages/django/template/base.py:60: in 
 from django.utils.html import conditional_escape, escape
 ../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-
 packages/django/utils/html.py:11: in 
 from django.utils.encoding import punycode
 ../../BUILDROOT/python-django-5.0.3-4.fc36.x86_64/usr/lib/python3.9/site-
 packages/django/utils/encoding.py:5: in 
 from types import NoneType
 E   ImportError: cannot import name 'NoneType' from 'types'
 (/usr/lib64/python3.9/types.py)
 }}}
-- 
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/0107018e5200803a-a3c9f6fd-74d2-44aa-a683-448b32ebaad5-00%40eu-central-1.amazonses.com.

Re: [Django] #35314: Django 5 breaks value of Date field rendering correctly in template

2024-03-18 Thread Django

#35314: Django 5 breaks value of Date field rendering correctly in template
---+--
 Reporter:  Michael|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Forms  |  Version:  5.0
 Severity:  Normal |   Resolution:  duplicate
 Keywords:  form date  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Comment (by David Sanders):

 Yep you need to read the full comment:

 > Have you tried setting the DATE_FORMAT in your custom language format
 file as per: https://docs.djangoproject.com/en/5.0/topics/i18n/formatting
 /#creating-custom-format-files ?

 whereas you're using settings
-- 
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/0107018e51fd3fb8-9cc84a42-24c7-4b6b-a869-469256752bb0-00%40eu-central-1.amazonses.com.

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

2024-03-18 Thread Django

#35289: Chunked transfer encoding is not handled correctly by MultiPartParser
-+-
 Reporter:  Kyle Agronick|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  transfer-encoding,   | Triage Stage:  Accepted
  chunked, multi-part|
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
 * version:  5.0 => dev

Comment:

 Following Carlton's comment and the various links/issues, I think this is
 ticket should be accepted. Kyle, would you like to prepare a 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/0107018e51fd1029-b1e4b015-7ed4-4ff1-ab45-f123b1c5e9b7-00%40eu-central-1.amazonses.com.

Re: [Django] #35306: Localisation of dates very confusing - why can't it be turned off anymore?

2024-03-18 Thread Django

#35306: Localisation of dates very confusing - why can't it be turned off 
anymore?
-+-
 Reporter:  Richard  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  5.0
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  LANGUAGE_CODE,   | Triage Stage:
  DATE_FORMAT|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Natalia Bidart):

 Hello Richard, thank you for your report. I've been debugging your issue
 for a few days now. I think we may need to make some docs adjustments as
 you imply, but I do not think the code is broken. See as a references
 [https://stackoverflow.com/questions/77654801/use-l10n-deprecated-but-it-
 disables-datetime-input-formats-when-removed this post in stackoverflow].

 Have you tried using the `formats.py` approach to solve your need?
-- 
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/0107018e51eedb49-745e6250-3e50-45b2-a559-590b3edf3804-00%40eu-central-1.amazonses.com.

Re: [Django] #35314: Django 5 breaks value of Date field rendering correctly in template

2024-03-18 Thread Django

#35314: Django 5 breaks value of Date field rendering correctly in template
---+--
 Reporter:  Michael|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Forms  |  Version:  5.0
 Severity:  Normal |   Resolution:  duplicate
 Keywords:  form date  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Comment (by Michael):

 In #35255 the author recommends passing in the value of
 `settings.USE_L10N` ... which is deprecated. And in the thread you then
 recommend setting `DATE_FORMAT`, as mentioned above I have set
 `DATE_INPUT_FORMATS`, and they are not used.

 Would you please care to explain why this issue is invalid?
-- 
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/0107018e51ee0e3a-0e6c6944-d34d-43ac-8b18-186e15c4d1ed-00%40eu-central-1.amazonses.com.

Re: [Django] #35306: Localisation of dates very confusing - why can't it be turned off anymore?

2024-03-18 Thread Django

#35306: Localisation of dates very confusing - why can't it be turned off 
anymore?
-+-
 Reporter:  Richard  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  5.0
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  LANGUAGE_CODE,   | Triage Stage:
  DATE_FORMAT|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Natalia Bidart):

 Thank you for your comment Michael, though it seems that your may be
 mixing `USE_L10N` with `USE_I18N`?
-- 
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/0107018e51ecefd8-b7f9d09b-b01a-4224-8cf5-4c36f22b0419-00%40eu-central-1.amazonses.com.

Re: [Django] #35306: Localisation of dates very confusing - why can't it be turned off anymore?

2024-03-18 Thread Django

#35306: Localisation of dates very confusing - why can't it be turned off 
anymore?
-+-
 Reporter:  Richard  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  5.0
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  LANGUAGE_CODE,   | Triage Stage:
  DATE_FORMAT|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Michael):

 I agree and also miss the `USE_L10N` setting. Removing it feels like a
 large tech company that believes they know better than you, and force
 various changes without asking you to opt in. Unlike linux where it's the
 same, unless you wish to opt in.

 Anyways if `USE_L10N` is never coming back, we need to deprecate it
 properly, its still lurking in the code base, grepping to see where its
 used, with Django 5.0.3 shows:

 {{{
 utils/cache.py|340 col 17| if settings.USE_I18N:
 utils/cache.py|420 col 49| is_accept_language_redundant =
 settings.USE_I18N
 utils/translation/trans_null.py|3 col 12| # settings.USE_I18N = False can
 use this module rather than trans_real.py.
 utils/translation/reloader.py|13 col 17| if settings.USE_I18N:
 utils/translation/__init__.py|43 col 12| # settings.USE_I18N, as late as
 possible, so that modules can be imported
 utils/translation/__init__.py|54 col 5| USE_I18N will have no effect to
 which function is served upon request. If
 utils/translation/__init__.py|55 col 33| your tests rely on changing
 USE_I18N, you can delete all the functions
 utils/translation/__init__.py|66 col 21| if settings.USE_I18N:
 conf/global_settings.py|158 col 1| USE_I18N = True
 conf/project_template/project_name/settings.py-tpl|110 col 1| USE_I18N =
 True
 conf/urls/i18n.py|13 col 21| if not settings.USE_I18N:
 }}}
-- 
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/0107018e51e69052-4934116c-2895-44a7-8a6a-71be542bb21c-00%40eu-central-1.amazonses.com.

Re: [Django] #35314: Django 5 breaks value of Date field rendering correctly in template

2024-03-18 Thread Django

#35314: Django 5 breaks value of Date field rendering correctly in template
---+--
 Reporter:  Michael|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Forms  |  Version:  5.0
 Severity:  Normal |   Resolution:  duplicate
 Keywords:  form date  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by David Sanders):

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

Comment:

 Duplicate of 35255
-- 
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/0107018e51e0464b-3e68ea73-0b53-46cb-9f09-30ede89f3885-00%40eu-central-1.amazonses.com.

Re: [Django] #35314: Django 5 breaks value of Date field rendering correctly in template

2024-03-18 Thread Django

#35314: Django 5 breaks value of Date field rendering correctly in template
---+--
 Reporter:  Michael|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Forms  |  Version:  5.0
 Severity:  Normal |   Resolution:
 Keywords:  form date  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Description changed by Michael:

Old description:

> This used to work correctly in Django 4. Django 5 removed USE_L10N
> setting from settings.py
>
> When rendering an input field that is of type date:
> {{{
>   /home/michael/.venv/project/lib/python3.11/site-
> packages/django/forms/boundfield.py(108)as_widget()
> -> return widget.render(
>   /home/michael/.venv/project/lib/python3.11/site-
> packages/django/forms/widgets.py(279)render()
> -> context = self.get_context(name, value, attrs)
>   /home/michael/.venv/project/lib/python3.11/site-
> packages/django/forms/widgets.py(332)get_context()
> -> context = super().get_context(name, value, attrs)
>   /home/michael/.venv/project/lib/python3.11/site-
> packages/django/forms/widgets.py(271)get_context()
> -> "value": self.format_value(value),
>   /home/michael/.venv/project/lib/python3.11/site-
> packages/django/forms/widgets.py(555)format_value()
> -> value, self.format or formats.get_format(self.format_key)[0]
> }}}
>
> We that ` formats.get_format(self.format_key)` only passes in 1 argument
> to:
>
> {{{
> # django/utils/formats.py(109)get_format()
>
> def get_format(format_type, lang=None, use_l10n=None):
> """
> For a specific format type, return the format for the current
> language (locale). Default to the format in the settings.
> format_type is the name of the format, e.g. 'DATE_FORMAT'.
>
> If use_l10n is provided and is not None, it forces the value to
> be localized (or not), otherwise it's always localized.
> """
> if use_l10n is None:
> use_l10n = True
> if use_l10n and lang is None:
> lang = get_language()
> format_type = str(format_type)  # format_type may be lazy.
> cache_key = (format_type, lang)
> try:
> return _format_cache[cache_key]
> except KeyError:
> pass
> }}}
>
> this means use_l10n initial value is `None`, which means it will be set
> to True via the logic:
> {{{
> if use_l10n is None:
> use_l10n = True
> }}}
>
> So then it sets a language, in my case `en-gb`, which makes results in a
> `cache_key` of `('DATE_INPUT_FORMATS', 'en-gb')`
>
> Which means the `get_format` method returns `['%d/%m/%Y', '%d/%m/%y',
> '%Y-%m-%d']`
> Which is really bad when `format_type = 'DATE_INPUT_FORMATS'`, because
> HTML inputs must always be in the format `/MM/DD`, and hence
> selecting the first format of `%d/%m/%Y` results in an error in your HTML
> template when your input is rendered like ` value="31/12/2024">` instead of  ``
>

> Not that it changes anything, but here is my `DATE_INPUT_FORMATS` from
> settings.py (it has no `USE_L10N` setting as unfortunately that has been
> removed):
> {{{
> DATE_INPUT_FORMATS = [
> '%Y-%m-%d',
> ]
> }}}

New description:

 This used to work correctly in Django 4. Django 5 removed USE_L10N setting
 from settings.py

 When rendering an input field that is of type `date`:
 {{{
   /home/michael/.venv/project/lib/python3.11/site-
 packages/django/forms/boundfield.py(108)as_widget()
 -> return widget.render(
   /home/michael/.venv/project/lib/python3.11/site-
 packages/django/forms/widgets.py(279)render()
 -> context = self.get_context(name, value, attrs)
   /home/michael/.venv/project/lib/python3.11/site-
 packages/django/forms/widgets.py(332)get_context()
 -> context = super().get_context(name, value, attrs)
   /home/michael/.venv/project/lib/python3.11/site-
 packages/django/forms/widgets.py(271)get_context()
 -> "value": self.format_value(value),
   /home/michael/.venv/project/lib/python3.11/site-
 packages/django/forms/widgets.py(555)format_value()
 -> value, self.format or formats.get_format(self.format_key)[0]
 }}}

 We see that ` formats.get_format(self.format_key)` only passes in 1
 argument to:

 {{{
 # django/utils/formats.py(109)get_format()

 def get_format(format_type, lang=None, use_l10n=None):
 """
 For a specific format type, return the format for the current
 language (locale). Default to the format in the settings.
 format_type is the name of the format, e.g. 'DATE_FORMAT'.

 If use_l10n is provided and is not None, it forces the value to
 be localized (or not), otherwise it's always localized.
 """
 if use_l10n is None:
 use_l10n = True
 if use_l10n and lang is None:

[Django] #35314: Django 5 breaks value of Date field rendering correctly in template

2024-03-18 Thread Django

#35314: Django 5 breaks value of Date field rendering correctly in template
--+---
   Reporter:  Michael |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Forms   |Version:  5.0
   Severity:  Normal  |   Keywords:  form date
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+---
 This used to work correctly in Django 4. Django 5 removed USE_L10N setting
 from settings.py

 When rendering an input field that is of type date:
 {{{
   /home/michael/.venv/project/lib/python3.11/site-
 packages/django/forms/boundfield.py(108)as_widget()
 -> return widget.render(
   /home/michael/.venv/project/lib/python3.11/site-
 packages/django/forms/widgets.py(279)render()
 -> context = self.get_context(name, value, attrs)
   /home/michael/.venv/project/lib/python3.11/site-
 packages/django/forms/widgets.py(332)get_context()
 -> context = super().get_context(name, value, attrs)
   /home/michael/.venv/project/lib/python3.11/site-
 packages/django/forms/widgets.py(271)get_context()
 -> "value": self.format_value(value),
   /home/michael/.venv/project/lib/python3.11/site-
 packages/django/forms/widgets.py(555)format_value()
 -> value, self.format or formats.get_format(self.format_key)[0]
 }}}

 We that ` formats.get_format(self.format_key)` only passes in 1 argument
 to:

 {{{
 # django/utils/formats.py(109)get_format()

 def get_format(format_type, lang=None, use_l10n=None):
 """
 For a specific format type, return the format for the current
 language (locale). Default to the format in the settings.
 format_type is the name of the format, e.g. 'DATE_FORMAT'.

 If use_l10n is provided and is not None, it forces the value to
 be localized (or not), otherwise it's always localized.
 """
 if use_l10n is None:
 use_l10n = True
 if use_l10n and lang is None:
 lang = get_language()
 format_type = str(format_type)  # format_type may be lazy.
 cache_key = (format_type, lang)
 try:
 return _format_cache[cache_key]
 except KeyError:
 pass
 }}}

 this means use_l10n initial value is `None`, which means it will be set to
 True via the logic:
 {{{
 if use_l10n is None:
 use_l10n = True
 }}}

 So then it sets a language, in my case `en-gb`, which makes results in a
 `cache_key` of `('DATE_INPUT_FORMATS', 'en-gb')`

 Which means the `get_format` method returns `['%d/%m/%Y', '%d/%m/%y',
 '%Y-%m-%d']`
 Which is really bad when `format_type = 'DATE_INPUT_FORMATS'`, because
 HTML inputs must always be in the format `/MM/DD`, and hence selecting
 the first format of `%d/%m/%Y` results in an error in your HTML template
 when your input is rendered like ``
 instead of  ``


 Not that it changes anything, but here is my `DATE_INPUT_FORMATS` from
 settings.py (it has no `USE_L10N` setting as unfortunately that has been
 removed):
 {{{
 DATE_INPUT_FORMATS = [
 '%Y-%m-%d',
 ]
 }}}
-- 
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/0107018e51da8688-d5dc3392-5448-49dc-b22e-20c7a5cdd919-00%40eu-central-1.amazonses.com.

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

2024-03-18 Thread 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 Carlton Gibson):

 This [https://github.com/django/daphne/issues/476#issuecomment-1557267731
 comment on the related request-centred Daphne issue] suggests that that
 request body is correctly dechunked before being passed off to Django. The
 question we had there was "why it's not getting out of Django's
 `HttpRequest._load_post_and_files()`" Kyle's suggestion looks on point:
 the missing content length isn't an error (IIUC).

 I'd guess here we'd would set expected content length to
 `len(request.body)` if the Transfer-Encoding header field was set 樂
-- 
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/0107018e51b6e7a4-f71888e9-e908-4abf-a64d-244bec69cc81-00%40eu-central-1.amazonses.com.

Re: [Django] #34059: Validation of check constraints on JSONField key transforms with None produces invalid SQL on PostgreSQL.

2024-03-18 Thread Django

#34059: Validation of check constraints on JSONField key transforms with None
produces invalid SQL on PostgreSQL.
-+-
 Reporter:  Dan LaManna  |Owner:  David
 |  Sanders
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 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):

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

Comment:

 Fixed in 09ffc5c1212d4ced58b708cbbf3dfbfb77b782ca.
-- 
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/0107018e51a16b8c-d7762054-9ea5-4c18-9f91-524058a6f527-00%40eu-central-1.amazonses.com.

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

2024-03-18 Thread 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 bcail):

 > You can see in the ASGI spec mentioned in that ticket it says "a
 response that is given to the server with no Content-Length may be chunked
 as the server sees fit". Which is what is happening. Everything is
 streaming into Django correctly. It just doesn't know how to handle a non-
 existent content length.

 I actually understand that to be talking about responses coming *from*
 Django (or another ASGI app) back to the ASGI server, not a request going
 into Django.
-- 
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/0107018e519ef145-bd1403f5-3316-4fb4-86a5-bdff477189e6-00%40eu-central-1.amazonses.com.

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

2024-03-18 Thread 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
-+-
Changes (by Natalia Bidart):

 * cc: Carlton Gibson (added)

Comment:

 Hello Kyle!

 [https://datatracker.ietf.org/doc/html/rfc2616#section-4.4 RFC 2616] is
 obsoleted by [https://datatracker.ietf.org/doc/html/rfc7230 RFC 7230]
 which in turn is obsoleted by RFC 9110 and RFC 9112, and as far as I read
 in [https://datatracker.ietf.org/doc/html/rfc9112#message.body RFC 9112],
 both headers could co-exist (but `Content-Length` should be ignored if
 `Transfer-Encoding` is sent):

 > Early implementations of Transfer-Encoding would occasionally send both
 a chunked transfer coding for message framing and an estimated Content-
 Length header field for use by progress bars. This is why Transfer-
 Encoding is defined as overriding Content-Length, as opposed to them being
 mutually incompatible.

 But, at the same time, I found an analogous issue for
 [https://github.com/django/daphne/issues/371 Daphne], and I see that you
 have just commented on the other referenced Daphne issue, so this may be a
 valid issue. I will cc/Carlton to confirm before fully triaging.
-- 
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/0107018e5197f137-62bfab67-42b8-408a-81e6-a65dd6036908-00%40eu-central-1.amazonses.com.

Re: [Django] #35308: FileNotFoundError escapes from run_formatters()

2024-03-18 Thread Django

#35308: FileNotFoundError escapes from run_formatters()
---+--
 Reporter:  Jacob Walls|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  4.2
 Severity:  Normal |   Resolution:
 Keywords:  black  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Comment (by Jacob Walls):

 My colleagues were developing on Macs. I just mentioned the Windows
 information when seeing it in the python docs.

 This isn't a solid reproducer, but I managed to hack together an example
 that at least fails to launch. Something else must be responsible for
 escaping the FileNotFoundError, since the call to subprocess.run does not
 include `check=True`. (I'm not saying this is how my colleagues reproduced
 it they had black installs from in abandoned environments, unsure what
 versions of pip, black, homebrew etc were used):

 {{{
 ~ % chmod 777 /opt/homebrew/bin/black
 ~ % chmod 644 /opt/homebrew/bin/black
 ~ % chmod +u /opt/homebrew/bin/black
 ~ % chmod -u /opt/homebrew/bin/black
 ~ % chmod +u /opt/homebrew/bin/black
 ~ % chmod +x /opt/homebrew/bin/black
 ~ % python3.12
 Python 3.12.0 (v3.12.0:0fb18b02c8, Oct  2 2023, 09:45:56) [Clang 13.0.0
 (clang-1300.0.29.30)] on darwin
 Type "help", "copyright", "credits" or "license" for more information.
 >>> import shutil
 >>> import subprocess
 >>> subprocess.run(shutil.which('black'))
 
/opt/homebrew/Cellar/python@3.11/3.11.5/Frameworks/Python.framework/Versions/3.11/Resources/Python.app/Contents/MacOS/Python:
 can't open file '/opt/homebrew/bin/black': [Errno 13] Permission denied
 CompletedProcess(args='/opt/homebrew/bin/black', returncode=2)
 }}}
-- 
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/0107018e518d16bc-d4958fc4-1ad8-456d-808f-6179090cacfc-00%40eu-central-1.amazonses.com.

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

2024-03-18 Thread Django

Replying to [comment:3 bcail]:
> [https://github.com/django/daphne/issues/476 This Daphne issue] may be
relevant. There's a quote in that issue (from the ASGI spec) that the ASGI
server is supposed to dechunk the request - so shouldn't it come to Django
as a regular (not chunked) request? Hopefully someone else will weigh in
here as well.
>
> What ASGI server are you using?

You can see in the ASGI spec mentioned in that ticket it says "a response
that is given to the server with no Content-Length may be chunked as the
server sees fit". Which is what is happening. Everything is streaming into
Django correctly. It just doesn't know how to handle a non-existent
content length.

That seems to be the same issue and I would argue this is a Django issue
as ASGI servers are streaming the results correctly. If the ASGI servers
were expected to buffer the files you would introduce blocking IO with
tempfiles or OOM issues if it all happened in memory. I came across this
issue while trying to implement large file uploads >6GB. The less
buffering the better.

I am using Daphene in development and Uvicorn in production. My hacky
middleware fix with the content-length seems to work on both of them.
--
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/0107018e518a3c1a-036cf008-c95f-4f18-b0b2-390329bbd3a4-00%40eu-central-1.amazonses.com.

Re: [Django] #7732: Oracle Backend with SessionPool

2024-03-18 Thread Django

#7732: Oracle Backend with SessionPool
-+-
 Reporter:  halturin |Owner:  Suraj
 |  Shaw
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  yandex-sprint| Triage Stage:  Accepted
  oracle session pool|
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/0107018e512d98a3-a65587c4-8be5-4031-9633-81e78fda9e76-00%40eu-central-1.amazonses.com.

Re: [Django] #31014: add FromWKB and FromWKT GIS functions

2024-03-18 Thread Django

#31014: add FromWKB and FromWKT GIS functions
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Claude
 |  Paroz
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  wkt, wkb | 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

-- 
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/0107018e5115f880-d56e954c-7ba6-4fe9-a3b3-accf0bef9123-00%40eu-central-1.amazonses.com.

Re: [Django] #31014: add FromWKB and FromWKT GIS functions

2024-03-18 Thread Django

#31014: add FromWKB and FromWKT GIS functions
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Claude
 |  Paroz
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  wkt, wkb | 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:"10b31eea337261ba724a71839ebc4bd4ddac3675" 10b31ee]:
 {{{#!CommitTicketReference repository=""
 revision="10b31eea337261ba724a71839ebc4bd4ddac3675"
 Refs #31014 -- Added srid argument to FromWKB/FromWKT() GIS functions.
 }}}
-- 
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/0107018e5115954f-5c8d0ade-3536-4a61-bdbf-b5de0bdc134d-00%40eu-central-1.amazonses.com.

Re: [Django] #35308: FileNotFoundError escapes from run_formatters()

2024-03-18 Thread Django

#35308: FileNotFoundError escapes from run_formatters()
---+--
 Reporter:  Jacob Walls|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  4.2
 Severity:  Normal |   Resolution:
 Keywords:  black  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Comment (by Mariusz Felisiak):

 I cannot reproduce it on Linux. Is it Windows-specific issue? Did you
 manage to reproduce it? Is not this an issue in Python instead?
-- 
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/0107018e50f6283a-38c15c19-f596-45ac-9ac7-25dea46f3543-00%40eu-central-1.amazonses.com.

Re: [Django] #25068: Metaclass conflict when doing createmigrations in ModelState.render

2024-03-18 Thread Django

#25068: Metaclass conflict when doing createmigrations in ModelState.render
-+-
 Reporter:  kosz85   |Owner:  Tom L.
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  metaclass conflict   | Triage Stage:  Accepted
  createmigrations   |
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/0107018e50de3fe4-0f25b133-60e7-4cac-9174-6edd8f1d6b27-00%40eu-central-1.amazonses.com.

Re: [Django] #23521: removal of concrete Model from bases doesn't remove it from ModelState bases

2024-03-18 Thread Django

#23521: removal of concrete Model from bases doesn't remove it from ModelState
bases
-+
 Reporter:  Sergey Fedoseev  |Owner:  Tom L.
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  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/0107018e50de1aba-ce93f3f6-ab1b-40c7-8fbc-14306b03918f-00%40eu-central-1.amazonses.com.

Re: [Django] #34943: Support passing unique constraint names to bulk_create().

2024-03-18 Thread Django

#34943: Support passing unique constraint names to bulk_create().
-+-
 Reporter:  Alex Vandiver|Owner:  HAMA
 |  Barhamou
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  bulk insert update   | Triage Stage:  Accepted
  upsert |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by HAMA Barhamou):

 * owner:  (none) => HAMA Barhamou
 * status:  new => assigned

Comment:

 I will make a proposal to work on the ticket for GSoC 2024.
-- 
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/0107018e50dcb4a0-f891c3e2-df11-447e-935a-8d77d68a4456-00%40eu-central-1.amazonses.com.

Re: [Django] #31014: add FromWKB and FromWKT GIS functions

2024-03-18 Thread Django

#31014: add FromWKB and FromWKT GIS functions
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Claude
 |  Paroz
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  wkt, wkb | 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/0107018e50da6546-8b0b725a-824d-4af5-8dc9-ef26f8a9714a-00%40eu-central-1.amazonses.com.

Re: [Django] #20551: Duplicate fixture labels

2024-03-18 Thread Django

#20551: Duplicate fixture labels
-+-
 Reporter:  Anssi Kääriäinen |Owner:  nobody
 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:  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/0107018e50731bc3-38c9eb2e-2c16-4172-a734-3eb8525cca07-00%40eu-central-1.amazonses.com.

Re: [Django] #21286: Fix commented out tests in serializers.test_data

2024-03-18 Thread Django

#21286: Fix commented out tests in serializers.test_data
--+
 Reporter:  Tim Graham|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Serialization)  |  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/0107018e5072cc68-946c5158-3b37-4819-b289-324d1e1da282-00%40eu-central-1.amazonses.com.

Re: [Django] #25594: Difficult to customize model field default_validators and have them used on both model and form fields

2024-03-18 Thread Django

#25594: Difficult to customize model field default_validators and have them 
used on
both model and form fields
-+-
 Reporter:  Marcin Nowak |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:  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/0107018e507191e6-960bc76b-104e-4c0e-9464-8341430599ba-00%40eu-central-1.amazonses.com.

Re: [Django] #25782: Discourage usage of cache_page decorator with UpdateCacheMiddleware (or make middleware ignore decorated views)

2024-03-18 Thread Django

#25782: Discourage usage of cache_page decorator with UpdateCacheMiddleware (or
make middleware ignore decorated views)
--+
 Reporter:  Serhiy|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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/0107018e5070f39b-3c825764-aff4-4e4a-80d5-7660619298c1-00%40eu-central-1.amazonses.com.

Re: [Django] #35233: Push templates checks down to backend engine classes

2024-03-18 Thread Django

#35233: Push templates checks down to backend engine classes
-+-
 Reporter:  Adam Johnson |Owner:  Giannis
 Type:   |  Terzopoulos
  Cleanup/optimization   |   Status:  assigned
Component:  Core (System |  Version:  dev
  checks)|
 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/0107018e50705445-70c6e79d-4b50-47e5-872f-c12481e0fce7-00%40eu-central-1.amazonses.com.

Re: [Django] #25762: Optimize numberformat.format

2024-03-18 Thread Django

#25762: Optimize numberformat.format
--+
 Reporter:  Jaap Roes |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Utilities |  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/0107018e50703a12-49ae8fc7-746c-4765-b5d5-1a44f2cbe8de-00%40eu-central-1.amazonses.com.

Re: [Django] #25705: Parameters are not adapted or quoted in Query.str

2024-03-18 Thread Django

#25705: Parameters are not adapted or quoted in Query.__str__
-+-
 Reporter:  Dmitry Dygalo|Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
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:  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/0107018e506fda2b-4cdc8914-e627-4e7f-bae5-a96a63d825a8-00%40eu-central-1.amazonses.com.

Re: [Django] #25701: Add warning to an admin list_view if too many queries are being used

2024-03-18 Thread Django

#25701: Add warning to an admin list_view if too many queries are being used
+
 Reporter:  Jacinda Shelly  |Owner:  (none)
 Type:  New feature |   Status:  new
Component:  contrib.admin   |  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/0107018e506f5665-530129f3-9127-4da3-ae55-11dc1ff584c8-00%40eu-central-1.amazonses.com.

Re: [Django] #26223: Squashing migrations with preserve_default=False keeps the default

2024-03-18 Thread Django

#26223: Squashing migrations with preserve_default=False keeps the default
-+
 Reporter:  Bartek Wójcicki  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Migrations   |  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/0107018e506ed0ca-b747de76-5094-436d-a46f-dfcca801e25c-00%40eu-central-1.amazonses.com.

Re: [Django] #26407: Investigate applying transitive reduction to migration graph.

2024-03-18 Thread Django

#26407: Investigate applying transitive reduction to migration graph.
-+-
 Reporter:  Jarek Glowacki   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  transitive   | Triage Stage:  Accepted
  reduction showmigrations   |
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/0107018e506df365-6194fe6c-0acb-4cab-8274-e9066b6c7c2e-00%40eu-central-1.amazonses.com.

Re: [Django] #20034: Upload handlers provide no way to retrieve previously parsed POST variables

2024-03-18 Thread Django

#20034: Upload handlers provide no way to retrieve previously parsed POST 
variables
---+
 Reporter:  rfkrocktk@…|Owner:  (none)
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  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/0107018e506d71af-73f178ab-4412-414c-8378-e92ccb84bb37-00%40eu-central-1.amazonses.com.

Re: [Django] #25540: Reusing databases doesn't work on PostgreSQL for migrations tests

2024-03-18 Thread Django

#25540: Reusing databases doesn't work on PostgreSQL for migrations tests
--+
 Reporter:  Anssi Kääriäinen  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Migrations|  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/0107018e506cc766-5ca5c3a5-16af-4d7a-9165-0686b6c7906f-00%40eu-central-1.amazonses.com.

Re: [Django] #25887: Clarify support for ForeignKey and form fields other than ModelChoiceField

2024-03-18 Thread Django

#25887: Clarify support for ForeignKey and form fields other than 
ModelChoiceField
-+-
 Reporter:  Miriam Gershenson|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  ModelForm,   | Triage Stage:  Accepted
  ForeignKey |
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/0107018e506c57b3-e5ef1007-70db-40b5-aa1e-341c0fa8fc28-00%40eu-central-1.amazonses.com.

Re: [Django] #25889: Organize tests in tests/queries

2024-03-18 Thread Django

#25889: Organize tests in tests/queries
--+
 Reporter:  Claude Paroz  |Owner:  (none)
 Type:  Cleanup/optimization  |   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/0107018e506c1c55-50a2c6c5-1ad0-472e-8dba-f560e9d24c1a-00%40eu-central-1.amazonses.com.

Re: [Django] #25902: Add system check for project-wide database table name conflicts

2024-03-18 Thread Django

#25902: Add system check for project-wide database table name conflicts
--+
 Reporter:  Amos Onn  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (System checks)  |  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/0107018e506a8f5c-dfdc228a-457f-42b0-9cbb-439ec7ed6ecc-00%40eu-central-1.amazonses.com.

Re: [Django] #25955: FK constraints are not checked at the end of nested atomic blocks

2024-03-18 Thread Django

#25955: FK constraints are not checked at the end of nested atomic blocks
-+-
 Reporter:  Artyem Klimenko  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  DEFERRED | Triage Stage:
  transaction.atomic savepoint   |  Someday/Maybe
  postgresql |
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/0107018e506a6b0c-5c950b93-5233-4ef2-9257-3d810aef43d8-00%40eu-central-1.amazonses.com.

Re: [Django] #25991: A new implementation for exclude() queries

2024-03-18 Thread Django

#25991: A new implementation for exclude() queries
-+-
 Reporter:  Anssi Kääriäinen |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  dev
  (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 Ü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/0107018e506a047c-6fd0643f-6966-4905-a098-ed4ffc91373f-00%40eu-central-1.amazonses.com.

Re: [Django] #25857: DateTimeShortcuts.js could try and consume all DATE_INPUT_FORMATS.

2024-03-18 Thread Django

#25857: DateTimeShortcuts.js could try and consume all DATE_INPUT_FORMATS.
---+
 Reporter:  Keryn Knight   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords:  calendar   | 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/0107018e50698a31-19080552-6ee4-4c12-bc7d-a28a1de85323-00%40eu-central-1.amazonses.com.

Re: [Django] #25703: Create topic documentation for Expressions

2024-03-18 Thread Django

#25703: Create topic documentation for Expressions
--+
 Reporter:  Mikey Ariel   |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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/0107018e50692c01-2c788a5f-a54a-4923-b1d2-bfd3a03595ec-00%40eu-central-1.amazonses.com.

Re: [Django] #24342: Add EnumField model/form fields

2024-03-18 Thread Django

#24342: Add EnumField model/form fields
-+-
 Reporter:  Thomas Stephenson|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 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/0107018e5068b395-7c32ddad-faf2-4c99-84a0-41737dcef484-00%40eu-central-1.amazonses.com.

Re: [Django] #19898: Document why/when of class-based views

2024-03-18 Thread Django

#19898: Document why/when of class-based views
-+
 Reporter:  Steven Cummings  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  docs sprint2013  | 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/0107018e506790ec-8df1ab72-4fc1-4ee6-9709-07911ec19525-00%40eu-central-1.amazonses.com.

Re: [Django] #19227: Reorganize method flowchart for class based generic views to tree

2024-03-18 Thread Django

#19227: Reorganize method flowchart for class based generic views to tree
--+
 Reporter:  shoul@…   |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:  docs  | 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/0107018e50673a70-973fdbfa-c6d8-4269-8897-fb9d58639617-00%40eu-central-1.amazonses.com.

Re: [Django] #15396: full path to modules in documentation inconsistently referenced

2024-03-18 Thread Django

#15396: full path to modules in documentation inconsistently referenced
---+
 Reporter:  slinkp@…   |Owner:  (none)
 Type:  Bug|   Status:  new
Component:  Documentation  |  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/0107018e5066a482-e17e5295-29a3-4de7-b4a3-7339dc6fd046-00%40eu-central-1.amazonses.com.

Re: [Django] #15220: replace SelectFilter2.js with a jQuery plugin

2024-03-18 Thread Django

#15220: replace SelectFilter2.js with a jQuery plugin
--+
 Reporter:  Nick Sandford |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  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:  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/0107018e5065f064-dee4051e-ad19-4538-951a-28f00763e32b-00%40eu-central-1.amazonses.com.

Re: [Django] #15179: django.test.client.Client.login fake HttpRequest is not run through middlewares

2024-03-18 Thread Django

#15179: django.test.client.Client.login fake HttpRequest is not run through
middlewares
---+
 Reporter:  Jari Pennanen  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  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/0107018e50652c1c-e06810f2-6fd4-447a-a7ac-463394689e41-00%40eu-central-1.amazonses.com.

Re: [Django] #14974: Add support for translation backends other than gettext

2024-03-18 Thread Django

#14974: Add support for translation backends other than gettext
--+
 Reporter:  Marinho Brandão   |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Internationalization  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  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/0107018e5064c6cf-0a95fe9a-74b4-4821-8091-77802b335e2f-00%40eu-central-1.amazonses.com.

Re: [Django] #15156: Ordinal numbers in English and in other locales

2024-03-18 Thread Django

#15156: Ordinal numbers in English and in other locales
--+
 Reporter:  Besnik  |Owner:  (none)
 Type:  New feature   |   Status:  new
Component:  Internationalization  |  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/0107018e50647a08-53b4bc7d-1a98-4edc-a85c-e027bb82e60e-00%40eu-central-1.amazonses.com.

Re: [Django] #33573: Add native async support to redis cache backend

2024-03-18 Thread Django

#33573: Add native async support to redis cache backend
-+-
 Reporter:  Christopher Bailey   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Cache system)  |  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/0107018e5063f301-48816ebf-3097-4889-abec-c47513db537d-00%40eu-central-1.amazonses.com.

Re: [Django] #33586: Cannot delete object (A) referenced by another object (B) if said object (A) has a foreign key to a custom user.

2024-03-18 Thread Django

#33586: Cannot delete object (A) referenced by another object (B) if said object
(A) has a foreign key to a custom user.
---+
 Reporter:  Jeremy Poulin  |Owner:  (none)
 Type:  Bug|   Status:  new
Component:  Migrations |  Version:  4.0
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Ü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/0107018e50639b39-6c24b55b-7189-4f23-aab7-bab9971ffe3b-00%40eu-central-1.amazonses.com.

Re: [Django] #32674: DEFAULT_AUTO_FIELD changes should be detected for PKs of auto-created intermediate M2M models.

2024-03-18 Thread Django

#32674: DEFAULT_AUTO_FIELD changes should be detected for PKs of auto-created
intermediate M2M models.
-+-
 Reporter:  Cristiano Coelho |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Migrations   |  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:  DEFAULT_AUTO_FIELD   | Triage Stage:  Accepted
  AutoField BigAutoField |
  ManyToManyField|
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/0107018e506300ba-d0aa6f28-3466-4840-8f5a-14af2d60d87c-00%40eu-central-1.amazonses.com.

Re: [Django] #32312: Performance decrease following implementation of ASGI handler and coroutine-safety.

2024-03-18 Thread Django

#32312: Performance decrease following implementation of ASGI handler and
coroutine-safety.
--+
 Reporter:  David Smith   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  3.0
 Severity:  Normal|   Resolution:
 Keywords:  async | 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/0107018e506280db-9d6e4a65-baae-47ca-bff5-1decfab6a6d5-00%40eu-central-1.amazonses.com.

Re: [Django] #26834: MinValueValidator/MaxValueValidator not forwarded to form field for ModelForm

2024-03-18 Thread Django

#26834: MinValueValidator/MaxValueValidator not forwarded to form field for
ModelForm
-+-
 Reporter:  Sergei Maertens  |Owner:  Tobias
 |  Kunze
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  MaxValueValidator,   | Triage Stage:  Accepted
  MinValueValidator, ModelForm,  |
  IntegerField   |
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/0107018e5061c3d0-df8fe260-8406-4fee-bf3c-70c9f2b2323d-00%40eu-central-1.amazonses.com.

Re: [Django] #21143: runtests might execute queries against the normal database instead of the testdatabase

2024-03-18 Thread Django

#21143: runtests might execute queries against the normal database instead of 
the
testdatabase
---+
 Reporter:  Florian Apolloner  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  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/0107018e506106f0-296c0869-8a9d-43ed-9baf-b14c0ffe0975-00%40eu-central-1.amazonses.com.

Re: [Django] #16774: Backtracking URL resolver

2024-03-18 Thread Django

#16774: Backtracking URL resolver
---+
 Reporter:  Nowell Strite  |Owner:  (none)
 Type:  New feature|   Status:  new
Component:  Core (URLs)|  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  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/0107018e5060c5f3-4b223dc4-76b7-400c-a10c-7edddfffacf4-00%40eu-central-1.amazonses.com.

Re: [Django] #27645: Move Settings.init checks to system checks

2024-03-18 Thread Django

#27645: Move Settings.__init__ checks to system checks
--+
 Reporter:  Adam Johnson  |Owner:  (none)
 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 Adam Johnson):

 948a874425e7d50a8fa3b6598d9e34a4b861 moved the `SECRET_KEY` validation
 so Tim’s comment no longer applies there.
-- 
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/0107018e505e17a2-df5525d9-bb1b-4a06-bef0-a495c9451041-00%40eu-central-1.amazonses.com.

Re: [Django] #26423: Make EmailValidator use HTML5 validation rather than more complicated regular expressions

2024-03-18 Thread Django

#26423: Make EmailValidator use HTML5 validation rather than more complicated
regular expressions
--+
 Reporter:  Tim Graham|Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  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/0107018e505dde81-a0b77411-42f9-4f48-b443-dfcc19bcd707-00%40eu-central-1.amazonses.com.

Re: [Django] #26565: Allow Prefetch query to use .values()

2024-03-18 Thread Django

#26565: Allow Prefetch query to use .values()
-+-
 Reporter:  Maxime Lorant|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  prefetch, 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 Ü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/0107018e505adb1e-e7c5125c-7253-4b5f-8c84-0878266e1fba-00%40eu-central-1.amazonses.com.

Re: [Django] #27447: Provide an easy way to test sending of signals

2024-03-18 Thread Django

#27447: Provide an easy way to test sending of signals
---+
 Reporter:  James Bennett  |Owner:  (none)
 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/0107018e505aa798-2a03a236-f81d-4b43-89f4-b8467dbb62a4-00%40eu-central-1.amazonses.com.

Re: [Django] #27620: Add a TransactionMiddleware

2024-03-18 Thread Django

#27620: Add a TransactionMiddleware
--+
 Reporter:  Tim Graham|Owner:  (none)
 Type:  New feature   |   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
--+
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/0107018e50592aec-24115d37-eef6-4918-8361-262616efc4c8-00%40eu-central-1.amazonses.com.

Re: [Django] #27645: Move Settings.init checks to system checks

2024-03-18 Thread Django

#27645: Move Settings.__init__ checks to system checks
--+
 Reporter:  Adam Johnson  |Owner:  (none)
 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
--+
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/0107018e5058acab-155703c0-d3f3-4608-a536-3e0313a16fd0-00%40eu-central-1.amazonses.com.

Re: [Django] #27747: Add signals for Django management commands

2024-03-18 Thread Django

#27747: Add signals for Django management commands
-+-
 Reporter:  Dmitry Gladkov   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  dev
  commands)  |
 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/0107018e50583e1b-4d66c9ed-9bac-47a5-9731-95389c294c99-00%40eu-central-1.amazonses.com.

Re: [Django] #27752: Fix and test admin_order_field set for the str of a model

2024-03-18 Thread Django

#27752: Fix and test admin_order_field set for the __str__ of a model
---+
 Reporter:  Claude Paroz   |Owner:  (none)
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  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/0107018e50577c82-3414d429-7392-4563-912f-068a1d039327-00%40eu-central-1.amazonses.com.

Re: [Django] #28250: Ignore soft applied migrations in consistency check

2024-03-18 Thread Django

#28250: Ignore soft applied migrations in consistency check
--+
 Reporter:  Brian May |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  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/0107018e5056d2b2-fbc1847f-a810-44ea-b843-ea43ac93cac4-00%40eu-central-1.amazonses.com.

1 2 >

1 - 100 of 114 matches

Mail list logo