Re: [Django] #30565: HttpResponseBase.close not called when using FileResponse / WSGI "file wrapper" object

[Django]

#30565: HttpResponseBase.close not called when using FileResponse / WSGI "file
wrapper" object
-+-
 Reporter:  Chris Jerdonek   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  HttpResponse,| Triage Stage:  Accepted
  streaming, StreamingHttpResponse   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Chris Jerdonek):

 Thanks, Johannes! I'll try to put together a patch as time permits.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.a19d83b13dc232eaa66c5f726015c9a2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30567: Start passing FileResponse.block_size to wsgi.file_wrapper. (was: Start passing FileResponse.block_size to wsgi.file_wrapper)

[Django]

#30567: Start passing FileResponse.block_size to wsgi.file_wrapper.
-+-
 Reporter:  Chris Jerdonek   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  block_size,wsgi.file_wrapper,FileResponse,wsgi|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * stage:  Unreviewed => Accepted


Comment:

 Seems reasonable, Thanks (see [https://modwsgi.readthedocs.io/en/develop
 /user-guides/file-wrapper-extension.html?highlight=block_size#example-of-
 wrapper-usage example-of-wrapper-usage]).

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.1bd67ac7780390c632842932b9700742%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30568: Definition of URLconf appears in tutorial 3; first mention is in tutorial 1. (was: Definition of URLconf appears in tutorial 3; first mention is in tutorial 1)

[Django]

#30568: Definition of URLconf appears in tutorial 3; first mention is in 
tutorial
1.
-+-
 Reporter:  Reuben Schmidt   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  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:  1|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  new => closed
 * version:  2.2 => master
 * resolution:   => wontfix


Comment:

 Thanks for the report, but I don't think that a clarification is required.
 Explanation from the 1st tutorial seems sufficient for the 1st step: ''"To
 call the view, we need to map it to a URL - and for this we need a
 URLconf."''

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.04a77254af839a026335c9a012c6c5b0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30570: Integrity errors in Django project with custom User model. (was: Integrity errors in Django project with custom User model)

[Django]

#30570: Integrity errors in Django project with custom User model.
+--
 Reporter:  siriuslan   |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:  worksforme
 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
 * type:  Uncategorized => Bug
 * component:  Uncategorized => Migrations
 * version:  2.2 => master
 * resolution:   => worksforme


Comment:

 Thanks for the report, however using a custom user model works for me.
 Please use one of
 [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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.b4812c8addf578aa9768fb63d0537a43%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30213: Add support for a "watchdog" based autoreloader

[Django]

#30213: Add support for a "watchdog" based autoreloader
-+
 Reporter:  Tom Forbes   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by Tom Forbes):

 Potential patch: https://github.com/django/django/pull/11480

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.3def5eef86a6b861500728b960fa6924%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30565: HttpResponseBase.close not called when using FileResponse / WSGI "file wrapper" object

[Django]

#30565: HttpResponseBase.close not called when using FileResponse / WSGI "file
wrapper" object
-+-
 Reporter:  Chris Jerdonek   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  HttpResponse,| Triage Stage:  Accepted
  streaming, StreamingHttpResponse   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Johannes Hoppe):

 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 I see, thanks for the clarification. I agree that either the documentation
 is wrong or the behavior is inconsistent.

 I suggest fixing the behavior as well. So please go ahead and wrap the
 file object. That seems to be in full agreement with PEP333.

 If you don't care to implement a patch, let me know. I am happy to write
 one myself.

 Oh, and fantastic catch. It always amazes me, what bugs people dig up.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.a5933763df9904a25de022c017da6567%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #10060: Multiple table annotation failure

[Django]

#10060: Multiple table annotation failure
-+-
 Reporter:  svsharma@…   |Owner:  (none)
 Type:  Bug  |   Status:  new
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 Antoine):

 * cc: Antoine (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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/081.539987ddb57366ccc3298c551642b025%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #30570: Integrity errors in Django project with custom User model

[Django]

#30570: Integrity errors in Django project with custom User model
-+
   Reporter:  siriuslan  |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  2.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  |
-+
 I am setting up a new django(version 2.2) project and want to use custom
 user model. When I load fixtures data, it failed with error like below:

 django.db.utils.IntegrityError: Problem installing fixtures: insert or
 update on table "doctors_doctor" violates foreign key constraint
 "doctors_doctor_user_ptr_id_ba968804_fk_doctors_user_id" DETAIL: Key
 (user_ptr_id)=(1) is not present in table "doctors_user".

 From django document -
 https://docs.djangoproject.com/en/2.2/topics/auth/customizing/#using-a
 -custom-user-model-when-starting-a-project I realized I did 'python
 manage.py migrate' before changing AUTH_USER_MODEL in settings.py. So I
 tried to delete all tables and redo 'python manage.py migrate', but it
 still hit this problem.

 I can see there is another ticket -
 https://code.djangoproject.com/ticket/23297 complaining the same issue, I
 follow the solution for it but not working. No idea why.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.a6e78db6c7c0e24562925ad60d285e59%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30569: Count and Sum annotation interfere with each other. (was: Count and Sum annotation interfere with each other in a QuerySet involving multiple relations)

[Django]

#30569: Count and Sum annotation interfere with each other.
-+-
 Reporter:  Antoine  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 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
 * version:  2.2 => master
 * resolution:   => duplicate


Comment:

 Duplicate of #10060 (see
 ​[https://docs.djangoproject.com/en/stable/topics/db/aggregation
 /#combining-multiple-aggregations documentation]).

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.d7b6a43ca12cc8611dc1777f3ba30a06%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30569: Count and Sum annotation interfere with each other in a QuerySet involving multiple relations

[Django]

#30569: Count and Sum annotation interfere with each other in a QuerySet 
involving
multiple relations
-+-
 Reporter:  Antoine  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.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
-+-

Comment (by Antoine):

 I can push the test project on Github if it is helpful -- let me know.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.c34c00357fbc6453f337029804aea2f4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #30569: Count and Sum annotation interfere with each other in a QuerySet involving multiple relations

[Django]

#30569: Count and Sum annotation interfere with each other in a QuerySet 
involving
multiple relations
-+-
   Reporter:  Antoine|  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  2.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  |
-+-
 While constructing a complex QuerySet, I ran into an issue where a Sum
 annotation on a relation would yield a different result whether or not
 another, seemingly unrelated Count annotation would be added. Everything
 needed to reproduce the issue is detailed here, including a dump of the
 database I used to illustrate the issue:

 https://stackoverflow.com/questions/56567841/django-count-and-sum-
 annotations-interfere-with-each-other

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/049.fc8ca7d843e550120904ecd903f15c3a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30557: order_by() a parent model crash when Meta.ordering contains expressions.

[Django]

#30557: order_by() a parent model crash when Meta.ordering contains expressions.
-+-
 Reporter:  Jonny Fuller |Owner:  Eran
 |  Keydar
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ordering | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Eran Keydar):

 * owner:  nobody => Eran Keydar
 * 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.6cd4d9e0a51b4f6a453c75424b03db20%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.