Re: [Django] #34480: Annotating with Chr raises ValueError

[Django]

#34480: Annotating with Chr raises ValueError
-+-
 Reporter:  Jacob Walls  |Owner:  Jacob
 |  Walls
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"c3d7a71f836f7cfe8fa90dd9ae95b37b660d5aae" c3d7a71f]:
 {{{
 #!CommitTicketReference repository=""
 revision="c3d7a71f836f7cfe8fa90dd9ae95b37b660d5aae"
 Fixed #34480 -- Fixed crash of annotations with Chr().
 }}}

-- 
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/010701876ede2438-6b47bd57-857b-42b5-8205-21d282766ae1-00%40eu-central-1.amazonses.com.

Re: [Django] #34478: django 4.2 admin page issue

[Django]

#34478: django 4.2 admin page issue
---+--
 Reporter:  ZorinArch  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  4.2
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+--
Changes (by Mariusz Felisiak):

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


Comment:

 Please don't reopen closed tickets without any context.

-- 
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/010701876edac9fa-5454b97a-e9f0-4e2e-829e-81f578ba7468-00%40eu-central-1.amazonses.com.

Re: [Django] #34478: django 4.2 admin page issue

[Django]

#34478: django 4.2 admin page issue
---+--
 Reporter:  ZorinArch  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  4.2
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+--
Changes (by Akshat verma):

 * status:  closed => new
 * resolution:  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/010701876ec2dab3-f323169c-b19a-4116-9b35-360dfd6bd3e3-00%40eu-central-1.amazonses.com.

Re: [Django] #32398: Excluding on annotations doesn't apply null handling.

[Django]

#32398: Excluding on annotations doesn't apply null handling.
-+-
 Reporter:  Gordon Wrigley   |Owner:  Jacob
 |  Walls
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (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 Mariusz Felisiak):

 * needs_better_patch:  0 => 1


Comment:

 Per Simon's
 [https://github.com/django/django/pull/16748#issuecomment-1502162075
 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/010701876e792cd4-d0c8026e-7b56-4897-aeaa-4796f70cee96-00%40eu-central-1.amazonses.com.

Re: [Django] #34480: Annotating with Chr raises ValueError

[Django]

#34480: Annotating with Chr raises ValueError
-+-
 Reporter:  Jacob Walls  |Owner:  Jacob
 |  Walls
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * stage:  Accepted => Ready for checkin


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701876e76bc9a-963af707-5001-44f2-92e1-0aff3588313f-00%40eu-central-1.amazonses.com.

Re: [Django] #34481: Admin check for reversed foreign key used in "list_display"

[Django]

#34481: Admin check for reversed foreign key used in "list_display"
+
 Reporter:  Natalia Bidart  |Owner:  nobody
 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 Mariusz Felisiak):

 * type:  Uncategorized => Bug
 * component:  Uncategorized => contrib.admin
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the report.

-- 
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/010701876e5c7b82-2fb4c29d-1260-44af-8198-da9cad0005b3-00%40eu-central-1.amazonses.com.

Re: [Django] #27505: Error messages customization and internationalization in Paginator class

[Django]

#27505: Error messages customization and internationalization in Paginator class
-+-
 Reporter:  Anton Bazhanov   |Owner:  Marcelo
 Type:   |  Galigniana
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Marcelo Galigniana):

 * needs_better_patch:  1 => 0
 * needs_docs:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701876de83ffd-d0063a91-6983-4c3a-890a-1b062a5b3f3f-00%40eu-central-1.amazonses.com.

Re: [Django] #34480: Annotating with Chr raises ValueError

[Django]

#34480: Annotating with Chr raises ValueError
-+-
 Reporter:  Jacob Walls  |Owner:  Jacob
 |  Walls
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jacob Walls):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/16750 PR]

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701876cdf5529-34498d47-fc91-4ef5-900b-c54225c3961a-00%40eu-central-1.amazonses.com.

[Django] #34481: Admin check for reversed foreign key used in "list_display"

[Django]

#34481: Admin check for reversed foreign key used in "list_display"
--+
   Reporter:  Natalia Bidart  |  Owner:  nobody
   Type:  Uncategorized   | Status:  new
  Component:  Uncategorized   |Version:  dev
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
 Currently the admin site checks and reports an `admin.E109` system check
 error when a `ManyToManyField` is declared within the `list_display`
 values.
 But, when a reversed foreign key is used there is no system error
 reported:

 {{{
 System check identified no issues (0 silenced).
 April 10, 2023 - 19:04:29
 Django version 5.0.dev20230410064954, using settings
 'projectfromrepo.settings'
 Starting development server at http://0.0.0.0:8000/
 Quit the server with CONTROL-C.
 }}}

 and visiting the admin site for the relevant model results in the
 following error:

 {{{
 TypeError:
 create_reverse_many_to_one_manager..RelatedManager.__call__()
 missing 1 required keyword-only argument: 'manager'
 [10/Apr/2023 19:30:40] "GET /admin/testapp/question/ HTTP/1.1" 500 415926
 }}}

 Ideally, using a reversed foreign key would also result in a system check
 error instead of a 500 response.

 To reproduce, follow the `Question` and `Choice` models from the Django
 Tutorial and add the following to the `QuestionAdmin`:

 {{{
 list_display = ["question_text", "choice_set"]
 }}}

 Then, visit `/admin/testapp/question/` and the following traceback is
 returned:

 {{{
 Internal Server Error: /admin/testapp/question/
 Traceback (most recent call last):
   File "/some/path/django/django/db/models/options.py", line 681, in
 get_field
 return self.fields_map[field_name]
~~~
 KeyError: 'choice_set'

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File "/some/path/django/django/contrib/admin/utils.py", line 288, in
 lookup_field
 f = _get_non_gfk_field(opts, name)
 ^^
   File "/some/path/django/django/contrib/admin/utils.py", line 319, in
 _get_non_gfk_field
 field = opts.get_field(name)
 
   File "/some/path/django/django/db/models/options.py", line 683, in
 get_field
 raise FieldDoesNotExist(
 django.core.exceptions.FieldDoesNotExist: Question has no field named
 'choice_set'

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File "/some/path/django/django/core/handlers/exception.py", line 55, in
 inner
 response = get_response(request)
^
   File "/some/path/django/django/core/handlers/base.py", line 220, in
 _get_response
 response = response.render()
^
   File "/some/path/django/django/template/response.py", line 111, in
 render
 self.content = self.rendered_content
^
   File "/some/path/django/django/template/response.py", line 89, in
 rendered_content
 return template.render(context, self._request)
^^^
   File "/some/path/django/django/template/backends/django.py", line 61, in
 render
 return self.template.render(context)
^
   File "/some/path/django/django/template/base.py", line 171, in render
 return self._render(context)
^
   File "/some/path/django/django/template/base.py", line 163, in _render
 return self.nodelist.render(context)
^
   File "/some/path/django/django/template/base.py", line 1001, in render
 return SafeString("".join([node.render_annotated(context) for node in
 self]))
 ^
   File "/some/path/django/django/template/base.py", line 1001, in
 
 return SafeString("".join([node.render_annotated(context) for node in
 self]))
^^
   File "/some/path/django/django/template/base.py", line 962, in
 render_annotated
 return self.render(context)

   File "/some/path/django/django/template/loader_tags.py", line 157, in
 render
 return compiled_parent._render(context)

   File "/some/path/django/django/template/base.py", line 163, in _render
 return self.nodelist.render(context)
^
   File "/some/path/django/django/template/base.py", line 1001, in render
 return 

Re: [Django] #10743: Support lookup separators in ModelAdmin.list_display

[Django]

#10743: Support lookup separators in ModelAdmin.list_display
-+-
 Reporter:  mrts |Owner:  Alex
 |  Garcia Ruiz de Oteiza
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  efficient-admin, | Triage Stage:  Accepted
  list_display   |
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Natalia Bidart):

 * needs_better_patch:  0 => 1
 * needs_tests:  0 => 1
 * needs_docs:  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/010701876c62a04e-2ee6db1c-915a-41f7-a218-6c0bf6c6bbd0-00%40eu-central-1.amazonses.com.

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

[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 David Sanders):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701876c1dfb1e-8ec00f37-d46e-4d46-8fce-99a41dd296a1-00%40eu-central-1.amazonses.com.

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

[Django]

#34479: Support "watchfiles" in the autoreloader
--+
 Reporter:  Tom Forbes|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  assigned
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 David Sanders):

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


Comment:

 Cool  Looks like a fair bit of support from the community to improve it,
 just need to determine what the improvement is?

 Are you going to assign yourself Tom?

-- 
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/010701876c1c8865-f826ac3c-cc5b-4f5b-89c2-d71e4d3796b0-00%40eu-central-1.amazonses.com.

Re: [Django] #34480: Annotating with Chr raises ValueError

[Django]

#34480: Annotating with Chr raises ValueError
-+-
 Reporter:  Jacob Walls  |Owner:  Jacob
 |  Walls
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * stage:  Unreviewed => Accepted


-- 
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/010701876c1a3149-c4f690d4-06dc-44b0-8d39-05204415562e-00%40eu-central-1.amazonses.com.

Re: [Django] #34480: Annotating with Chr raises ValueError

[Django]

#34480: Annotating with Chr raises ValueError
-+-
 Reporter:  Jacob Walls  |Owner:  Jacob
 |  Walls
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 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
-+-
Description changed by Jacob Walls:

Old description:

> {{{
> >>> Author.objects.annotate(first_letter=Chr(Value(77)))
> File "/Users/.../geoguard/.venv/lib/python3.9/site-
> packages/django/db/models/expressions.py", line 369, in 
> else int(value)
> ValueError: invalid literal for int() with base 10: 'M'
> }}}
>
> I'm suggesting in `Chr` we can set `output_field = CharField()` to
> prevent this.

New description:

 {{{
 >>> Author.objects.annotate(first_letter=Chr(Value(77)))
 File "/Users/.../.../.venv/lib/python3.9/site-
 packages/django/db/models/expressions.py", line 369, in 
 else int(value)
 ValueError: invalid literal for int() with base 10: 'M'
 }}}

 I'm suggesting in `Chr` we can set `output_field = CharField()` to prevent
 this.

--

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701876bc16242-00ff8bc2-e691-4caf-83e3-7174c1775795-00%40eu-central-1.amazonses.com.

[Django] #34480: Annotating with Chr raises ValueError

[Django]

#34480: Annotating with Chr raises ValueError
-+-
   Reporter:  Jacob  |  Owner:  Jacob Walls
  Walls  |
   Type:  Bug| Status:  assigned
  Component:  Database   |Version:  4.2
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 {{{
 >>> Author.objects.annotate(first_letter=Chr(Value(77)))
 File "/Users/.../geoguard/.venv/lib/python3.9/site-
 packages/django/db/models/expressions.py", line 369, in 
 else int(value)
 ValueError: invalid literal for int() with base 10: 'M'
 }}}

 I'm suggesting in `Chr` we can set `output_field = CharField()` to prevent
 this.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701876bc0f293-d70ca8d3-0649-495a-8b4e-803eb40b405c-00%40eu-central-1.amazonses.com.

Re: [Django] #34473: StepValueValidator does not take into account min_value

[Django]

#34473: StepValueValidator does not take into account min_value
--+--
 Reporter:  James Meakin  |Owner:  Jacob Rief
 Type:  Bug   |   Status:  assigned
Component:  Forms |  Version:  4.1
 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 Sarah Boyce):

 * has_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/010701876bbfadfd-3cce164a-c6df-4d94-ba2f-19d05b3b460c-00%40eu-central-1.amazonses.com.

Re: [Django] #34394: ASGIRequest doesn't respect settings.FORCE_SCRIPT_NAME.

[Django]

#34394: ASGIRequest doesn't respect settings.FORCE_SCRIPT_NAME.
--+---
 Reporter:  julyzergcn|Owner:  Sarah Boyce
 Type:  Bug   |   Status:  assigned
Component:  HTTP handling |  Version:  4.1
 Severity:  Normal|   Resolution:
 Keywords:  asgi SCRIPT_NAME  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+---
Changes (by Sarah Boyce):

 * owner:  Ayush Bisht => Sarah Boyce
 * has_patch:  0 => 1


Comment:

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

-- 
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/010701876bbcc092-50222c6b-d592-4325-84c6-a59cc04592b2-00%40eu-central-1.amazonses.com.

Re: [Django] #32398: Excluding on annotations doesn't apply null handling.

[Django]

#32398: Excluding on annotations doesn't apply null handling.
-+-
 Reporter:  Gordon Wrigley   |Owner:  Jacob
 |  Walls
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jacob Walls):

 * needs_better_patch:  1 => 0


Comment:

 [https://github.com/django/django/pull/16748 preliminary PR to add
 is_nullable()]

-- 
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/010701876baaee37-9e401127-03dd-4ccd-a49a-09c618da9001-00%40eu-central-1.amazonses.com.

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

[Django]

#34479: Support "watchfiles" in the autoreloader
---+--
   Reporter:  Tom Forbes   |  Owner:  nobody
   Type:  New feature  | Status:  assigned
  Component:  Utilities|Version:  4.2
   Severity:  Normal   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+--
 As per https://forum.djangoproject.com/t/the-future-of-the-watchman-
 autoreloader/19973, I believe we should drop support for the pywatchman
 autoreloader backend and switch to watchfiles. The current pywatchman
 implementation is broken.

 This should make it a bit easier to test, and the implementation seems
 like it will be simpler than our watchman implementation.

-- 
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/010701876b7fd692-68de9d81-e9c6-456e-bb7b-2e01a4b1a9d3-00%40eu-central-1.amazonses.com.

Re: [Django] #34455: i18n_patterns() not respecting prefix_default_language=False

[Django]

#34455: i18n_patterns() not respecting prefix_default_language=False
-+-
 Reporter:  Oussama Jarrousse|Owner:  Sarah
 |  Boyce
 Type:  Bug  |   Status:  closed
Component:   |  Version:  4.2
  Internationalization   |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
  internationalization, i18n,|  checkin
  prefix_default_language|
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:"facc153af7dc96ad83f1bfb86c92d41ec97aa14b" facc153]:
 {{{
 #!CommitTicketReference repository=""
 revision="facc153af7dc96ad83f1bfb86c92d41ec97aa14b"
 [4.2.x] Fixed #34455 -- Restored i18n_patterns() respect of
 prefix_default_language argument when fallback language is used.

 Regression in 94e7f471c4edef845a4fe5e3160132997b4cca81.

 Thanks Oussama Jarrousse for the report.

 Backport of 3b4728310a7a64f8fcc548163b0aa5f98a5c78f5 from main
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701876b6168d9-3fd72862-daf5-4c27-8fc8-3ffe20662a4c-00%40eu-central-1.amazonses.com.

Re: [Django] #34455: i18n_patterns() not respecting prefix_default_language=False

[Django]

#34455: i18n_patterns() not respecting prefix_default_language=False
-+-
 Reporter:  Oussama Jarrousse|Owner:  Sarah
 |  Boyce
 Type:  Bug  |   Status:  closed
Component:   |  Version:  4.2
  Internationalization   |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
  internationalization, i18n,|  checkin
  prefix_default_language|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"3b4728310a7a64f8fcc548163b0aa5f98a5c78f5" 3b47283]:
 {{{
 #!CommitTicketReference repository=""
 revision="3b4728310a7a64f8fcc548163b0aa5f98a5c78f5"
 Fixed #34455 -- Restored i18n_patterns() respect of
 prefix_default_language argument when fallback language is used.

 Regression in 94e7f471c4edef845a4fe5e3160132997b4cca81.

 Thanks Oussama Jarrousse for the report.
 }}}

-- 
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/010701876b60e513-85664503-17c3-4be4-9784-c648709f086e-00%40eu-central-1.amazonses.com.

Re: [Django] #16055: Filtering over generic relations with TextField/CharField object_id breaks in postgres

[Django]

#16055: Filtering over generic relations with TextField/CharField object_id 
breaks
in postgres
-+-
 Reporter:  anonymous|Owner:  David
 |  Wobrock
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  3.2
  contrib.contenttypes   |
 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 David Wobrock):

 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701876ae69c78-630f56c9-fa46-4fc0-949f-a88fa2d6c6c5-00%40eu-central-1.amazonses.com.

Re: [Django] #27505: Error messages customization and internationalization in Paginator class

[Django]

#27505: Error messages customization and internationalization in Paginator class
-+-
 Reporter:  Anton Bazhanov   |Owner:  Marcelo
 Type:   |  Galigniana
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1
 * needs_docs:  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/010701876acdcc56-c4b64baf-24d8-4170-9fe9-0df138c6c384-00%40eu-central-1.amazonses.com.

Re: [Django] #34455: i18n_patterns() not respecting prefix_default_language=False

[Django]

#34455: i18n_patterns() not respecting prefix_default_language=False
-+-
 Reporter:  Oussama Jarrousse|Owner:  Sarah
 |  Boyce
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  4.2
  Internationalization   |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
  internationalization, i18n,|  checkin
  prefix_default_language|
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/0107018769eeae50-3f08503b-26f5-4f23-865b-b65b0252c0c9-00%40eu-central-1.amazonses.com.