[Django] #35433: NumberInput off-by-one on min value for type range

[Django]

#35433: NumberInput off-by-one on min value for type range
--+
   Reporter:  mitch99 |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Forms   |Version:  5.0
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  1
  UI/UX:  0   |
--+
 Given this:


 {{{
 widgets = {
"weight": forms.NumberInput(attrs={'type':'range', 'step': '1', 'min':
 '1', 'max': '5'),
 }
 }}}


 I expect the min value on the range input to be 1, but it's actually 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/0107018f47345a53-11f7986e-3df3-4e21-beea-898beaf479f4-00%40eu-central-1.amazonses.com.

Re: [Django] #35429: Add argparse choices to --database options

[Django]

#35429: Add argparse choices to --database options
-+-
 Reporter:  Adam Johnson |Owner:  Jae Hyuck
 Type:   |  Sa
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Management |  Version:  dev
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Jae Hyuck Sa ):

 * needs_better_patch:  1 => 0

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018f46c08bb5-a2fb25ae-89ef-483c-979c-c19a84c7b782-00%40eu-central-1.amazonses.com.

Re: [Django] #35429: Add argparse choices to --database options

[Django]

#35429: Add argparse choices to --database options
-+-
 Reporter:  Adam Johnson |Owner:  Jae Hyuck
 Type:   |  Sa
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Management |  Version:  dev
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Comment (by Jae Hyuck Sa ):

 Replying to [comment:6 Adam Johnson]:
 As you told me, I applied them to the related database options.
-- 
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/0107018f46c012f7-cdf93240-a05e-472e-9700-fa6499a9b2fe-00%40eu-central-1.amazonses.com.

Re: [Django] #35414: Issue with AsyncClient ignoring default headers compared to synchronous Client

[Django]

#35414: Issue with AsyncClient ignoring default headers compared to synchronous
Client
-+-
 Reporter:  설원준(Wonjoon   |Owner:  nobody
  Seol)/Dispatch squad   |
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  5.0
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  AsyncClient, | Triage Stage:
  ASGIRequest|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by 설원준(Wonjoon Seol)/Dispatch squad):

 Hi Mariusz,

 Thanks for the documentation link. So the async client intended behaviour
 is inconsistent with the sync counterpart.

 But I should've mentioned in my original post that the headers field does
 not work neither.
 Because converting the above example test using headers argument still
 fails.

 {{{
 class EXAMPLE_TESTS(TestCase):
 async def test_should_return_ok( # FAILS
 self,
 ) -> None:
 async_client = AsyncClient(headers={"HTTP_AUTHORIZATION": f"Bearer
 I_AM_JWT_TOKEN"})

 response = await async_client.get(
 reverse("index"),
 )

 self.assertEqual(response.status_code, HTTPStatus.OK)

 async def test_should_return_ok2( # Passes
 self,
 ) -> None:
 async_client = AsyncClient()

 response = await async_client.get(
 reverse("index"),
 AUTHORIZATION=f"Bearer I_AM_JWT_TOKEN"
 )

 self.assertEqual(response.status_code, HTTPStatus.OK)
 }}}


 The reason is still due the the original post.


 {{{
 def _base_scope(self, **request):
 """The base scope for a request."""
 # This is a minimal valid ASGI scope, plus:
 # - headers['cookie'] for cookie support,
 # - 'client' often useful, see #8551.
 scope = {
 "asgi": {"version": "3.0"},
 "type": "http",
 "http_version": "1.1",
 "client": ["127.0.0.1", 0],
 "server": ("testserver", "80"),
 "scheme": "http",
 "method": "GET",
 "headers": [], # <- scope ignores default header
 **self.defaults,
 **request,
 }
 scope["headers"].append(
 (
 b"cookie",
 b"; ".join(
 sorted(
 ("%s=%s" % (morsel.key,
 morsel.coded_value)).encode("ascii")
 for morsel in self.cookies.values()
 )
 ),
 )
 )
 return scope
 }}}

 the scope only takes in default argument but ignores default header.

 Using the example test, this is the constructed META header after the
 initialization.
 The default headers are still missing:

 {{{
  {'REQUEST_METHOD': 'GET', 'QUERY_STRING': '', 'SCRIPT_NAME': '',
 'PATH_INFO': '/polls/', 'wsgi.multithread': True, 'wsgi.multiprocess':
 True, 'REMOTE_ADDR': '127.0.0.1', 'REMOTE_HOST': '127.0.0.1',
 'REMOTE_PORT': 0, 'SERVER_NAME': '127.0.0.1', 'SERVER_PORT': '80',
 'HTTP_HOST': 'testserver', 'HTTP_COOKIE': ''}
 }}}

 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/0107018f468dded2-194cd961-0ee4-4a2f-aa4e-ec09c91c3c14-00%40eu-central-1.amazonses.com.

Re: [Django] #35432: Usage of django new STORAGE added in version 4.2

[Django]

#35432: Usage of django new STORAGE added in version 4.2
-+-
 Reporter:  Ashwanth |Owner:  nobody
  Balakrishnan   |
 Type:  Uncategorized|   Status:  closed
Component:  File |  Version:  4.2
  uploads/storage|
 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:

 Hi Ashwanth,

 You've asked a question about using Django, however this forum is for bug
 reports and feature requests. Instead, you are likely to find someone who
 can help you in one of the
 [https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels
 support channels].
-- 
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/0107018f459f9fd8-b87f2560-1880-47e4-916e-8539dfc7ac1e-00%40eu-central-1.amazonses.com.

Re: [Django] #35425: .save(force_update=True) not respected for model instances with default primary keys

[Django]

#35425: .save(force_update=True) not respected for model instances with default
primary keys
-+-
 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:  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/18131 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/0107018f457d1020-3be0ca2e-24de-4f4a-b8f5-297cd204de41-00%40eu-central-1.amazonses.com.

Re: [Django] #35137: Collapsible error container elements do not indicate that they are interactive

[Django]

#35137: Collapsible error container elements do not indicate that they are
interactive
-+-
 Reporter:  Denis Anuschewski|Owner:  Abhijeet
 Type:   |  Singh
  Cleanup/optimization   |   Status:  assigned
Component:  Error reporting  |  Version:  dev
 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:  1
-+-
Comment (by Abhijeet Singh):

 Hay! I just opened a Discord Thred to discuss the Patch Improvement, I
 would appreciate if you checked it out
 (https://discordapp.com/channels/856567261900832808/1236418777323671633)
-- 
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/0107018f45729291-cdba77c6-4a0e-44a0-b1a4-2c5bca75fce1-00%40eu-central-1.amazonses.com.

Re: [Django] #35326: OverwritingStorageTests fail if a TemporaryUploadedFile is used

[Django]

#35326: OverwritingStorageTests fail if a TemporaryUploadedFile is used
--+
 Reporter:  bcail |Owner:  bcail
 Type:  Bug   |   Status:  assigned
Component:  File uploads/storage  |  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 Sarah Boyce):

 * 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/0107018f4466e64e-4f9d09a9-bd66-4c22-838f-fce37a5d808a-00%40eu-central-1.amazonses.com.

[Django] #35432: Usage of django new STORAGE added in version 4.2

[Django]

#35432: Usage of django new STORAGE added in version 4.2
-+
   Reporter:  Ashwanth Balakrishnan  |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  File uploads/storage   |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  |
-+
 https://github.com/jschneier/django-storages/issues/1393

 Is this the correct way of using storages in FileField ?

 And why does intellisense not pick this ?
 {{{#!python
   from django.core.files.storage import storages
   }}}
-- 
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/0107018f441ac45b-69d46cae-bb65-4056-a62f-fc9f75e653b1-00%40eu-central-1.amazonses.com.

Re: [Django] #35430: Documentation about timezone is misleading

[Django]

#35430: Documentation about timezone is misleading
--+
 Reporter:  younes-chaoui |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  5.0
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Sarah Boyce):

 * component:  Uncategorized => Documentation
 * easy:  0 => 1
 * stage:  Unreviewed => Accepted
 * type:  Uncategorized => Cleanup/optimization

Comment:

 Yes thank you!
 This is clearer further down in the "Time zone aware input in forms" and
 "Time zone aware output in templates" section.
 I recommend that `end user's time zone` is updated to {{{:ref:`default
 current time zone `}}} here.
-- 
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/0107018f43a8f7f1-10f6bfa4-dce7-4d38-8d94-6134cbd547c3-00%40eu-central-1.amazonses.com.

[Django] #35431: Failing to serialize NumericRange with CheckConstraint on IntegerRangeField

[Django]

#35431: Failing to serialize NumericRange with CheckConstraint on 
IntegerRangeField
--+
   Reporter:  Arran   |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Migrations  |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   |
--+
 I am trying to create a PostgreSQL check constraint on an
 `IntegerRangeField`, but when I run `makemigrations` I get the following
 error:

 {{{
 ValueError: Cannot serialize: Range(1, 1, '[)')
 There are some values Django cannot serialize into migration files.
 }}}

 Here's a simple example of my model which raises the error:

 {{{
 from django.contrib.postgres.fields import IntegerRangeField
 from django.db.backends.postgresql.psycopg_any import NumericRange
 from django.db import models
 from django.db.models.constraints import CheckConstraint
 from django.db.models.expressions import Q


 class MyModel(models.Model):
 price_range = IntegerRangeField()

 class Meta:
 constraints = [
 CheckConstraint(
 check=Q(price_range__contained_by=NumericRange(1, 1)),
 name="price_range_gt_1_and_lte_1",
 )
 ]
 }}}

 Judging by the following ticket this should work, so any help would be
 welcome:

 [https://code.djangoproject.com/ticket/30258]

 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/0107018f43a6a863-f7ead347-c8ac-4218-991d-3c2689b52eb4-00%40eu-central-1.amazonses.com.

[Django] #35430: Documentation about timezone is misleading

[Django]

#35430: Documentation about timezone is misleading
-+
   Reporter:  younes-chaoui  |  Owner:  nobody
   Type:  Uncategorized  | 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  |
-+
 Official documentation says :
 {{{
 When support for time zones is enabled, Django stores datetime information
 in UTC in the database, uses time-zone-aware datetime objects internally,
 and translates them to the end user’s time zone in templates and forms.
 }}}

 This is not True. In templates (including admin panel), Django uses
 TIME_ZONE setting instead of end user's timezone.
-- 
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/0107018f438dc049-8479df9d-fd26-4db1-b13e-612a83aeccee-00%40eu-central-1.amazonses.com.

Re: [Django] #35414: Issue with AsyncClient ignoring default headers compared to synchronous Client

[Django]

#35414: Issue with AsyncClient ignoring default headers compared to synchronous
Client
-+-
 Reporter:  설원준(Wonjoon   |Owner:  nobody
  Seol)/Dispatch squad   |
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  5.0
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  AsyncClient, | Triage Stage:
  ASGIRequest|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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

Comment:

 This works as expected and
 
[https://docs.djangoproject.com/en/5.0/topics/testing/tools/#django.test.AsyncClient
 documented]:

 ''"In the initialization, arbitrary keyword arguments in defaults are
 added directly into the ASGI scope."''

 If you want to add default headers you should pass them in the `headers`
 arguments.
-- 
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/0107018f43224466-413e4f5d-61cd-4086-abda-0342e36607e4-00%40eu-central-1.amazonses.com.

Re: [Django] #35429: Add argparse choices to --database options

[Django]

#35429: Add argparse choices to --database options
-+-
 Reporter:  Adam Johnson |Owner:  Jae Hyuck
 Type:   |  Sa
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Management |  Version:  dev
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Adam Johnson):

 * 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/0107018f43107875-a6ae3bfb-a83b-4bfa-85c4-466169214741-00%40eu-central-1.amazonses.com.

Re: [Django] #35426: `GenericPrefetch` should have `queryset` parameter as required

[Django]

#35426: `GenericPrefetch` should have `queryset` parameter as required
-+-
 Reporter:  Sobolev Nikita   |Owner:  Sobolev
 |  Nikita
 Type:  Bug  |   Status:  closed
Component:   |  Version:  5.0
  contrib.contenttypes   |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Sarah Boyce):

 * 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/0107018f42fc2c5f-5fe8a090-1608-4172-89a6-261bf31c625b-00%40eu-central-1.amazonses.com.

Re: [Django] #35426: `GenericPrefetch` should have `queryset` parameter as required

[Django]

#35426: `GenericPrefetch` should have `queryset` parameter as required
-+-
 Reporter:  Sobolev Nikita   |Owner:  Sobolev
 |  Nikita
 Type:  Bug  |   Status:  closed
Component:   |  Version:  5.0
  contrib.contenttypes   |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Comment (by Sarah Boyce <42296566+sarahboyce@…>):

 In [changeset:"9b5029f04851878923e04085591b29ee291718b6" 9b5029f0]:
 {{{#!CommitTicketReference repository=""
 revision="9b5029f04851878923e04085591b29ee291718b6"
 [5.0.x] Fixed #35426 -- Updated querysets to be a required argument of
 GenericPrefetch.

 Backport of 9a27c76021f934201cccf12215514a3091325ec8 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/0107018f42f4d765-b44d9ed1-c4c9-42a5-bb74-f4e14b36f72d-00%40eu-central-1.amazonses.com.

Re: [Django] #35426: `GenericPrefetch` should have `queryset` parameter as required

[Django]

#35426: `GenericPrefetch` should have `queryset` parameter as required
-+-
 Reporter:  Sobolev Nikita   |Owner:  Sobolev
 |  Nikita
 Type:  Bug  |   Status:  closed
Component:   |  Version:  5.0
  contrib.contenttypes   |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Sarah Boyce <42296566+sarahboyce@…>):

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

Comment:

 In [changeset:"9a27c76021f934201cccf12215514a3091325ec8" 9a27c760]:
 {{{#!CommitTicketReference repository=""
 revision="9a27c76021f934201cccf12215514a3091325ec8"
 Fixed #35426 -- Updated querysets to be a required argument of
 GenericPrefetch.
 }}}
-- 
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/0107018f42f0fe14-6ab553a0-3439-4808-99b7-3fcde9b03353-00%40eu-central-1.amazonses.com.

Re: [Django] #35429: Add argparse choices to --database options

[Django]

#35429: Add argparse choices to --database options
-+-
 Reporter:  Adam Johnson |Owner:
 Type:   |  saJaeHyukc
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Management |  Version:  dev
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Comment (by saJaeHyukc):

 [https://github.com/django/django/pull/18130]
-- 
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/0107018f42546102-f767878a-478b-4077-ba42-c0f5d6690248-00%40eu-central-1.amazonses.com.

Re: [Django] #35429: Add argparse choices to --database options

[Django]

#35429: Add argparse choices to --database options
-+-
 Reporter:  Adam Johnson |Owner:
 Type:   |  saJaeHyukc
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Management |  Version:  dev
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by saJaeHyukc):

 * 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/0107018f42539085-5b2964f5-82c3-4417-a176-223a2503f50a-00%40eu-central-1.amazonses.com.