Re: [Django] #35167: JSONField get_db_prep_value being called with `Cast` types

[Django]

#35167: JSONField get_db_prep_value being called with `Cast` types
-+-
 Reporter:  Samantha Hughes  |Owner:
 |  HeejunShin
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  JSONField| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by HeejunShin):

 Replying to [comment:23 Natalia Bidart]:
 > Hello HeejunShin, thank you for asking! You can take the time you need
 to work on this ticket, in general no ticket is urgent unless is a release
 blocker, which is not the case for this one.
 > Also, if you can't work on this anymore, that is also fine and you can
 just de-assign yourself from the ticket and eventually someone else would
 pick it up.
 >
 > Django is built and maintained by its community and everyone contributes
 their time and energy when they can.


 thank you for your response.
 I'll try my best.
-- 
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/0107018efead8700-1babd4a4-18d1-4b9b-a323-f12a84115356-00%40eu-central-1.amazonses.com.

Re: [Django] #18119: add DomainNameValidator to validate Internet Domain Names

[Django]

#18119: add DomainNameValidator to validate Internet Domain Names
--+
 Reporter:  michele   |Owner:  Nina Menezes
 Type:  New feature   |   Status:  assigned
Component:  Core (Other)  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:  validators| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Nina Menezes):

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

Comment:

 Documentation now updated.
-- 
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/0107018efd9c862e-c62aed32-4a83-44c8-b744-f01c44b4b720-00%40eu-central-1.amazonses.com.

Re: [Django] #35390: Missing BCC entry in message function.

[Django]

#35390: Missing BCC entry in message function.
--+--
 Reporter:  Antonio Morillas  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (Mail)   |  Version:
 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
--+--
Comment (by Antonio Morillas):

 OK.
-- 
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/0107018efd176025-0cb14453-2119-40c7-acf7-d50ce182822d-00%40eu-central-1.amazonses.com.

Re: [Django] #35166: Return python-memcached support

[Django]

#35166: Return python-memcached support
-+-
 Reporter:  Matej Spiller Muys   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Cache system)  |  Version:  5.0
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  memcached| Triage Stage:
  performance get_many   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Jochen Garcke):

 Besides the performance aspect, there is also the silenting of errors that
 python-memcached does, while the alternatives do not.

 Also somewhat related to this issue #33092, which also talks about
 threading issues and errors due to that.

 So at this time there is no drop-in replacement for the former default
 cache-backend that just works for everyone.

 In any case, thanks for the short code for the own backend, now the cache
 errors are silent again.
-- 
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/0107018efc87b634-d471c305-d6f4-4be6-8325-6b9ad1978e4b-00%40eu-central-1.amazonses.com.

Re: [Django] #35382: Remove unused CSS style `.inline-related fieldset.module h3`

[Django]

#35382: Remove unused CSS style `.inline-related fieldset.module h3`
--+
 Reporter:  Sarah Boyce   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  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
--+
Comment (by vinayaka314):

 I'm new here and I wanna help. Can anyone guide me, please?
-- 
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/0107018efc775199-382c23fc-cb77-4497-b2a7-d703a95cde5f-00%40eu-central-1.amazonses.com.

Re: [Django] #28900: QuerySet.values() and values_list() for compound queries fails with annotation.

[Django]

#28900: QuerySet.values() and values_list() for compound queries fails with
annotation.
-+-
 Reporter:  elliott-omosheye |Owner:  ontowhee
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  union, values| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by ontowhee):

 Replying to [comment:10 David Sanders]:

 Thanks for the simple example!

 I'm not too knowledgeable about the ORM, but I'm trying to work through
 this problem. Is the problem within annotate, or somewhere else, or a
 combination of annotate and something else?

 Using the simple example, I tried taking the union of Foo and Bar without
 any annotation, and I apply `.values('name')` to the result


 {{{
 Foo.objects.create(name='hello')
 Bar.objects.create(name='goodbye')

 qs = Foo.objects.all().union(Bar.objects.all())
 print(qs)
 }}}

 and it gives

 {{{
 
 }}}

 Which is correct and expected. However, when I remove `.values('name')`

 {{{
 qs = Foo.objects.all().union(Bar.objects.all())
 print(qs)
 }}}

 it then gives

 {{{
 , ]>
 }}}

 Is this expected, or is this something to look into?
-- 
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/0107018efc527c8b-b9b4991f-081d-49d0-ac71-1392515e8086-00%40eu-central-1.amazonses.com.

Re: [Django] #20744: Docs imply that forms.Field.__init__ accepts any keyword arguments

[Django]

#20744: Docs imply that forms.Field.__init__ accepts any keyword arguments
-+-
 Reporter:  Gunnlaugur Þór   |Owner:  Adam
  Briem  |  Zapletal
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  dev
 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 Adam Zapletal):

 * cc: Adam Zapletal (added)
 * has_patch:  0 => 1
 * owner:  nobody => Adam Zapletal
 * status:  new => assigned

Comment:

 I opened a simple pull request changing


 `.. class:: Field(**kwargs)`

 to

 `.. class:: Field`

 in the docs. That's how the `Form` class is documented.
-- 
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/0107018efc45b90f-726c5ddd-f656-473e-b6bc-1bd79e1f59d6-00%40eu-central-1.amazonses.com.

Re: [Django] #35306: Improve documentation for the various date format settings

[Django]

#35306: Improve documentation for the various date format settings
-+-
 Reporter:  Richard  |Owner:  Lufafa
 Type:   |  Joshua
  Cleanup/optimization   |   Status:  assigned
Component:   |  Version:  5.0
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  LANGUAGE_CODE,   | Triage Stage:  Accepted
  DATE_FORMAT|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Lufafa Joshua):

 * 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/0107018efc0d1dd9-ba1f831b-57f9-45a7-868b-762472cf6b11-00%40eu-central-1.amazonses.com.

Re: [Django] #35392: aprefetch_related_objects cannot be imported from django.db.models

[Django]

#35392: aprefetch_related_objects cannot be imported from django.db.models
-+-
 Reporter:  James Ostrander  |Owner:  James
 |  Ostrander
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  prefetch, async, | Triage Stage:  Ready for
  orm|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_docs:  1 => 0
 * 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/0107018efb81fc8f-2adb07a6-e508-4d62-8b0f-d250a18b5ddb-00%40eu-central-1.amazonses.com.