Re: [Django] #24121: Provide a better repr() experience

[Django]

#24121: Provide a better repr() experience
--+---
 Reporter:  Keryn Knight  |Owner:  Nrestrepo05
 Type:  New feature   |   Status:  assigned
Component:  Core (Other)  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+---
Changes (by Nrestrepo05):

 * owner:  nobody => Nrestrepo05
 * 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.5a38bd489f1114520683f3da7ff92648%40djangoproject.com.

Re: [Django] #25264: Misleading list of options available for manage.py commands

[Django]

#25264: Misleading list of options available for manage.py commands
-+-
 Reporter:  Maxime Lorant|Owner:  Edald123
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Core (Management |  Version:  dev
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Edald123):

 * owner:  nobody => Edald123
 * 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/065.7b00ef67ff25cb438564d8147ce18de9%40djangoproject.com.

Re: [Django] #30577: feature request: custom rendering for readonly fields in admin

[Django]

#30577: feature request: custom rendering for readonly fields in admin
---+--
 Reporter:  David  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  2.2
 Severity:  Normal |   Resolution:  needsinfo
 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 Florian Demmer):

 * cc: Florian Demmer (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/064.e8950f9df5b8923dd965f746aa53ef0a%40djangoproject.com.

Re: [Django] #32845: Names of uploaded files cannot be modified.

[Django]

#32845: Names of uploaded files cannot be modified.
-+-
 Reporter:  Jacob Fredericksen   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  File |  Version:  3.2
  uploads/storage|
 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 Bal Krishna Jha):

 You need to refer `model_instance` while changing the name.
 Replace `f.file.name`  with `model_instance.file.name` and it should work.

-- 
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.6744ffc1a37fd7edc940aa7994fdc40a%40djangoproject.com.

Re: [Django] #32798: StreamingHttpResponse raises SynchronousOnlyOperation in ASGI server

[Django]

#32798: StreamingHttpResponse raises SynchronousOnlyOperation in ASGI server
+-
 Reporter:  Ralph Broenink  |Owner:  Michael Brown
 Type:  Bug |   Status:  assigned
Component:  HTTP handling   |  Version:  3.2
 Severity:  Normal  |   Resolution:
 Keywords:  ASGI, async | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+-
Changes (by Michael Brown):

 * has_patch:  0 => 1


Comment:

 Created a pull request: https://github.com/django/django/pull/14526

-- 
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.64e12291a7d559312dfa0c3c9290474c%40djangoproject.com.

[Django] #32846: DateMixin.uses_datetime_field does not work when date_field is defined on a related model

[Django]

#32846: DateMixin.uses_datetime_field does not work when date_field is defined 
on a
related model
-+
   Reporter:  Jaap Roes  |  Owner:  nobody
   Type:  New feature| Status:  new
  Component:  Generic views  |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  |
-+
 Today I had the need to create a date based archive for a model that
 stores the date on a related model:

 {{{#!python
 class Bar(models.Model):
 date = models.DateField()

 class Foo(models.Model):
 bar = models.OneToOneField(Bar, on_delete=models.CASCADE)
 }}}

 with a view like this:

 {{{#!python
 class FooMonthArchiveView(MonthArchiveView):
 queryset = Foo.objects.all()
 date_field = "bar__date"
 }}}

 Django raises an error from `uses_datetime_field` because `bar__date`
 isn't a field on the `Foo` model.

 By overriding `uses_datetime_field` to just return `False` things seem to
 work just fine.

 I'll mark this as a new feature as it isn't explicitly documented that
 this should work, and hasn't worked for quite a while (for at least since
 whenever the `uses_datetime_field property` was introduced)

-- 
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/048.14d5f01f11b17dbd474094ead71192a9%40djangoproject.com.