Re: [Django] #35356: Issue with OneToOneField and recursive relationships in select_related() and only().

2024-04-05 Thread Django 
#35356: Issue with OneToOneField and recursive relationships in select_related()
and only().
-+-
 Reporter:  Joshua van Besouw|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 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 Simon Charette):

 * 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/0107018eb16f437e-54a7db2e-4cf6-4927-9f4b-c718ff3259a0-00%40eu-central-1.amazonses.com.

Re: [Django] #35356: Issue with OneToOneField and recursive relationships in select_related() and only().

2024-04-05 Thread Django 
#35356: Issue with OneToOneField and recursive relationships in select_related()
and only().
-+-
 Reporter:  Joshua van Besouw|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.2
  (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
-+-
Comment (by Simon Charette):

 #34612 could have fixed it but it took a different approach.
-- 
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/0107018eb1178b19-466db6f6-fbe6-4233-98de-832ef701817b-00%40eu-central-1.amazonses.com.

Re: [Django] #35356: Issue with OneToOneField and recursive relationships in select_related() and only().

2024-04-05 Thread Django 
#35356: Issue with OneToOneField and recursive relationships in select_related()
and only().
-+-
 Reporter:  Joshua van Besouw|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.2
  (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 Simon Charette):

 * stage:  Unreviewed => Accepted

Comment:

 {{{!diff
 diff --git a/tests/defer_regress/models.py b/tests/defer_regress/models.py
 index dd492993b7..38ba4a622f 100644
 --- a/tests/defer_regress/models.py
 +++ b/tests/defer_regress/models.py
 @@ -10,6 +10,12 @@ class Item(models.Model):
  text = models.TextField(default="xyzzy")
  value = models.IntegerField()
  other_value = models.IntegerField(default=0)
 +source = models.OneToOneField(
 +"self",
 +related_name="destination",
 +on_delete=models.CASCADE,
 +null=True,
 +)


  class RelatedItem(models.Model):
 diff --git a/tests/defer_regress/tests.py b/tests/defer_regress/tests.py
 index 10100e348d..d8b2186f0a 100644
 --- a/tests/defer_regress/tests.py
 +++ b/tests/defer_regress/tests.py
 @@ -309,6 +309,21 @@ def test_only_reverse_many_to_many_ignored(self):
  with self.assertNumQueries(1):
  self.assertEqual(Item.objects.only("request").get(), item)

 +def test_self_referential(self):
 +first = Item.objects.create(name="first", value=1)
 +second = Item.objects.create(name="second", value=2,
 source=first)
 +with self.assertNumQueries(1):
 +deferred_first, deferred_second = (
 +Item.objects.select_related("source", "destination")
 +.only("name", "source__name", "destination__value")
 +.order_by("pk")
 +)
 +with self.assertNumQueries(0):
 +self.assertEqual(deferred_first.name, first.name)
 +self.assertEqual(deferred_second.name, second.name)
 +self.assertEqual(deferred_second.source.name, first.name)
 +self.assertEqual(deferred_first.destination.name,
 second.name)
 +

  class DeferDeletionSignalsTests(TestCase):
  senders = [Item, Proxy]
 }}}
-- 
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/0107018eb1049105-540492a3-8c8b-4fe9-9fff-62469b39c21f-00%40eu-central-1.amazonses.com.

Re: [Django] #35356: Issue with OneToOneField and recursive relationships in select_related() and only().

2024-04-05 Thread Django 
#35356: Issue with OneToOneField and recursive relationships in select_related()
and only().
-+-
 Reporter:  OdinsPlasmaRifle |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.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 Simon Charette):

 Likely related to #21204 (b3db6c8dcb5145f7d45eff517bcd96460475c879) which
 was merged in 4.2.
-- 
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/0107018eb03c332d-2a5a5d96-b67c-44f3-ad20-63af84e84a5a-00%40eu-central-1.amazonses.com.

[Django] #35356: Issue with OneToOneField and recursive relationships in select_related() and only().

2024-04-05 Thread Django 
#35356: Issue with OneToOneField and recursive relationships in select_related()
and only().
-+-
   Reporter:  Joshua |  Owner:  nobody
  van Besouw |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  4.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  |
-+-
 In Django a 4.2 project, if you have a model with a recursive relationship
 `OneToOneField` like this:

 {{{
 class Example(models.Model):
 name = models.CharField(max_length=32)
 source = models.OneToOneField(
 'self', related_name='destination', on_delete=models.CASCADE
 )
 }}}

 And then query this model using:

 {{{
 Example.objects.select_related(
 "source",
 "destination",
 ).only(
 "name",
 "source__name",
 "destination__name",
 ).all()
 }}}

 It throws the following error:

 {{{
 django.core.exceptions.FieldError: Field Example.source cannot be both
 deferred and traversed using select_related at the same time.
 }}}

 **Expected behavior:**

 The queryset should apply the `select_related()` and `only()` without an
 exception occurring as the `only()` is specifying sub fields of the fields
 in the `select_related()`. Or at least this is how it used to behave.

 Interestingly, if you change the queryset to the following, it works
 without any issues:

 {{{
 Example.objects.select_related("source").only("name",
 "source__name").all()
 }}}

 And vice versa also works:

 {{{
 Example.objects.select_related("destination").only("name",
 "destination__name").all()
 }}}

 **Effected versions:**

 This error occurs in version 4.2+ of Django.

 This worked as expected in all versions of Django 4.1.

 As far as I can tell, this is a regression as a brief search doesn't
 indicate this functionality was explicitly changed at any point. I have
 not tested whether this is only an issue with recursive relationships or a
 general issues with reverse relationships.
-- 
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/0107018eafeb8a9f-3633728c-5354-4060-b9fc-950df6b73653-00%40eu-central-1.amazonses.com.

Re: [Django] #35354: Simplify ASGIRequest path handling.

2024-04-05 Thread Django 
#35354: Simplify ASGIRequest path handling.
-+-
 Reporter:  Carlton Gibson   |Owner:  Carlton
 Type:   |  Gibson
  Cleanup/optimization   |   Status:  closed
Component:  HTTP handling|  Version:  5.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  asgi | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Natalia <124304+nessita@…>):

 In [changeset:"58061fd2b4c4b66c0fd3db8026c8b5e369ed9ec3" 58061fd2]:
 {{{#!CommitTicketReference repository=""
 revision="58061fd2b4c4b66c0fd3db8026c8b5e369ed9ec3"
 [5.0.x] Refs #35354 -- Clarified FORCE_SCRIPT_NAME docs.

 Backport of ca5cd3e3e8e53f15e68ccd727ec8fe719cc48099 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/0107018eafbeb57a-f9ed113e-01d9-4f09-9611-e46971340956-00%40eu-central-1.amazonses.com.

Re: [Django] #35354: Simplify ASGIRequest path handling.

2024-04-05 Thread Django 
#35354: Simplify ASGIRequest path handling.
-+-
 Reporter:  Carlton Gibson   |Owner:  Carlton
 Type:   |  Gibson
  Cleanup/optimization   |   Status:  closed
Component:  HTTP handling|  Version:  5.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  asgi | 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 Carlton Gibson ):

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

Comment:

 In [changeset:"bcd255cd5ca0a1e686d276cca71f45ec400d84a2" bcd255cd]:
 {{{#!CommitTicketReference repository=""
 revision="bcd255cd5ca0a1e686d276cca71f45ec400d84a2"
 Fixed #35354 -- Simplified ASGIRequest path handling.

 Following the ASGI HTTP Connection Scope docs[0], the provided `path`
 is already the correct value that Django requires.

 In combination with `root_path`, from which `script_name` is derived,
 the `path_info` variable is set. It's then redundant to
 re-calculate `path` from `script_name` and `path_info`.

 See also, a clarifying discussion on the ASGIref repo[1].

 [0]: https://asgi.readthedocs.io/en/latest/specs/www.html#http-connection-
 scope
 [1]: https://github.com/django/asgiref/issues/424
 }}}
-- 
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/0107018eafbdfa85-451e10fe-2f76-42d5-9a28-9ee6da1c68d9-00%40eu-central-1.amazonses.com.

Re: [Django] #35354: Simplify ASGIRequest path handling.

2024-04-05 Thread Django 
#35354: Simplify ASGIRequest path handling.
-+-
 Reporter:  Carlton Gibson   |Owner:  Carlton
 Type:   |  Gibson
  Cleanup/optimization   |   Status:  closed
Component:  HTTP handling|  Version:  5.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  asgi | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Carlton Gibson ):

 In [changeset:"ca5cd3e3e8e53f15e68ccd727ec8fe719cc48099" ca5cd3e3]:
 {{{#!CommitTicketReference repository=""
 revision="ca5cd3e3e8e53f15e68ccd727ec8fe719cc48099"
 Refs #35354 -- Clarified FORCE_SCRIPT_NAME docs.
 }}}
-- 
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/0107018eafbdfaad-d163fbe3-ca79-4887-90b6-5be67a1ce447-00%40eu-central-1.amazonses.com.

Re: [Django] #35354: Simplify ASGIRequest path handling.

2024-04-05 Thread Django 
#35354: Simplify ASGIRequest path handling.
-+-
 Reporter:  Carlton Gibson   |Owner:  Carlton
 Type:   |  Gibson
  Cleanup/optimization   |   Status:  assigned
Component:  HTTP handling|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  asgi | 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 Natalia Bidart):

 * 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/0107018eafa3443b-4187b8f1-741b-4202-82da-edfcd899d118-00%40eu-central-1.amazonses.com.

Re: [Django] #29748: Add AUTH_GROUP_MODEL setting to swap the group model

2024-04-05 Thread Django 
#29748: Add AUTH_GROUP_MODEL setting to swap the group model
--+---
 Reporter:  damoncheng|Owner:  csirmazbendeguz
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Someday/Maybe
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+---
Changes (by csirmazbendeguz):

 * has_patch:  0 => 1
 * owner:  damoncheng => csirmazbendeguz

Comment:

 I have submitted a patch: https://github.com/django/django/pull/18053
-- 
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/0107018eaf6060a6-b1367203-9fb2-4ae7-83e9-98326d4a2992-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

2024-04-05 Thread Django 
#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Akash
 |  Kumar Sen
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 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/0107018eaf2fe13a-b6d23577-2b9b-4501-930f-1327a0abdd13-00%40eu-central-1.amazonses.com.

Re: [Django] #31710: Added all files validation to the "Uploading multiple files" example.

2024-04-05 Thread Django 
#31710: Added all files validation to the "Uploading multiple files" example.
-+-
 Reporter:  nawaik   |Owner:  Mariusz
 Type:   |  Felisiak 
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 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 Natalia Bidart):

 Related PR with docs clarifications:
 https://github.com/django/django/pull/18044
 Merged in ba4ffdc8771c2f38cf6de26a2b82bbceea2b933a
-- 
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/0107018eaf1bf386-3079e009-d3f0-4e9b-8706-a8d87ac4521c-00%40eu-central-1.amazonses.com.

Re: [Django] #35355: Images derived from models are not showing in template

2024-04-05 Thread Django 
#35355: Images derived from models are not showing in template
-+-
 Reporter:  Blauwe Stad  |Owner:  nobody
  Technologieen  |
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  4.2
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  models, ImageField   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by David Sanders):

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

Comment:

 Hi there,

 There's not sufficient information to confirm this is indeed a bug; this
 is more of a support request. Please seek assistance from a friendly
 community member in one of the support channels:
 https://www.djangoproject.com/community/

 If it does turn out there is a bug feel free to reopen the ticket.
-- 
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/0107018eaefd5bed-592b0de0-4ce9-489b-b4cf-06b82ff2ef16-00%40eu-central-1.amazonses.com.

[Django] #35355: Images derived from models are not showing in template

2024-04-05 Thread Django 
#35355: Images derived from models are not showing in template
-+-
   Reporter: |  Owner:  nobody
  BlauweStadTechnologieen|
   Type:  Bug| Status:  new
  Component:  Template   |Version:  4.2
  system |
   Severity:  Normal |   Keywords:  models, ImageField
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Images are not showing in templates despite following the documentation to
 the letter, which leave the conclusion that there is a bug with Django. I
 have the following:

 The directory goes as follows:  root  > media > assets

 {{{

 #models.py
 class NewsArticle(models.Model):

 uuid=   models.UUIDField(primary_key=True,
 default=uuid.uuid4, editable=False)
 image   =   models.ImageField(upload_to='assets/')


 }}}



 {{{
 # settings.py
 MEDIA_URL = '/media/'
 MEDIA_ROOT = os.path.join(BASE_DIR, 'media')
 MEDIA_DIR = BASE_DIR / 'media'
 }}}


 {{{
 #views.py
 from django.urls import path, include
 from . import views
 from django.conf import settings
 from django.conf.urls.static import static
 from django.contrib import admin
 from django.views.static import serve


 urlpatterns = [
 path('', views.details),
 path('',views.article_list),
 ] + static(settings.MEDIA_URL, document_root=settings.MEDIA_ROOT)
 }}}


 {{{
 # template
 
 }}}

 Despite this, there is a bug with Django which prevents images from being
 shown in the template.
-- 
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/0107018eaeeec1e6-18da33dd-dda7-4f24-98b0-c4a0ebee8643-00%40eu-central-1.amazonses.com.

Re: [Django] #35336: Adding GeneratedField fails with ProgrammingError when using When on CharField

2024-04-05 Thread Django 
#35336: Adding GeneratedField fails with ProgrammingError when using When on
CharField
-+-
 Reporter:  Adrian Garcia|Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  postgres,| Triage Stage:  Ready for
  generatedfield, contains   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by GitHub ):

 In [changeset:"d859c0be9c6098f624429874b695017c97ecf125" d859c0b]:
 {{{#!CommitTicketReference repository=""
 revision="d859c0be9c6098f624429874b695017c97ecf125"
 [5.0.x] Refs #35336 -- Fixed
 SchemaTests.test_add_generated_field_contains() test on PostgreSQL.

 Concat() in Django 5.0 is not immutable on PostgreSQL and cannot be used
 in GeneratedField, see 6364b6ee1071381eb3a23ba6b821fc0d6f0fce75.
 }}}
-- 
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/0107018eae2eb782-46b61fe5-aab2-4f20-b802-eab1acff5de9-00%40eu-central-1.amazonses.com.

Re: [Django] #34297: ValueError: invalid token in plural form: EXPRESSION when adding new language

2024-04-05 Thread Django 
#34297: ValueError: invalid token in plural form: EXPRESSION when adding new
language
-+-
 Reporter:  Azat |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Utilities|  Version:  4.1
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  gettext, i18n, l10n  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Natalia Bidart):

 Replying to [comment:6 Azat]:
 > To be honest, one important thing you can do before commenting on other
 people's ticket is simply try and check if that is the case. Python not
 displaying enough information but it dose not mean, you saw the whole
 world from that console info.

 While we appreciate your input, and while we understand that you may feel
 frustrated by the response, the sentence above is confrontational. We
 kindly remind you to maintain a respectful and constructive tone in your
 communications. Please follow the [https://www.djangoproject.com/conduct/
 Django Code of Conduct] when commenting on tickets.

 > I ma not sure, from which version Django behaves  like this, but in
 earlier versions, you could actually add a new language yourself, by
 changing proper settings and providing local translation files.

 It has been said that Django does not support the feature you are
 describing (adding new custom language), and that if it has worked before,
 it was by chance. The proper procedure at this stage was completed, which
 is to close this ticket as invalid following the
 [https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
 tickets/#closing-tickets ticket triaging process].

 Everyone is welcomed to seek further help in the
 [https://www.djangoproject.com/community/ user 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/0107018eae17b986-33845fbc-340e-4eff-9385-44a1f3d03d74-00%40eu-central-1.amazonses.com.

Re: [Django] #29111: Use autocomplete_fields in list_filter for related models

2024-04-05 Thread Django 
#29111: Use autocomplete_fields in list_filter for related models
---+
 Reporter:  Paul Tiplady   |Owner:  Gav O'Connor
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  dev
 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 Gav O'Connor):

 * owner:  Gav O'Connor => Gav O'Connor

-- 
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/0107018ead9a8e42-1900c7e7-d5e2-4701-819c-b19399c4ea27-00%40eu-central-1.amazonses.com.

Re: [Django] #35169: updated asgi handler for disconnects does not process ROOT_PATH

2024-04-05 Thread Django 
#35169: updated asgi handler for disconnects does not process ROOT_PATH
-+-
 Reporter:  Michael Smith|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  5.0
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  asgi, handler,   | Triage Stage:
  root_path  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Sarah Boyce <42296566+sarahboyce@…>):

 In [changeset:"4d2ef9bb826db76acb5ed7609a9162de9b651921" 4d2ef9b]:
 {{{#!CommitTicketReference repository=""
 revision="4d2ef9bb826db76acb5ed7609a9162de9b651921"
 Refs #35169 -- Added test for ASGIRequest root_path handling.
 }}}
-- 
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/0107018ead988a4a-eebaad0f-0fed-4a2c-9cf3-4f3c64720662-00%40eu-central-1.amazonses.com.

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

2024-04-05 Thread 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
-+-
Comment (by Rich):

 The proposed change to the LANGUAGE_CODE setting, in context, reads:

 A string representing the language code for this installation. This should
 be in
 standard `language ID format`. For example, U.S. English
 is "en-us"'', the default format to use when localization is disabled
 with `localize` and `unlocalize` template filter or tag see
 `controlling localization in templates`''. See also
 the `list of language identifiers` and `/topics/i18n/index`.

 That doesn't read well to me, and also doesn't really cover the situation.
 I think the first sentence needs to change to make it clear this is a
 fallback, e.g.:

 A string representing the fallback language code for this
 installation.

 The line "USE_I18N must be active for this setting to have any effect." is
 not true and should be removed I think.

 Finally, a third entry could be added to the list of 'purposes',  e.g.

 If localization is explicitly disabled via the `localize` and
 `unlocalize` template filters or tags. See `controlling localization in
 templates`.

 The proposed change to formatting.txt seems confusing and unnecessary to
 me.
-- 
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/0107018ead92ca45-b5a0176e-284d-4693-b9d2-186528962880-00%40eu-central-1.amazonses.com.

Re: [Django] #35354: Simplify ASGIRequest path handling.

2024-04-05 Thread Django 
#35354: Simplify ASGIRequest path handling.
-+-
 Reporter:  Carlton Gibson   |Owner:  Carlton
 Type:   |  Gibson
  Cleanup/optimization   |   Status:  assigned
Component:  HTTP handling|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  asgi | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by David Smith):

 * 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/0107018ead929b64-d2e41150-abe0-470f-a94b-28afc884c82a-00%40eu-central-1.amazonses.com.

Re: [Django] #35354: Simplify ASGIRequest path handling.

2024-04-05 Thread Django 
#35354: Simplify ASGIRequest path handling.
-+-
 Reporter:  Carlton Gibson   |Owner:  Carlton
 Type:   |  Gibson
  Cleanup/optimization   |   Status:  assigned
Component:  HTTP handling|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  asgi | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Carlton Gibson:

Old description:

> Following the ASGI HTTP Connection Scope docs[0], the provided `path` is
> already the correct value that Django requires.
>
> In combination with `root_path`, from which `script_name` is derived, the
> `path_info` variable can is set.
> It's then redundant to re-calculate `path` from `script_name` and
> `path_info`.
>
> See also, a clarifying discussion on the ASGIref repo[1].
>
> [0]: https://asgi.readthedocs.io/en/latest/specs/www.html#http-
> connection-scope
> [1]: https://github.com/django/asgiref/issues/424

New description:

 Following the ASGI HTTP Connection Scope docs[0], the provided `path` is
 already the correct value that Django requires.

 In combination with `root_path`, from which `script_name` is derived, the
 `path_info` variable is set.
 It's then redundant to re-calculate `path` from `script_name` and
 `path_info`.

 See also, a clarifying discussion on the ASGIref repo[1].

 [0]: https://asgi.readthedocs.io/en/latest/specs/www.html#http-connection-
 scope
 [1]: https://github.com/django/asgiref/issues/424

--
-- 
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/0107018ead6a2032-3fff5387-c674-44a5-86da-8550418296c4-00%40eu-central-1.amazonses.com.

Re: [Django] #35354: Simplify ASGIRequest path handling.

2024-04-05 Thread Django 
#35354: Simplify ASGIRequest path handling.
-+-
 Reporter:  Carlton Gibson   |Owner:  Carlton
 Type:   |  Gibson
  Cleanup/optimization   |   Status:  assigned
Component:  HTTP handling|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  asgi | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * cc: Andrew Godwin (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/0107018ead5dfb7d-00aea3b0-2feb-42c6-ae9c-a11c351d0d0b-00%40eu-central-1.amazonses.com.

Re: [Django] #35354: Simplify ASGIRequest path handling.

2024-04-05 Thread Django 
#35354: Simplify ASGIRequest path handling.
-+-
 Reporter:  Carlton Gibson   |Owner:  Carlton
 Type:   |  Gibson
  Cleanup/optimization   |   Status:  assigned
Component:  HTTP handling|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  asgi | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * owner:  nobody => Carlton Gibson

Comment:

 [https://github.com/django/django/pull/18050 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/0107018ead5d70ba-66190fa2-308d-4b71-bb7a-2b880ddbb970-00%40eu-central-1.amazonses.com.

[Django] #35354: Simplify ASGIRequest path handling.

2024-04-05 Thread Django 
#35354: Simplify ASGIRequest path handling.
+--
   Reporter:  Carlton Gibson|  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  assigned
  Component:  HTTP handling |Version:  5.0
   Severity:  Normal|   Keywords:  asgi
   Triage Stage:  Unreviewed|  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+--
 Following the ASGI HTTP Connection Scope docs[0], the provided `path` is
 already the correct value that Django requires.

 In combination with `root_path`, from which `script_name` is derived, the
 `path_info` variable can is set.
 It's then redundant to re-calculate `path` from `script_name` and
 `path_info`.

 See also, a clarifying discussion on the ASGIref repo[1].

 [0]: https://asgi.readthedocs.io/en/latest/specs/www.html#http-connection-
 scope
 [1]: https://github.com/django/asgiref/issues/424
-- 
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/0107018ead5be9d3-da848f7b-e687-4783-8801-33653c016557-00%40eu-central-1.amazonses.com.

Re: [Django] #33671: Migrations crashes when adding/altering collations on indexed columns on Oracle.

2024-04-05 Thread Django 
#33671: Migrations crashes when adding/altering collations on indexed columns on
Oracle.
--+
 Reporter:  Mariusz Felisiak  |Owner:  Mahesh Gupta
 Type:  Bug   |   Status:  assigned
Component:  Migrations|  Version:  4.0
 Severity:  Normal|   Resolution:
 Keywords:  oracle collation  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Comment (by Mahesh Gupta):

 Opened PR https://github.com/django/django/pull/18049
-- 
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/0107018ead21042b-69264e57-cd90-487f-a71f-a7dbb97bab42-00%40eu-central-1.amazonses.com.

Re: [Django] #33671: Migrations crashes when adding/altering collations on indexed columns on Oracle.

2024-04-05 Thread Django 
#33671: Migrations crashes when adding/altering collations on indexed columns on
Oracle.
--+
 Reporter:  Mariusz Felisiak  |Owner:  Mahesh Gupta
 Type:  Bug   |   Status:  assigned
Component:  Migrations|  Version:  4.0
 Severity:  Normal|   Resolution:
 Keywords:  oracle collation  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Mahesh Gupta):

 * 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/0107018ead20289b-22d7659c-58f0-4869-b905-b163b0b00477-00%40eu-central-1.amazonses.com.

Re: [Django] #35169: updated asgi handler for disconnects does not process ROOT_PATH

2024-04-05 Thread Django 
#35169: updated asgi handler for disconnects does not process ROOT_PATH
-+-
 Reporter:  Michael Smith|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:  5.0
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  asgi, handler,   | Triage Stage:
  root_path  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Carlton Gibson):

 I've created a [https://github.com/django/django/pull/18048 PR adding a
 test for this here]. The test passes (on both main and stable/4.2.x
 branches).

 Comment from there:

 > Possible change may be in 041b0a3 @sarahboyce: maybe folks have
 FORCE_SCRIPT_NAME set to a non-None value. That's the sort of thing once
 might have done when experimenting with mounting under a root_path.
 > If it's not that, then I'm out of ideas without a reproduce.
-- 
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/0107018ead1b3c30-01815dbb-3c4b-41a0-be21-1bd3811f41de-00%40eu-central-1.amazonses.com.

Re: [Django] #34297: ValueError: invalid token in plural form: EXPRESSION when adding new language

2024-04-05 Thread Django 
#34297: ValueError: invalid token in plural form: EXPRESSION when adding new
language
-+-
 Reporter:  Azat |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Utilities|  Version:  4.1
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  gettext, i18n, l10n  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Azat):

 Replying to [comment:5 Simon Charette]:
 > I'm not sure how this should be considered a regression given nothing
 points at Django being misconfigured here.
 >
 > Until someone can pinpoint how Django might be to blame and what exactly
 the problem is then everything seems to point at a `gettext`/ Python
 problem.

 To be honest, one important thing you can do before commenting on other
 people's ticket is simply try and check if that is the case. Python not
 displaying enough information but it dose not mean, you saw the whole
 world from that console info.

 The problem I mentioned 14 months ago, has been resolved by "Adding the
 language to django officially". That was the solution, yes, except your
 language is being added to the django source code, the problem above
 occurs when you try to add a new one yourself.

 I ma not sure, from which version Django behaves  like this, but in
 earlier versions, you could actually add a new language yourself, by
 changing proper settings and providing local translation files.
-- 
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/0107018eacebea2c-b9949892-d890-48ba-be0c-98e4cfda58d0-00%40eu-central-1.amazonses.com.