Re: [Django] #34471: Cannot import name 'url' from 'django.conf.urls'

[Django]

#34471: Cannot import name 'url' from 'django.conf.urls'
---+--
 Reporter:  VJ Magar   |Owner:  VJ Magar
 Type:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  4.2
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by VJ Magar):

 Replying to [comment:2 Mariusz Felisiak]:
 > The `django.conf.urls.url` alias was deprecated in Django 3.1 and
 removed in Django 4.0.

 Hey Mariusz Felisiak,

 I knew that `django.conf.urls.url` was removed in Django 4.0. However, I
 was getting this error when setup the new django project.
 It turns out that I had accidentally used older version of Django (some
 old django from global space).

 Thanks for quickly marking this issue as invalid. It saved few hours of
 mine

-- 
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/010701875a78544c-29f27f18-ebba-4802-bd39-b0370f28c13c-00%40eu-central-1.amazonses.com.

Re: [Django] #34470: client_encoding is no longer enforce on PostgreSQL. (was: client_encoding is no longer set on PostgreSQL.)

[Django]

#34470: client_encoding is no longer enforce on PostgreSQL.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  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/010701875a6adea3-a08906df-e52c-477e-afa7-4d4d8e3245f8-00%40eu-central-1.amazonses.com.

Re: [Django] #34471: Cannot import name 'url' from 'django.conf.urls' (was: ImportError: cannot import name 'url' from 'django.conf.urls')

[Django]

#34471: Cannot import name 'url' from 'django.conf.urls'
---+--
 Reporter:  VJ Magar   |Owner:  VJ Magar
 Type:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  4.2
 Severity:  Normal |   Resolution:  invalid
 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 Mariusz Felisiak):

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


Comment:

 The `django.conf.urls.url` alias was deprecated in Django 3.1 and removed
 in Django 4.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/010701875a6a4dd0-b6ff6045-6f4f-453b-b2cc-3437496513e2-00%40eu-central-1.amazonses.com.

Re: [Django] #34470: client_encoding is no longer set on PostgreSQL.

[Django]

#34470: client_encoding is no longer set on PostgreSQL.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/16739 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/010701875a676e1a-3a6949b3-fcd2-4d61-8c0e-4becb2b46f5e-00%40eu-central-1.amazonses.com.

Re: [Django] #34471: ImportError: cannot import name 'url' from 'django.conf.urls'

[Django]

#34471: ImportError: cannot import name 'url' from 'django.conf.urls'
---+--
 Reporter:  VJ Magar   |Owner:  VJ Magar
 Type:  Bug|   Status:  assigned
Component:  Uncategorized  |  Version:  4.2
 Severity:  Normal |   Resolution:
 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 VJ Magar):

 * owner:  nobody => VJ Magar
 * 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/010701875a644d80-fae9e3d1-f31c-45f0-b6d0-8115efef9406-00%40eu-central-1.amazonses.com.

[Django] #34471: ImportError: cannot import name 'url' from 'django.conf.urls'

[Django]

#34471: ImportError: cannot import name 'url' from 'django.conf.urls'
-+
   Reporter:  VJ Magar   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Uncategorized  |Version:  4.2
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+
 After creating new Django app using `django-admin startproject` when
 trying to run the project, we are getting import error for the URL.

-- 
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/010701875a642eec-49388458-73f2-4b80-9070-63454de1199c-00%40eu-central-1.amazonses.com.

Re: [Django] #34470: client_encoding is no longer set on PostgreSQL.

[Django]

#34470: client_encoding is no longer set on PostgreSQL.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 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 Mariusz Felisiak):

 * owner:  nobody => Mariusz Felisiak
 * status:  new => assigned


Comment:

 By default, client encoding is the encoding defined by the database but we
 should still enforce `utf-8`.

-- 
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/010701875a5be4b8-705d5363-8777-420f-a163-6edaba19252d-00%40eu-central-1.amazonses.com.

[Django] #34470: client_encoding is no longer set on PostgreSQL.

[Django]

#34470: client_encoding is no longer set on PostgreSQL.
-+-
   Reporter:  Mariusz|  Owner:  nobody
  Felisiak   |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  4.2
  layer (models, ORM)|
   Severity:  Release|   Keywords:
  blocker|
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 `client_encoding` defined in `get_connection_params()` is always
 overridden in the following
 
[https://github.com/django/django/blob/9daf8b4109c3e133eb57349bb44d73cc60c5773c/django/db/backends/postgresql/base.py#L212-L222
 code].

 Regression in 6a2165816394ab4bb259f6171e82417e098e97a6.

-- 
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/010701875a4c8e0a-801b29c3-72b6-471c-b8c7-2f8b78e5baa4-00%40eu-central-1.amazonses.com.

Re: [Django] #34466: Django 4.2 overwrites user-specified psycopg cursor_factory

[Django]

#34466: Django 4.2 overwrites user-specified psycopg cursor_factory
-+-
 Reporter:  Anders Kaseorg   |Owner:  Anders
 |  Kaseorg
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Release blocker  |   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 Mariusz Felisiak):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin
 * needs_docs:  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/010701875a45a2e6-bdd6f07e-737e-4e59-915b-92423170de99-00%40eu-central-1.amazonses.com.

Re: [Django] #34118: Python 3.12 compatibility

[Django]

#34118: Python 3.12 compatibility
-+-
 Reporter:  Mariusz Felisiak |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Other) |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by thesamesam):

 * cc: thesamesam (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/010701875a15f9dc-8dd6c8de-dc51-43a2-916e-7f9a01b580c1-00%40eu-central-1.amazonses.com.

Re: [Django] #34464: QuerySet.count() regression on Django 4.2 with values() and annotate()

[Django]

#34464: QuerySet.count() regression on Django 4.2 with values() and annotate()
-+-
 Reporter:  Ian Cubitt   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  postgresql   | 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 Mariusz Felisiak ):

 In [changeset:"511dc3db539122577aaba71f5a24d65d5adab092" 511dc3db]:
 {{{
 #!CommitTicketReference repository=""
 revision="511dc3db539122577aaba71f5a24d65d5adab092"
 [4.2.x] Fixed #34464 -- Fixed queryset aggregation over group by
 reference.

 Regression in 59bea9efd2768102fc9d3aedda469502c218e9b7.

 Refs #28477.

 Thanks Ian Cubitt for the report.

 Backport of 9daf8b4109c3e133eb57349bb44d73cc60c5773c 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/010701875a14d360-12834c91-ac7b-479a-9a07-5f78a192b2d4-00%40eu-central-1.amazonses.com.

Re: [Django] #28477: Strip unused annotations from count queries

[Django]

#28477: Strip unused annotations from count queries
-+-
 Reporter:  Tom Forbes   |Owner:  Simon
 Type:   |  Charette
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 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
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"511dc3db539122577aaba71f5a24d65d5adab092" 511dc3db]:
 {{{
 #!CommitTicketReference repository=""
 revision="511dc3db539122577aaba71f5a24d65d5adab092"
 [4.2.x] Fixed #34464 -- Fixed queryset aggregation over group by
 reference.

 Regression in 59bea9efd2768102fc9d3aedda469502c218e9b7.

 Refs #28477.

 Thanks Ian Cubitt for the report.

 Backport of 9daf8b4109c3e133eb57349bb44d73cc60c5773c 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/010701875a14d378-eed83881-1afd-4222-a96a-9e823e7698ac-00%40eu-central-1.amazonses.com.

Re: [Django] #28477: Strip unused annotations from count queries

[Django]

#28477: Strip unused annotations from count queries
-+-
 Reporter:  Tom Forbes   |Owner:  Simon
 Type:   |  Charette
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 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
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"9daf8b4109c3e133eb57349bb44d73cc60c5773c" 9daf8b41]:
 {{{
 #!CommitTicketReference repository=""
 revision="9daf8b4109c3e133eb57349bb44d73cc60c5773c"
 Fixed #34464 -- Fixed queryset aggregation over group by reference.

 Regression in 59bea9efd2768102fc9d3aedda469502c218e9b7.

 Refs #28477.

 Thanks Ian Cubitt for the report.
 }}}

-- 
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/010701875a147b9b-bf79a6e0-05b1-4311-a95c-6e7800b9f5c9-00%40eu-central-1.amazonses.com.

Re: [Django] #34464: QuerySet.count() regression on Django 4.2 with values() and annotate()

[Django]

#34464: QuerySet.count() regression on Django 4.2 with values() and annotate()
-+-
 Reporter:  Ian Cubitt   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  postgresql   | 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:"9daf8b4109c3e133eb57349bb44d73cc60c5773c" 9daf8b41]:
 {{{
 #!CommitTicketReference repository=""
 revision="9daf8b4109c3e133eb57349bb44d73cc60c5773c"
 Fixed #34464 -- Fixed queryset aggregation over group by reference.

 Regression in 59bea9efd2768102fc9d3aedda469502c218e9b7.

 Refs #28477.

 Thanks Ian Cubitt for the report.
 }}}

-- 
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/010701875a147b85-cb79602e-0a5b-4c41-8bd0-c20f6f0b7074-00%40eu-central-1.amazonses.com.

Re: [Django] #34118: Python 3.12 compatibility

[Django]

#34118: Python 3.12 compatibility
-+-
 Reporter:  Mariusz Felisiak |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Other) |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 Replying to [comment:11 thesamesam]:
 > Hi folks,
 >
 >
 
https://github.com/django/django/commit/38e63c9e61152682f3ff982c85a73793ab6d3267
 was applied to fix Python 3.12, but cpython upstream have backported the
 fix for https://github.com/python/cpython/issues/102549 to Python 3.11
 too.
 >
 > The Django patch will need adjusting to probably just allow both output
 messages (or sniff the Python minor/patch version).

 Thanks! It's unfortunate, will fix this.

-- 
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/010701875a0a8139-4ddf1502-b270-40cb-aa79-74e28498d748-00%40eu-central-1.amazonses.com.

Re: [Django] #34118: Python 3.12 compatibility

[Django]

#34118: Python 3.12 compatibility
-+-
 Reporter:  Mariusz Felisiak |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Other) |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by thesamesam):

 Hi folks,

 
https://github.com/django/django/commit/38e63c9e61152682f3ff982c85a73793ab6d3267
 was applied to fix Python 3.12, but cpython upstream have backported the
 fix for https://github.com/python/cpython/issues/102549 to Python 3.11
 too.

-- 
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/010701875a08beef-a9edc0a0-c739-475f-82b2-c98ac2c0c92f-00%40eu-central-1.amazonses.com.

Re: [Django] #34466: Django 4.2 overwrites user-specified psycopg cursor_factory

[Django]

#34466: Django 4.2 overwrites user-specified psycopg cursor_factory
-+-
 Reporter:  Anders Kaseorg   |Owner:  Anders
 |  Kaseorg
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1
 * severity:  Normal => Release blocker
 * needs_docs:  0 => 1


Comment:

 Replying to [comment:2 Florian Apolloner]:
 > Assuming we fix this we should also make it more pythonic (and I guess I
 am at fault for it being like it is now) and not check for `is True` but
 only truthiness.

 We use `is True` intentionally, to avoid errors when passing wrong truthy
 values, e.g.`"server_side_binding": os.environ.get("USE_SSB")` (where
 `os.environ.get("USE_SSB")` returns `"False"`).

-- 
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/010701875a00ab02-cb8136ae-d437-49e2-909b-32dee11cc82a-00%40eu-central-1.amazonses.com.

Re: [Django] #34464: QuerySet.count() regression on Django 4.2 with values() and annotate()

[Django]

#34464: QuerySet.count() regression on Django 4.2 with values() and annotate()
-+-
 Reporter:  Ian Cubitt   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  postgresql   | 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):

 * 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/0107018759f5a4ef-a523e233-3498-49a4-8088-1a3a1f0edb21-00%40eu-central-1.amazonses.com.

Re: [Django] #34469: Push inspectdb to assimilate the foreign keys that are in other databases

[Django]

#34469: Push inspectdb to assimilate the foreign keys that are in other 
databases
-+-
 Reporter:  daysus   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  inspectdb,   | Triage Stage:
  foreignkeys|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * status:  new => closed
 * has_patch:  1 => 0
 * resolution:   => duplicate


Comment:

 This is a duplicate of one of the tickets #7556, #25243, #22673, or #6148.
 Unfortunately, the description of the ticket is laconic.

 In the future, please check
 [https://docs.djangoproject.com/en/dev/internals/contributing/bugs-and-
 features/#reporting-bugs bug reporting guidelines] and provide more
 details.

-- 
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/0107018759e502a8-92e0e5e1-35c7-458e-bcc1-6c2fbe6ea905-00%40eu-central-1.amazonses.com.

Re: [Django] #34465: Handle malformed CSRF cookie

[Django]

#34465: Handle malformed CSRF cookie
-+--
 Reporter:  Miha Sedej   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  CSRF |  Version:  4.1
 Severity:  Normal   |   Resolution:
 Keywords:  csrf, 500 error  | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Ruchir Harbhajanka):

 * cc: Ruchir Harbhajanka (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/0107018759e1a759-8b20b194-de33-4514-ac29-1720e982f745-00%40eu-central-1.amazonses.com.

Re: [Django] #34469: Push inspectdb to assimilate the foreign keys that are in other databases

[Django]

#34469: Push inspectdb to assimilate the foreign keys that are in other 
databases
-+-
 Reporter:  daysus   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  inspectdb,   | Triage Stage:
  foreignkeys|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by daysus):

 Change type to bug

-- 
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/0107018758dd00a9-2b785d97-9485-4656-8533-3513d340ca57-00%40eu-central-1.amazonses.com.

Re: [Django] #34469: Push inspectdb to assimilate the foreign keys that are in other databases

[Django]

#34469: Push inspectdb to assimilate the foreign keys that are in other 
databases
-+-
 Reporter:  daysus   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  inspectdb,   | Triage Stage:
  foreignkeys|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by daysus):

 * type:  Uncategorized => Bug


-- 
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/0107018758dcc8fc-f147defc-8e65-4293-86ab-1215892ab2e3-00%40eu-central-1.amazonses.com.

[Django] #34469: Push inspectdb to assimilate the foreign keys that are in other databases

[Django]

#34469: Push inspectdb to assimilate the foreign keys that are in other 
databases
-+-
   Reporter:  daysus |  Owner:  nobody
   Type: | Status:  new
  Uncategorized  |
  Component:  Database   |Version:  4.1
  layer (models, ORM)|   Keywords:  inspectdb,
   Severity:  Normal |  foreignkeys
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I have a code for inspectdb to assimilate the foreign keys that are in
 other databases. How can I do the push?

-- 
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/0107018758dc71b6-3d0ce8a3-63ea-47d8-8d1d-a9a7a208e4a5-00%40eu-central-1.amazonses.com.

Re: [Django] #34466: Django 4.2 overwrites user-specified psycopg cursor_factory

[Django]

#34466: Django 4.2 overwrites user-specified psycopg cursor_factory
-+-
 Reporter:  Anders Kaseorg   |Owner:  Anders
 |  Kaseorg
 Type:  Bug  |   Status:  assigned
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 Anders Kaseorg):

 * needs_tests:  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/01070187589ee75d-45f001d9-73b9-46c0-a149-8833e53355a4-00%40eu-central-1.amazonses.com.

Re: [Django] #34466: Django 4.2 overwrites user-specified psycopg cursor_factory

[Django]

#34466: Django 4.2 overwrites user-specified psycopg cursor_factory
-+-
 Reporter:  Anders Kaseorg   |Owner:  Anders
 |  Kaseorg
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Anders Kaseorg):

 Removed `is True` and added a test.

-- 
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/01070187589eb825-94d1c082-bb0f-4e26-8f6d-1aab3de22724-00%40eu-central-1.amazonses.com.

Re: [Django] #34466: Django 4.2 overwrites user-specified psycopg cursor_factory

[Django]

#34466: Django 4.2 overwrites user-specified psycopg cursor_factory
-+-
 Reporter:  Anders Kaseorg   |Owner:  Anders
 |  Kaseorg
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Florian Apolloner):

 * needs_tests:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 Sounds like a legit request, we didn't limit this functionality on purpose
 but rather by accident.

 Assuming we fix this we should also make it more pythonic (and I guess I
 am at fault for it being like it is now) and not check for `is True` but
 only truthiness. Either way, a test ensuring that we do not regress here
 would be good.

-- 
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/01070187584a6349-e7b87210-227f-4738-a62f-40a3289a2cf2-00%40eu-central-1.amazonses.com.

Re: [Django] #34467: `Cycle` tag do not work with variables defined in `with`-tag.

[Django]

#34467: `Cycle` tag do not work with variables defined in `with`-tag.
-+-
 Reporter:  Prikalel |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  4.0
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  cycle, with, | Triage Stage:
  templates  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Prikalel):

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


Comment:

 Dublicate of
 #34468

-- 
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/01070187583596c6-4549d03b-3489-432b-9106-bd7dbb9ce91e-00%40eu-central-1.amazonses.com.

[Django] #34468: `Cycle` tag do not work with variables defined in `with`-tag.

[Django]

#34468: `Cycle` tag do not work with variables defined in `with`-tag.
-+-
   Reporter:  Prikalel   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Template   |Version:  4.0
  system |   Keywords:  cycle, with,
   Severity:  Normal |  templates
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Here is the example:

 {{{
 {# context is simple dict with one key {A=["1", "2", "3"]} #}

 {% with example_defined_variable="123" %}

 {% for item in A %}

 Current item: {{ item }}

 Current cycle item: {% cycle example_defined_variable %}

 {% endfor %}

 Visible page.

 {% endwith %}
 }}}

 As you can see I render this template using django 4.0.1 and context
 containing 1 key "**A**" with the value of **["1", "2", "3"]** (that is
 the list of strings).
 Then I try to print the items of the list along with predefined value (see
 **with**-tag).
 The result must be like:

 {{{
 Current item: 1
 Current cycle item: 123
 Current item: 2
 Current cycle item: 123
 Current item: 3
 Current cycle item: 123
 Visible page.
 }}}

 But instead Im getting:

 No named cycles in template. 'example_defined_variable' is not defined

 That means that cycle-tag do not recognize **example_defined_variable** as
 defined variable, BUT
 on the
 [https://docs.djangoproject.com/en/4.0/ref/templates/builtins/#cycle
 documentation] page there is the note that you CAN use defined variables
 in cycle-tag.

-- 
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/010701875833ef60-28e7829d-2dc0-430f-a138-4f6980dacfa2-00%40eu-central-1.amazonses.com.

[Django] #34467: `Cycle` tag do not work with variables defined in `with`-tag.

[Django]

#34467: `Cycle` tag do not work with variables defined in `with`-tag.
-+-
   Reporter:  Prikalel   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Template   |Version:  4.0
  system |   Keywords:  cycle, with,
   Severity:  Normal |  templates
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Here is the example:

 {{{
 {# context is simple dict with one key {A=["1", "2", "3"]} #}

 {% with example_defined_variable="123" %}

 {% for item in A %}

 Current item: {{ item }}

 Current cycle item: {% cycle example_defined_variable %}

 {% endfor %}

 Visible page.

 {% endwith %}
 }}}

 As you can see I render this template using django 4.0.1 and context
 containing 1 key "**A**" with the value of **["1", "2", "3"]** (that is
 the list of strings).
 Then I try to print the items of the list along with predefined value (see
 **with**-tag).
 The result must be like:

 {{{
 Current item: 1
 Current cycle item: 123
 Current item: 2
 Current cycle item: 123
 Current item: 3
 Current cycle item: 123
 Visible page.
 }}}

 But instead Im getting:

 No named cycles in template. 'example_defined_variable' is not defined

 That means that cycle-tag do not recognize **example_defined_variable** as
 defined variable, BUT
 on the
 [https://docs.djangoproject.com/en/4.0/ref/templates/builtins/#cycle
 documentation] page there is the note that you CAN use defined variables
 in cycle-tag.

-- 
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/010701875833921e-c613aec4-5b11-42bb-a253-a5b944f04dc4-00%40eu-central-1.amazonses.com.

Re: [Django] #34466: Django 4.2 overwrites user-specified psycopg cursor_factory

[Django]

#34466: Django 4.2 overwrites user-specified psycopg cursor_factory
-+-
 Reporter:  Anders Kaseorg   |Owner:  Anders
 |  Kaseorg
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Anders Kaseorg):

 * owner:  nobody => Anders Kaseorg
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

 Submitted a patch at https://github.com/django/django/pull/16736.

-- 
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/010701875822c498-92b53783-2b17-445c-bdf6-593edce70a2d-00%40eu-central-1.amazonses.com.

Re: [Django] #34455: i18n_patterns() not respecting prefix_default_language=False

[Django]

#34455: i18n_patterns() not respecting prefix_default_language=False
-+-
 Reporter:  Oussama Jarrousse|Owner:  Sarah
 |  Boyce
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  4.2
  Internationalization   |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  internationalization, i18n,|
  prefix_default_language|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mohit Singh Sinsniwal):

 Replying to [comment:17 Sarah Boyce]:
 > Hi Mohit 👋 sorry I started to have a look and should have said so on
 the ticket
 >
 > You can see here where I think the issue could be solved (doesn't mean
 it's where it should be https://github.com/django/django/pull/16735).
 > I think it's something around the whole `en-us` falling back to `en` and
 then that is different to the setting value for `LANGUAGE_CODE` 🤔
 >
 > In general how I would approach a ticket is to write a regression test
 first and then see if you can get that passing without breaking things in
 other places
 Hi Sarah,
 Thank you for solving the issue.
 No problem, I understand that it would have taken me a lot of time to
 solve as this was my first ticket on djangoproject. Thank you for your
 guidance. I will try to write tests first in the future. Also, thank you
 to Mariusz for being patient with me and bearing with my absurd mistakes.

-- 
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/01070187582072a3-6d2dc1d7-95f6-4f7a-9f9e-dfd2c19f8d77-00%40eu-central-1.amazonses.com.

Re: [Django] #34455: i18n_patterns() not respecting prefix_default_language=False

[Django]

#34455: i18n_patterns() not respecting prefix_default_language=False
-+-
 Reporter:  Oussama Jarrousse|Owner:  Sarah
 |  Boyce
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  4.2
  Internationalization   |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  internationalization, i18n,|
  prefix_default_language|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 > I think it's something around the whole `en-us` falling back to `en` and
 then that is different to the setting value for `LANGUAGE_CODE` 🤔

 Brilliant! Thanks, that's what I've been missing for the whole time.

-- 
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/010701875812453d-247f67e5-d3a7-42a1-be34-ff4eec61eccd-00%40eu-central-1.amazonses.com.

[Django] #34466: Django 4.2 overwrites user-specified psycopg cursor_factory

[Django]

#34466: Django 4.2 overwrites user-specified psycopg cursor_factory
-+-
   Reporter:  Anders |  Owner:  nobody
  Kaseorg|
   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  |
-+-
 Zulip
 
[https://github.com/zulip/zulip/blob/7c023042cfbbd8817d5ba3adfca365734500a0e2/zproject/computed_settings.py#L285
 configures] a custom `cursor_factory` that
 
[https://github.com/zulip/zulip/blob/7c023042cfbbd8817d5ba3adfca365734500a0e2/zerver/lib/db.py#L31
 wraps] `psycopg2.extensions.cursor` to collect timing statistics for
 logging. But this no longer works in Django 4.2 due to
 09ffc5c1212d4ced58b708cbbf3dfbfb77b782ca (#33308) and
 0e2649fdf40cedc5be7e2c0e5f7711f315e36b84 (#34255) because
 `DatabaseWrapper.get_new_connection` now unconditionally overwrites
 `connection.cursor_factory` (even for psycopg2).

 The configured `cursor_factory` is being passed to `get_new_connection` as
 `conn_params["cursor_factory"]`. `get_new_connection` should leave that
 alone if it’s set. (And if it’s not, it might also be cleaner for to pass
 the default `cursor_factory` via a keyword argument to
 `psycopg[2].connect` too, rather than mutating it later.)

-- 
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/0107018758113deb-91df768d-39bc-4482-934b-49d346fa1803-00%40eu-central-1.amazonses.com.

Re: [Django] #34455: i18n_patterns() not respecting prefix_default_language=False

[Django]

#34455: i18n_patterns() not respecting prefix_default_language=False
-+-
 Reporter:  Oussama Jarrousse|Owner:  Sarah
 |  Boyce
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  4.2
  Internationalization   |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  internationalization, i18n,|
  prefix_default_language|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sarah Boyce):

 * owner:  Mohit Singh Sinsniwal => Sarah Boyce
 * 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/0107018757b8a5ec-ea000f3e-f40f-441b-93fc-487ae79653ee-00%40eu-central-1.amazonses.com.

Re: [Django] #34455: i18n_patterns() not respecting prefix_default_language=False

[Django]

#34455: i18n_patterns() not respecting prefix_default_language=False
-+-
 Reporter:  Oussama Jarrousse|Owner:  Mohit
 |  Singh Sinsniwal
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  4.2
  Internationalization   |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  internationalization, i18n,|
  prefix_default_language|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Sarah Boyce):

 Hi Mohit Singh Sinsniwal 👋 sorry I started to have a look and should have
 said so on the ticket

 You can see here where I think the issue could be solved (doesn't mean
 it's where it should be https://github.com/django/django/pull/16735).
 I think it's something around the whole `en-us` falling back to `en` and
 then that is different to the setting value for `LANGUAGE_CODE` 🤔

 In general how I would approach a ticket is to write a regression test
 first and then see if you can get that passing without breaking things in
 other places

-- 
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/0107018757b8190e-5dda0ed0-c618-4cd9-a3b1-69915f700148-00%40eu-central-1.amazonses.com.

Re: [Django] #34455: i18n_patterns() not respecting prefix_default_language=False

[Django]

#34455: i18n_patterns() not respecting prefix_default_language=False
-+-
 Reporter:  Oussama Jarrousse|Owner:  Mohit
 |  Singh Sinsniwal
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  4.2
  Internationalization   |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  internationalization, i18n,|
  prefix_default_language|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mohit Singh Sinsniwal):

 * cc: Mohit Singh Sinsniwal (added)
 * status:  new => assigned


Comment:

 Mariusz, sorry for closing it, I went on a different track while solving
 the issue, and now I can replicate.
 I need your help in understanding the middleware. Locale class, what
 should be done with /admin/login/?next=/admin ?


 1. When /admin/login/?next=/admin is requested, it calls
 get_fallback_lanuage and redirects afterward to
 /en/admin/login/?next=/en/admin/
 get_faalback_language is taking the prefixed language. If we dont want
 that, then we can update the process_request function:
 OLD:
 def process_request(self, request):
 urlconf = getattr(request, "urlconf", settings.ROOT_URLCONF)
 i18n_patterns_used, _ = is_language_prefix_patterns_used(urlconf)
 language = translation.get_language_from_request(
 request, check_path=i18n_patterns_used
 )
 if not language:
 language = self.get_fallback_language(request)
 print('coo',language)
 translation.activate(language)
 request.LANGUAGE_CODE = translation.get_language()

 New:
 def process_request(self, request):
 urlconf = getattr(request, "urlconf", settings.ROOT_URLCONF)
 (
 i18n_patterns_used,
 prefixed_default_language,
 ) = is_language_prefix_patterns_used(urlconf)
 language = translation.get_language_from_request(
 request, check_path=i18n_patterns_used
 )
 language_from_path =
 translation.get_language_from_path(request.path_info)
 if (
 not language_from_path
 and i18n_patterns_used
 and not prefixed_default_language
 ):
 language = settings.LANGUAGE_CODE
 translation.activate(language)
 request.LANGUAGE_CODE = translation.get_language()

 I want to work on this issue and need your suggestion if I am on right
 track.


 Replying to [comment:12 Mariusz Felisiak]:
 > Replying to [comment:11 Mohit Singh Sinsniwal]:
 > > Unable to replicate the bug. For me, it works for both version 4.2 and
 4.1.7.
 > > I used LocaleMiddleware
 >
 > Please don't close already accepted tickets. I'm still able to reproduce
 the 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/010701875771297c-f83e2c5c-0418-4d31-9ef5-9d44a9079b12-00%40eu-central-1.amazonses.com.

Re: [Django] #12772: Allow loading template tags by fully qualified python module path

[Django]

#12772: Allow loading template tags by fully qualified python module path
-+
 Reporter:  Patryk Zawadzki  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Template system  |  Version:  1.2-beta
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by Patryk Zawadzki):

 * owner:  Patryk Zawadzki => (none)
 * status:  assigned => new


-- 
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/010701875767ce13-8080a69c-74ef-4356-8d4b-3f7e4bf1a3f1-00%40eu-central-1.amazonses.com.

Re: [Django] #470: Add Field.db_default for defining database defaults

[Django]

#470: Add Field.db_default for defining database defaults
-+-
 Reporter:  jws  |Owner:  Lily
 |  Foote
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  normal   |   Resolution:
 Keywords:  sql schema   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Lily Foote):

 * 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/01070187574dd98d-d843826c-d1bf-40ea-aae0-8882c44ca191-00%40eu-central-1.amazonses.com.

[Django] #34465: Handle malformed CSRF cookie

[Django]

#34465: Handle malformed CSRF cookie
--+-
   Reporter:  tresko  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  CSRF|Version:  4.1
   Severity:  Normal  |   Keywords:  csrf, 500 error
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+-
 If the CSRF cookie contains invalid characters then **CsrfViewMiddleware**
 middleware raises a 500 internal server error at each request.

 https://github.com/django/django/blob/main/django/middleware/csrf.py#L65
 can't handle invalid characters and raises **ValueError: substring not
 found** exception.

 Some clients like https://github.com/pjperez/httping send malformed CSRF
 cookie value. See the example:
 {{{
 "\"HpgYRzmZcUTBq8HW5Ms1ZpCcoKX2SLRa Max-Age=43200 Path=/
 
SameSite=Lax\\054stmpdid=zdfUYW3e0iLhc4_VfBHhoOGTidnz6mkYVU4yuvIx8ID9biwIrPVyFUdfcsbhZpZw0BteEJ7rXXZVKcaoshDtLe4
 Max-Age=220752000 Path=/ SameSite=Lax\" Max-Age=43200 Path=/
 SameSite=Lax\054stmpdid=OedsyDX-
 7s_guDKt1gZymYrTike8rzoZTmXpCeIMlGhPhR6LhfDh3Io3BlkdC3JoBuH4udHybYkC0LPy4_M9lpI
 Max-Age=220752000 Path=/ SameSite=Lax" Max-Age=43200 Path=/
 SameSite=Lax,stmpdid=nj7BSEFLimv_-
 VSAxllXPYtBSiTNpeK3ht6lrc9hKS92EW0vE4zPuP5-R5NNbsDBkNB7seF6Q2i06rrU2mSVZIA
 Max-Age=220752000 Path=/ SameSite=Lax
 }}}

 I recommend returning a 400 response code instead of raising a 500
 internal server error.

-- 
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/0107018756b93efe-a3eca85e-3e7e-49c1-8a70-b0f04448817f-00%40eu-central-1.amazonses.com.

Re: [Django] #373: Add support for multiple-column primary keys

[Django]

#373: Add support for multiple-column primary keys
-+-
 Reporter:  Jacob|Owner:  Clouds
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  database | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Wilson E. Husin):

 * cc: Wilson E. Husin (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/0107018756a2a96a-08c5e33f-6a18-4996-ad78-0b677614d5ee-00%40eu-central-1.amazonses.com.

Re: [Django] #34464: QuerySet.count() regression on Django 4.2 with values() and annotate()

[Django]

#34464: QuerySet.count() regression on Django 4.2 with values() and annotate()
-+-
 Reporter:  Ian Cubitt   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  postgresql   | 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/0107018756a1f257-1d6eec09-c4c8-4212-a425-86c20266c662-00%40eu-central-1.amazonses.com.

Re: [Django] #32577: Add support for `UUIDAutoField` `DEFAULT_AUTO_FIELD`

[Django]

#32577: Add support for `UUIDAutoField` `DEFAULT_AUTO_FIELD`
-+-
 Reporter:  Tomasz Wójcik|Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  3.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 Wilson E. Husin):

 * cc: Wilson E. Husin (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/01070187569b03a2-b641b5fe-f20f-4f3c-a47a-70ff8983fe43-00%40eu-central-1.amazonses.com.

Re: [Django] #34462: Deletions in admin panel create N + 1 queries

[Django]

#34462: Deletions in admin panel create N + 1 queries
-+-
 Reporter:  Mike Lissner |Owner:  Akash
 Type:   |  Kumar Sen
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:  performance  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Akash Kumar Sen):

 * owner:  nobody => Akash Kumar Sen
 * 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/01070187567266cc-bdbbc11f-a706-4419-adfc-1b77a1d238dd-00%40eu-central-1.amazonses.com.

Re: [Django] #34464: QuerySet.count() regression on Django 4.2 with values() and annotate()

[Django]

#34464: QuerySet.count() regression on Django 4.2 with values() and annotate()
-+-
 Reporter:  Ian Cubitt   |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  postgresql   | 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):

 * owner:  nobody => Simon Charette
 * 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/01070187566e4cd2-33c2214e-c2b1-4d6d-aa43-ca68f58a4389-00%40eu-central-1.amazonses.com.

Re: [Django] #34459: SearchVector() can return query strings that are unsafe to combine.

[Django]

#34459: SearchVector() can return query strings that are unsafe to combine.
-+-
 Reporter:  Patryk Zawadzki  |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  4.2
 Severity:  Release blocker  |   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
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"db49def5fc03757048d6725097d4c3da44e7ea84" db49def5]:
 {{{
 #!CommitTicketReference repository=""
 revision="db49def5fc03757048d6725097d4c3da44e7ea84"
 [4.2.x] Fixed #34459 -- Fixed SearchVector() crash for parameters with %
 symbol.

 Thanks Patryk Zawadzki for the report.

 Regression in 09ffc5c1212d4ced58b708cbbf3dfbfb77b782ca.

 Backport of 4bf4222010fd8e413963c6c873e4088614332ef9 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/0107018756586b1a-5206-bbd5-49ae-9c23-0b65e04801dc-00%40eu-central-1.amazonses.com.

Re: [Django] #34459: SearchVector() can return query strings that are unsafe to combine.

[Django]

#34459: SearchVector() can return query strings that are unsafe to combine.
-+-
 Reporter:  Patryk Zawadzki  |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  4.2
 Severity:  Release blocker  |   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:"4bf4222010fd8e413963c6c873e4088614332ef9" 4bf4222]:
 {{{
 #!CommitTicketReference repository=""
 revision="4bf4222010fd8e413963c6c873e4088614332ef9"
 Fixed #34459 -- Fixed SearchVector() crash for parameters with % symbol.

 Thanks Patryk Zawadzki for the report.

 Regression in 09ffc5c1212d4ced58b708cbbf3dfbfb77b782ca.
 }}}

-- 
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/0107018756576b22-fbb5d92c-dd62-4c75-803e-25f868f6a718-00%40eu-central-1.amazonses.com.

Re: [Django] #34463: WHERE clause example missing from Q() documentation

[Django]

#34463: WHERE clause example missing from Q() documentation
-+-
 Reporter:  ExTexan  |Owner:  Yahya Ali
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  4.2
 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:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"e68da20596847d6c165183bca52ebba570ccfdaa" e68da20]:
 {{{
 #!CommitTicketReference repository=""
 revision="e68da20596847d6c165183bca52ebba570ccfdaa"
 [4.2.x] Fixed #34463 -- Corrected code-block directives in docs.

 Thanks ExTexan for the report.
 Backport of 263db8af469f0f3a5bd8ddc4a7dd0154c3d1fbca 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/0107018756419155-55814543-d4e0-4af5-831c-b699164a6a22-00%40eu-central-1.amazonses.com.

Re: [Django] #34463: WHERE clause example missing from Q() documentation

[Django]

#34463: WHERE clause example missing from Q() documentation
-+-
 Reporter:  ExTexan  |Owner:  Yahya Ali
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  4.2
 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:  1|UI/UX:  0
-+-
Changes (by GitHub ):

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


Comment:

 In [changeset:"263db8af469f0f3a5bd8ddc4a7dd0154c3d1fbca" 263db8a]:
 {{{
 #!CommitTicketReference repository=""
 revision="263db8af469f0f3a5bd8ddc4a7dd0154c3d1fbca"
 Fixed #34463 -- Corrected code-block directives in docs.

 Thanks ExTexan for the report.
 }}}

-- 
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/010701875640cfb4-f68e1f85-5845-4e07-9599-dd392cc2cdbf-00%40eu-central-1.amazonses.com.

Re: [Django] #34463: WHERE clause example missing from Q() documentation

[Django]

#34463: WHERE clause example missing from Q() documentation
-+-
 Reporter:  ExTexan  |Owner:  Yahya Ali
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * 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/01070187563d06a3-11122e07-b351-4b5a-9dcc-2bfbf49a75c9-00%40eu-central-1.amazonses.com.

Re: [Django] #34028: Django 'static' template tag fails to generate URLs with SCRIPT_NAME prefix

[Django]

#34028: Django 'static' template tag fails to generate URLs with SCRIPT_NAME 
prefix
-+---
 Reporter:  Stewart Adam |Owner:  Sarah Boyce
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  dev
 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 Mariusz Felisiak ):

 In [changeset:"e34a54a36e2d7b35e8998fe60462e93a1a5424cf" e34a54a3]:
 {{{
 #!CommitTicketReference repository=""
 revision="e34a54a36e2d7b35e8998fe60462e93a1a5424cf"
 [4.2.x] Refs #34028 -- Doc'd that get_script_prefix() cannot be used
 outside of the request-response cycle.

 Backport of bdf59bff657975e577b86b194b39ec2f77983d2b 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/01070187563b63d3-10b73adc-ae6c-4b5c-821a-dda92d2dc31a-00%40eu-central-1.amazonses.com.

Re: [Django] #34028: Django 'static' template tag fails to generate URLs with SCRIPT_NAME prefix

[Django]

#34028: Django 'static' template tag fails to generate URLs with SCRIPT_NAME 
prefix
-+---
 Reporter:  Stewart Adam |Owner:  Sarah Boyce
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  dev
 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 GitHub ):

 In [changeset:"bdf59bff657975e577b86b194b39ec2f77983d2b" bdf59bf]:
 {{{
 #!CommitTicketReference repository=""
 revision="bdf59bff657975e577b86b194b39ec2f77983d2b"
 Refs #34028 -- Doc'd that get_script_prefix() cannot be used outside of
 the request-response cycle.
 }}}

-- 
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/01070187563ab420-fc2247ae-34d5-42c9-b83a-47a7182fe5a3-00%40eu-central-1.amazonses.com.

Re: [Django] #34463: WHERE clause example missing from Q() documentation

[Django]

#34463: WHERE clause example missing from Q() documentation
-+-
 Reporter:  ExTexan  |Owner:  Yahya Ali
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  4.2
 Severity:  Normal   |   Resolution:
 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 Yahya Ali):

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

-- 
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/010701875631e280-58de2b49-8598-44a4-b689-ccda384a3c44-00%40eu-central-1.amazonses.com.

Re: [Django] #34463: WHERE clause example missing from Q() documentation

[Django]

#34463: WHERE clause example missing from Q() documentation
-+-
 Reporter:  ExTexan  |Owner:  Yahya Ali
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Yahya Ali):

 * 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/01070187562adc84-564ac441-82d8-4d0e-82f0-e85a64e768a9-00%40eu-central-1.amazonses.com.

Re: [Django] #34455: i18n_patterns() not respecting prefix_default_language=False

[Django]

#34455: i18n_patterns() not respecting prefix_default_language=False
-+-
 Reporter:  Oussama Jarrousse|Owner:  Mohit
 |  Singh Sinsniwal
 Type:  Bug  |   Status:  new
Component:   |  Version:  4.2
  Internationalization   |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  internationalization, i18n,|
  prefix_default_language|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Oussama Jarrousse):

 Replying to [comment:14 Mariusz Felisiak]:
 > Oussama, thanks, would you like to prepare a patch?

 In theory, I would love to.
 However, I am not familiar enough with the core source code.

-- 
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/010701875606ff45-d9dd6e44-bb3e-4f75-b688-f7baf6984c60-00%40eu-central-1.amazonses.com.

Re: [Django] #34463: WHERE clause example missing from Q() documentation

[Django]

#34463: WHERE clause example missing from Q() documentation
-+-
 Reporter:  ExTexan  |Owner:  Yahya Ali
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  4.2
 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 Yahya Ali):

 * owner:  nobody => Yahya Ali
 * 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/0107018755f11938-d2f35f5a-9326-4b11-a121-b1859537a45a-00%40eu-central-1.amazonses.com.

Re: [Django] #34028: Django 'static' template tag fails to generate URLs with SCRIPT_NAME prefix

[Django]

#34028: Django 'static' template tag fails to generate URLs with SCRIPT_NAME 
prefix
-+---
 Reporter:  Stewart Adam |Owner:  Sarah Boyce
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  dev
 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 Mariusz Felisiak):

 * status:  assigned => closed
 * resolution:   => invalid
 * stage:  Accepted => Unreviewed


Comment:

 Let's document this caveat (see
 [https://github.com/django/django/pull/16714 PR]) and close this as
 "invalid". Discussion about constructing URLs outside of the request-
 response cycle (new feature) was moved to the #34461.

-- 
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/0107018755eaed6c-31d96b0c-2493-4042-80e4-bccdca0aa747-00%40eu-central-1.amazonses.com.

Re: [Django] #34464: QuerySet.count() regression on Django 4.2 with values() and annotate()

[Django]

#34464: QuerySet.count() regression on Django 4.2 with values() and annotate()
-+-
 Reporter:  Ian Cubitt   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  postgresql   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * 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/0107018755e60fbb-9effc16c-e5ac-4c25-9a06-04e1bdba74f0-00%40eu-central-1.amazonses.com.

Re: [Django] #34455: i18n_patterns() not respecting prefix_default_language=False

[Django]

#34455: i18n_patterns() not respecting prefix_default_language=False
-+-
 Reporter:  Oussama Jarrousse|Owner:  Mohit
 |  Singh Sinsniwal
 Type:  Bug  |   Status:  new
Component:   |  Version:  4.2
  Internationalization   |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  internationalization, i18n,|
  prefix_default_language|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 Oussama, thanks, would you like to prepare a patch?

-- 
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/0107018755a8d359-90be38be-ab64-463e-857a-6b02b0ebb95c-00%40eu-central-1.amazonses.com.

Re: [Django] #34464: QuerySet.count() regression on Django 4.2 with values() and annotate()

[Django]

#34464: QuerySet.count() regression on Django 4.2 with values() and annotate()
-+-
 Reporter:  Ian Cubitt   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  postgresql   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 Django 4.1:
 {{{#!sql
 SELECT COUNT(*) FROM (
 SELECT
 DATE_TRUNC('hour',
 "ticket_34464_samplemodel"."sample_datetime_field") AS "hour",
 COUNT(*) AS "hour_count"
 FROM "ticket_34464_samplemodel"
 GROUP BY
 DATE_TRUNC('hour',
 "ticket_34464_samplemodel"."sample_datetime_field")
 HAVING COUNT(*) >= 5
 ) subquery
 }}}
 Django 4.2:
 {{{#!sql
 SELECT COUNT(*) FROM (
 SELECT
 "ticket_34464_samplemodel"."id" AS "col1"
 FROM "ticket_34464_samplemodel"
 GROUP BY
 DATE_TRUNC('hour',
 "ticket_34464_samplemodel"."sample_datetime_field"),
 1
 HAVING COUNT(*) >= 5
 ) subquery
 }}}

-- 
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/0107018755a5f997-1a740126-6491-400e-85fc-9749e2e20a88-00%40eu-central-1.amazonses.com.

Re: [Django] #34455: i18n_patterns() not respecting prefix_default_language=False

[Django]

#34455: i18n_patterns() not respecting prefix_default_language=False
-+-
 Reporter:  Oussama Jarrousse|Owner:  Mohit
 |  Singh Sinsniwal
 Type:  Bug  |   Status:  new
Component:   |  Version:  4.2
  Internationalization   |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  internationalization, i18n,|
  prefix_default_language|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Oussama Jarrousse):

 Replying to [comment:11 Mohit Singh Sinsniwal]:
 > Unable to replicate the bug. For me, it works for both version 4.2 and
 4.1.7.
 > I used LocaleMiddleware

 here is a project to replicate the issue... it uses tox to setup two
 different environments and run a simple test in each environment.

 ​https://github.com/oussjarrousse/djangoproject-ticket-34455

-- 
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/0107018755a273b3-f4c9afcc-a57d-4a7a-ae08-24c0c99d320b-00%40eu-central-1.amazonses.com.

Re: [Django] #34464: QuerySet.count() regression on Django 4.2 with values() and annotate()

[Django]

#34464: QuerySet.count() regression on Django 4.2 with values() and annotate()
-+-
 Reporter:  Ian Cubitt   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  postgresql   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * cc: charette (added)
 * severity:  Normal => Release blocker


Comment:

 Thanks for the report!

 Regression in 59bea9efd2768102fc9d3aedda469502c218e9b7.
 Reproduced at 38e63c9e61152682f3ff982c85a73793ab6d3267.

-- 
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/0107018755a2348f-ae2f2242-fb9e-417b-a64a-1c379e2bad69-00%40eu-central-1.amazonses.com.

Re: [Django] #34464: QuerySet.count() regression on Django 4.2 with values() and annotate()

[Django]

#34464: QuerySet.count() regression on Django 4.2 with values() and annotate()
-+-
 Reporter:  Ian  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  postgresql   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ian):

 * Attachment "Screenshot 2023-04-06 at 09.30.15.png" added.

 Reproducing the issue using my sample code in 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/01070187557adf35-4ca0508e-f177-4fcd-8c75-cb39f418bf4a-00%40eu-central-1.amazonses.com.

[Django] #34464: QuerySet.count() regression on Django 4.2 with values() and annotate()

[Django]

#34464: QuerySet.count() regression on Django 4.2 with values() and annotate()
-+-
   Reporter:  Ian|  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  4.2
  layer (models, ORM)|
   Severity:  Normal |   Keywords:  postgresql
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 After upgrading to Django 4.2 we noticed incorrect results on some queries
 we use in reporting.

 We are using PostgreSQL as our database.
 Using psycopg2 or the new psycopg 3 support does not change the result.

 Sample model:

 {{{
 #!python
 class SampleModel(models.Model):
 sample_datetime_field = models.DateTimeField()
 }}}

 Example code to reproduce the issue:

 {{{
 #!python
 from bug_test.models import SampleModel
 from django.db.models import Count
 from django.db.models.functions import TruncHour
 from django.utils import timezone

 # Prepopulate 10 hours of sample data

 now = timezone.now()

 for i in range(10):
 field_value = now - timedelta(hours=1 + i)

 for i in range(5):
 SampleModel.objects.create(sample_datetime_field=field_value)

 # Affected query example

 qs =
 SampleModel.objects.all().annotate(hour=TruncHour('sample_datetime_field')).\
 values('hour').annotate(hour_count=Count('*')).filter(hour_count__gte=5)

 print(f"Count: {qs.count()}")  # Incorrectly returns 0. Returns correct
 result on Django 4.1
 print(f"Len: {len(qs)}")  # Returns correct result of 10
 }}}

-- 
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/01070187557a565a-d16028a8-2a67-48a8-90d8-22775287db52-00%40eu-central-1.amazonses.com.

Re: [Django] #34461: Constructing urls outside the request cycle

[Django]

#34461: Constructing urls outside the request cycle
--+--
 Reporter:  Sarah Boyce   |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  Core (Other)  |  Version:  dev
 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 Sarah Boyce):

 Sorry 👍 moved to here: https://groups.google.com/g/django-
 developers/c/YzRj7OXpLkk

-- 
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/01070187556bfdcb-a08c9708-3dce-4912-a50f-c19b7c47332a-00%40eu-central-1.amazonses.com.