Re: [Django] #31506: ExpressionWrapper() doesn't respect output_field when combining DateField and timedelta on PostgreSQL and MySQL.

[Django]

#31506: ExpressionWrapper() doesn't respect output_field when combining 
DateField
and timedelta on PostgreSQL and MySQL.
-+-
 Reporter:  Matthieu Rigal   |Owner:
 |  TapanGujjar
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (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 TapanGujjar):

 * owner:  nobody => TapanGujjar
 * 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/064.0d37a3336da87349022a39f60a2e14ce%40djangoproject.com.

Re: [Django] #9107: URL arguments to set values of fields in admin don't work for inlines

[Django]

#9107: URL arguments to set values of fields in admin don't work for inlines
---+---
 Reporter:  josh@… |Owner:  TapanGujjar
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin inline   | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+---

Comment (by TapanGujjar):

 Hi Carlton please check the pull request for this. I have created two
 tests to demonstrate my solutions. One of the test will fail.

 https://github.com/django/django/pull/12882

-- 
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/075.1e08f740270a1927aff5e2ad6097aca9%40djangoproject.com.

Re: [Django] #31548: URLValidator crashes on non-strings.

[Django]

#31548: URLValidator crashes on non-strings.
-+-
 Reporter:  Vasiliy Bondarenko   |Owner:  Yash
 |  Saini
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  3.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"ccb1cfb64e919e163c51995ed99bff3c92d7d006" ccb1cfb]:
 {{{
 #!CommitTicketReference repository=""
 revision="ccb1cfb64e919e163c51995ed99bff3c92d7d006"
 Fixed #31548 -- Fixed URLValidator crash on non-strings.
 }}}

-- 
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/076.1d1581c3f4d94649e6d0a7da8bd450d6%40djangoproject.com.

Re: [Django] #31550: AssertionError raised by test_file_response method of ASGITest class.

[Django]

#31550: AssertionError raised by test_file_response method of ASGITest class.
-+-
 Reporter:  Yash Saini   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  3.0
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  ASGI tests   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Yash Saini):

 I am using Windows 10 and python 3.7.7.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.88605e1e22b659eefebb69f80f987cb0%40djangoproject.com.

[Django] #31553: Incorrect query for inline admin when the parent is a proxy model

[Django]

#31553: Incorrect query for inline admin when the parent is a proxy model
-+
   Reporter:  Adam Duren |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  contrib.admin  |Version:  3.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  |
-+
 In our application we have a `ModelAdmin` which displays all rows and a
 special `ModelAdmin` which displays a subset of data available on the
 table (filtered rows) via the use of ProxyModel. The `ModelAdmin` contains
 an inline to a related model.

 We noticed that as our related table grew the time it took to render the
 one using a proxy model increased drastically. The non-proxy model detail
 page loads in sub-second where as the proxy model detail page takes over a
 minute.

 Upon further inspection we discovered through the use of `django-debug-
 toolbar` that the query which was being issued for the proxy model did not
 filter the related objects by the foreign key but instead retrieves all
 objects from the database.

 Below is an example which will reproduce the issue. You can easily verify
 by creating two users. Create 100K notifications and assign them to User
 A. Click on the detail for User B and observe that User B takes just as
 long as User A to load only when using the Proxy model.

 {{{#!python
 # models.py
 class User(models.Model):
 name = models.CharField()

 class UserProxy(User)
 class Meta:
 proxy = True

 class Notification(models.Model):
 user = models.ForeignKey("Person", models.CASCADE)
 text = models.CharField()

 # admin.py
 class NotificationAdmin(admin.TabularInline):
 model = Notification

 """
 Query for will be:

 SELECT *
 FROM "app_notification"
 WHERE app_notification"."user_id" = 'd0b44931-2d8d-4668-a74b-
 38b83ba9abf4'::uuid
 """
 class UserAdmin(admin.ModelAdmin):
 model = User

 """
 Query for will be:

 SELECT *
 FROM "app_notification"
 """
 class UserProxyAdmin(admin.ModelAdmin):
 model = UserProxy
 }}}

-- 
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/052.ca3371d13703a36399973d3918f4854f%40djangoproject.com.

Re: [Django] #31548: URLValidator crashes on non-strings. (was: URLValidator crashes on None, empty strings, and non-strings.)

[Django]

#31548: URLValidator crashes on non-strings.
-+-
 Reporter:  Vasiliy Bondarenko   |Owner:  Yash
 |  Saini
 Type:  Bug  |   Status:  assigned
Component:  Core (Other) |  Version:  3.0
 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 felixxm):

 * 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/076.cff623fd4ef975e20ebffadb3d9e6855%40djangoproject.com.

Re: [Django] #31551: TypeError: _bulk_create() got an unexpected keyword argument 'ignore_conflicts'. (was: TypeError: _bulk_create() got an unexpected keyword argument 'ignore_conflicts')

[Django]

#31551: TypeError: _bulk_create() got an unexpected keyword argument
'ignore_conflicts'.
-+-
 Reporter:  Shivam Chaurasia |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  Many-to-many Fields  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

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


Comment:

 Thanks for this ticket, however I cannot reproduce this issue, moreover
 `_bulk_create()` (with leading underscore) never existed in the Django.
 Can you provide a sample project to reproduce this issue?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.34efe800c08d9af04405f0da7b23a50d%40djangoproject.com.

Re: [Django] #31552: Loading lzma compressed fixtures

[Django]

#31552: Loading lzma compressed fixtures
-+-
 Reporter:  Paolo Melchiorre |Owner:  Paolo
 Type:   |  Melchiorre
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  fixtures | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

 * 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/067.85e9a77dbb6cebfa293c0d4186443810%40djangoproject.com.

Re: [Django] #31528: collectstatic doesn't run staticfiles checks.

[Django]

#31528: collectstatic doesn't run staticfiles checks.
-+-
 Reporter:  Keryn Knight |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  closed
Component:  contrib.staticfiles  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"87faeee4e0c0eb3937e2e575794f4512e513d214" 87faeee4]:
 {{{
 #!CommitTicketReference repository=""
 revision="87faeee4e0c0eb3937e2e575794f4512e513d214"
 Fixed #31528 -- Made collectstatic management command run staticfiles
 checks.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.8a139438489ad4f68b0f9011d9bbef33%40djangoproject.com.

Re: [Django] #27661: Move FileSystemFinder ImproperlyConfigured errors to system checks

[Django]

#27661: Move FileSystemFinder ImproperlyConfigured errors to system checks
-+-
 Reporter:  Jerome Leclanche |Owner:  Ling-Xiao
 Type:   |  Yang
  Cleanup/optimization   |   Status:  closed
Component:  contrib.staticfiles  |  Version:  1.10
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"b23e3a1caa10f824b6a0f8bbfaaab7fe53ac3abf" b23e3a1c]:
 {{{
 #!CommitTicketReference repository=""
 revision="b23e3a1caa10f824b6a0f8bbfaaab7fe53ac3abf"
 Refs #27661 -- Added Tags.staticfiles.

 Follow up to 0ec4dc91e0e7befdd06aa0613b5d0fbe3c785ee7.
 }}}

-- 
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/062.d7a95680711a882c9c978cf1bddf67ac%40djangoproject.com.

Re: [Django] #31552: Loading lzma compressed fixtures

[Django]

#31552: Loading lzma compressed fixtures
-+-
 Reporter:  Paolo Melchiorre |Owner:  Paolo
 Type:   |  Melchiorre
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  fixtures | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Paolo Melchiorre):

 * type:  New feature => 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/067.3ee3dd8e6491245a8106c10cfa6b5f13%40djangoproject.com.

Re: [Django] #31552: Loading lzma compressed fixtures

[Django]

#31552: Loading lzma compressed fixtures
-+-
 Reporter:  Paolo Melchiorre |Owner:  Paolo
 |  Melchiorre
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  fixtures | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Paolo Melchiorre):

 * cc: Paolo Melchiorre (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/067.654b23d37013f3f8ee0a0db18d4c7bb2%40djangoproject.com.

Re: [Django] #31552: Loading lzma compressed fixtures

[Django]

#31552: Loading lzma compressed fixtures
-+-
 Reporter:  Paolo Melchiorre |Owner:  Paolo
 |  Melchiorre
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  fixtures | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Paolo Melchiorre):

 * owner:  nobody => Paolo Melchiorre
 * status:  new => assigned


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.48443f5a3656f8503e3e725c89f7df55%40djangoproject.com.

Re: [Django] #31552: Loading lzma compressed fixtures

[Django]

#31552: Loading lzma compressed fixtures
-+-
 Reporter:  Paolo Melchiorre |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  fixtures | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Paolo Melchiorre):

 * has_patch:  0 => 1


Comment:

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

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.8d37f6779dd43089cb4cecf1c364528d%40djangoproject.com.

[Django] #31552: Loading lzma compressed fixtures

[Django]

#31552: Loading lzma compressed fixtures
-+-
   Reporter:  Paolo  |  Owner:  nobody
  Melchiorre |
   Type:  New| Status:  new
  feature|
  Component:  Core   |Version:  master
  (Management commands)  |
   Severity:  Normal |   Keywords:  fixtures
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Since `lzma` format is supported natively in Python 3 [1] from version
 3.3, I would propose to add `lzma` compressed fixtures (`.xz`) support in
 `loaddata` command.

 [1] https://docs.python.org/3/library/lzma.html

-- 
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/052.b1ffeb6d48047f242d9dc492b6cb3e4e%40djangoproject.com.

[Django] #31551: TypeError: _bulk_create() got an unexpected keyword argument 'ignore_conflicts'

[Django]

#31551: TypeError: _bulk_create() got an unexpected keyword argument
'ignore_conflicts'
-+-
   Reporter:  scshivam   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  3.0
  layer (models, ORM)|
   Severity:  Normal |   Keywords:  Many-to-many Fields
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Code:

 I get error in using .add() and .set() functions with many to many keys in
 models.
 I rolled back to Django-2.2.12 and this issue was gone.

 {{{
 class GroupSerializer(serializers.ModelSerializer):
 permissions = PermissionSerializerGroup(many=True, required=False)

 class Meta:
 model = Group
 fields = ('id', 'name', 'permissions')
 extra_kwargs = {
 'name': {'validators': []},
 }

 def create(self, validated_data):
 print(validated_data)
 permissions_data = validated_data.pop("permissions")
 obj, group =
 Group.objects.update_or_create(name=validated_data["name"])
 obj.permissions.clear()
 for permission in permissions_data:
 per = Permission.objects.get(codename=permission["codename"])
 obj.permissions.add(per)
 obj.save()
 return obj
 }}}


 Traceback:
 {{{
   File "/home/suman/Desktop/suman1234/myvenv/lib/python3.6/site-
 packages/django/core/handlers/exception.py", line 34, in inner
 response = get_response(request)
   File "/home/suman/Desktop/suman1234/myvenv/lib/python3.6/site-
 packages/django/core/handlers/base.py", line 115, in _get_response
 response = self.process_exception_by_middleware(e, request)
   File "/home/suman/Desktop/suman1234/myvenv/lib/python3.6/site-
 packages/django/core/handlers/base.py", line 113, in _get_response
 response = wrapped_callback(request, *callback_args,
 **callback_kwargs)
   File "/home/suman/Desktop/suman1234/myvenv/lib/python3.6/site-
 packages/django/contrib/admin/options.py", line 607, in wrapper
 return self.admin_site.admin_view(view)(*args, **kwargs)
   File "/home/suman/Desktop/suman1234/myvenv/lib/python3.6/site-
 packages/django/utils/decorators.py", line 130, in _wrapped_view
 response = view_func(request, *args, **kwargs)
   File "/home/suman/Desktop/suman1234/myvenv/lib/python3.6/site-
 packages/django/views/decorators/cache.py", line 44, in _wrapped_view_func
 response = view_func(request, *args, **kwargs)
   File "/home/suman/Desktop/suman1234/myvenv/lib/python3.6/site-
 packages/django/contrib/admin/sites.py", line 231, in inner
 return view(request, *args, **kwargs)
   File "/home/suman/Desktop/suman1234/myvenv/lib/python3.6/site-
 packages/django/contrib/admin/options.py", line 1638, in add_view
 return self.changeform_view(request, None, form_url, extra_context)
   File "/home/suman/Desktop/suman1234/myvenv/lib/python3.6/site-
 packages/django/utils/decorators.py", line 43, in _wrapper
 return bound_method(*args, **kwargs)
   File "/home/suman/Desktop/suman1234/myvenv/lib/python3.6/site-
 packages/django/utils/decorators.py", line 130, in _wrapped_view
 response = view_func(request, *args, **kwargs)
   File "/home/suman/Desktop/suman1234/myvenv/lib/python3.6/site-
 packages/django/contrib/admin/options.py", line 1522, in changeform_view
 return self._changeform_view(request, object_id, form_url,
 extra_context)
   File "/home/suman/Desktop/suman1234/myvenv/lib/python3.6/site-
 packages/django/contrib/admin/options.py", line 1566, in _changeform_view
 self.save_related(request, form, formsets, not add)
   File "/home/suman/Desktop/suman1234/myvenv/lib/python3.6/site-
 packages/django/contrib/admin/options.py", line 1107, in save_related
 form.save_m2m()
   File "/home/suman/Desktop/suman1234/myvenv/lib/python3.6/site-
 packages/django/forms/models.py", line 442, in _save_m2m
 f.save_form_data(self.instance, cleaned_data[f.name])
   File "/home/suman/Desktop/suman1234/myvenv/lib/python3.6/site-
 packages/django/db/models/fields/related.py", line 1618, in save_form_data
 getattr(instance, self.attname).set(data)
   File "/home/suman/Desktop/suman1234/myvenv/lib/python3.6/site-
 packages/django/db/models/fields/related_descriptors.py", line 1008, in
 set
 self.add(*new_objs, through_defaults=through_defaults)
   File "/home/suman/Desktop/suman1234/myvenv/lib/python3.6/site-
 packages/django/db/models/fields/related_descriptors.py", line 946, in add
 through_defaults=through_defaults,
   File "/home/suman/Desktop/suman1234/myvenv/lib/python3.6/site-
 

Re: [Django] #31550: AssertionError raised by test_file_response method of ASGITest class.

[Django]

#31550: AssertionError raised by test_file_response method of ASGITest class.
-+-
 Reporter:  Yash Saini   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  3.0
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  ASGI tests   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  new => closed
 * resolution:   => needsinfo
 * component:  Uncategorized => HTTP handling
 * type:  Uncategorized => Cleanup/optimization


Comment:

 Content-type depends on a platform. Jenkins doesn't report this issue on
 Windows and Linux. What platform and Python version are you using?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.4eb4c3dc353f1e6bebc43cd5fb369ddb%40djangoproject.com.

Re: [Django] #30678: Confirm support for GDAL 3.0.

[Django]

#30678: Confirm support for GDAL 3.0.
-+-
 Reporter:  Yury Ryabov  |Owner:  Claude
 Type:   |  Paroz
  Cleanup/optimization   |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  GDAL, GIS| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/12878 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/069.3ceb3d5b74741fea102c374188ad061c%40djangoproject.com.

[Django] #31550: AssertionError raised by test_file_response method of ASGITest class.

[Django]

#31550: AssertionError raised by test_file_response method of ASGITest class.
-+
   Reporter:  Yash Saini |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  3.0
   Severity:  Normal |   Keywords:  ASGI tests
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 On running:
 `python runtests.py asgi`
 The following assertion is raised in tests\asgi\tests.py in
 ASGITest.test_file_response method:
 {{{
 AssertionError: Items in the first set but not the second:
 (b'Content-Type', b'text/x-python')
 Items in the second set but not the first:
 (b'Content-Type', b'text/plain')
 }}}

-- 
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/056.6b94f357081aeabc0d2748dc124e9573%40djangoproject.com.

Re: [Django] #31549: Wrong results when executing QuerySet.query. (was: Diffrent result from connection)

[Django]

#31549: Wrong results when executing QuerySet.query.
-+-
 Reporter:  MrLawes  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 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 felixxm):

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


Old description:

> We have a class:
>
> from django.db.models import models
> class MyModel(models.Model):
> import_at = models.DateField( db_index=True, null=True,
> default=None,)
>
> then I can get some results by:
>
> queryset = MyModel.objects.filter(import_at__month=5,
> import_at__year=import_at[0])
> print(queryset.count())
> It will print  4
>
> but when I used connection, I got diffrent result:
>
> from django.db import transaction, connection
> with connection.cursor() as cursor:
> cursor.execute(queryset.query)
> print(len(cursor.fetchall()))
>
> It will print 0
>
> I got 0 !
>
> If I using __month or __year, and get result by
> cursor.execute(queryset.query), we have diffrent result from connection.

New description:

 We have a class:
 {{{
 from django.db.models import models
 class MyModel(models.Model):
 import_at = models.DateField( db_index=True, null=True, default=None,)
 }}}
 then I can get some results by:
 {{{
 queryset = MyModel.objects.filter(import_at__month=5,
 import_at__year=import_at[0])
 print(queryset.count())
 }}}
 It will print  4

 but when I used connection, I got diffrent result:
 {{{
 from django.db import transaction, connection
 with connection.cursor() as cursor:
 cursor.execute(queryset.query)
 print(len(cursor.fetchall()))
 }}}
 It will print 0

 I got 0 !

 If I using __month or __year, and get result by
 cursor.execute(queryset.query), we have diffrent result from connection.

--

Comment:

 `queryset.query` is a helper, it doesn't produce SQL that can be executed
 directly in a database console, see #25705.

-- 
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/065.69e1c103ef02d3dc94b6ee64b0d0c2ef%40djangoproject.com.

Re: [Django] #31544: Document input/output capturing utils in django.test.utils

[Django]

#31544: Document input/output capturing utils in django.test.utils
-+-
 Reporter:  Adam (Chainz)|Owner:  nobody
  Johnson|
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Adam (Chainz) Johnson):

 Thanks. I thought of that, I just get a bit shy about opening up Python
 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/068.e7edc91fa035e788e7e566158b1c825d%40djangoproject.com.

Re: [Django] #31549: Diffrent result from connection

[Django]

#31549: Diffrent result from connection
-+-
 Reporter:  MrLawes  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (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 MrLawes:

Old description:

> We have a class:
>
> from django.db.models import models
> class MyModel(models.Model):
> import_at = models.DateField( db_index=True, null=True,
> default=None,)
>
> then I can get some results by:
>
> queryset = MyModel.objects.filter(import_at__month=5,
> import_at__year=import_at[0])
> print(queryset.count())
> >>>  4
>
> but when I used connection, I got diffrent result:
>
> from django.db import transaction, connection
> with connection.cursor() as cursor:
> cursor.execute(queryset.query)
> print(len(cursor.fetchall()))
>
> >>> 0
>
> I got 0 !
>
> If I using __month or __year, and get result by
> cursor.execute(queryset.query), we have diffrent result from connection.

New description:

 We have a class:

 from django.db.models import models
 class MyModel(models.Model):
 import_at = models.DateField( db_index=True, null=True, default=None,)

 then I can get some results by:

 queryset = MyModel.objects.filter(import_at__month=5,
 import_at__year=import_at[0])
 print(queryset.count())
 It will print  4

 but when I used connection, I got diffrent result:

 from django.db import transaction, connection
 with connection.cursor() as cursor:
 cursor.execute(queryset.query)
 print(len(cursor.fetchall()))

 It will print 0

 I got 0 !

 If I using __month or __year, and get result by
 cursor.execute(queryset.query), we have diffrent result from connection.

--

-- 
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/065.1935c00916261564a488ec7382467e93%40djangoproject.com.

Re: [Django] #30678: Confirm support for GDAL 3.0.

[Django]

#30678: Confirm support for GDAL 3.0.
-+-
 Reporter:  Yury Ryabov  |Owner:  Claude
 Type:   |  Paroz
  Cleanup/optimization   |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  GDAL, GIS| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

 * owner:  nobody => Claude Paroz
 * 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/069.ae5c76ad9b57dd54739ad53100cdccfe%40djangoproject.com.

[Django] #31549: Diffrent result from connection

[Django]

#31549: Diffrent result from connection
-+-
   Reporter:  MrLawes|  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  2.0
  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  |
-+-
 We have a class:

 from django.db.models import models
 class MyModel(models.Model):
 import_at = models.DateField( db_index=True, null=True, default=None,)

 then I can get some results by:

 queryset = MyModel.objects.filter(import_at__month=5,
 import_at__year=import_at[0])
 print(queryset.count())
 >>>  4

 but when I used connection, I got diffrent result:

 from django.db import transaction, connection
 with connection.cursor() as cursor:
 cursor.execute(queryset.query)
 print(len(cursor.fetchall()))

 >>> 0

 I got 0 !

 If I using __month or __year, and get result by
 cursor.execute(queryset.query), we have diffrent result from connection.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.fe94f949a6aa2ef7c3c4f1ba62fbd3a3%40djangoproject.com.

Re: [Django] #31541: Improve documentation of django.contrib.redirects.

[Django]

#31541: Improve documentation of django.contrib.redirects.
-+-
 Reporter:  Adam (Chainz)|Owner:  Yash
  Johnson|  Saini
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.redirects|  Version:  master
 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 (Chainz) 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/068.bb2586bbe1e60a21cdc265f96788c472%40djangoproject.com.

Re: [Django] #31548: URLValidator crashes on None, empty strings, and non-strings.

[Django]

#31548: URLValidator crashes on None, empty strings, and non-strings.
+--
 Reporter:  Vasiliy Bondarenko  |Owner:  Yash Saini
 Type:  Bug |   Status:  assigned
Component:  Core (Other)|  Version:  3.0
 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 Yash Saini):

 * has_patch:  0 => 1


Comment:

 https://github.com/django/django/pull/12877 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/076.ef97726283dbeabc96631f14149c928c%40djangoproject.com.

Re: [Django] #31157: JSONField are not properly displayed in admin when they are readonly.

[Django]

#31157: JSONField are not properly displayed in admin when they are readonly.
---+
 Reporter:  Gagaro |Owner:  dbxnr
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  3.0
 Severity:  Normal |   Resolution:  fixed
 Keywords:  admin json | Triage Stage:  Accepted
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:"fc0f7f6c152766c92a95c74a02cc6fab79440ed8" fc0f7f6c]:
 {{{
 #!CommitTicketReference repository=""
 revision="fc0f7f6c152766c92a95c74a02cc6fab79440ed8"
 Fixed #31157 -- Fixed displaying read-only JSONField values in admin.
 }}}

-- 
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/064.d02c68a24b02618d9c4aafea647aba12%40djangoproject.com.

Re: [Django] #31157: JSONField are not properly displayed in admin when they are readonly.

[Django]

#31157: JSONField are not properly displayed in admin when they are readonly.
---+
 Reporter:  Gagaro |Owner:  dbxnr
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  3.0
 Severity:  Normal |   Resolution:
 Keywords:  admin json | Triage Stage:  Accepted
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:"675ce4dd35702ce353006611ba30799c0c4b015f" 675ce4d]:
 {{{
 #!CommitTicketReference repository=""
 revision="675ce4dd35702ce353006611ba30799c0c4b015f"
 Refs #31157 -- Added tests for display_for_field() with empty JSONField.
 }}}

-- 
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/064.a6d4d3338c3d154f017da40c94b2c0f9%40djangoproject.com.