date:20240418

Re: [Django] #24076: Query may fail with pytz exception

2024-04-18 Thread Django

#24076: Query may fail with pytz exception
---+-
 Reporter:  lvella |Owner:  Adam Zapletal
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by Adam Zapletal):

 * 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/0107018ef30a20c7-f59e1364-3d78-40b8-a53b-46e9a2f7d417-00%40eu-central-1.amazonses.com.

Re: [Django] #35389: stringformat filter in template breaks numeric localization

2024-04-18 Thread Django

#35389: stringformat filter in template breaks numeric localization
-+-
 Reporter:  Danic|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  5.0
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  locale,  | Triage Stage:
  localization   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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

Comment:

 It's explicitly
 [https://docs.djangoproject.com/en/stable/ref/templates/builtins/#stringformat
 documented] that `stringformat`:

 > ''Formats the variable according to the argument, a **string formatting
 specifier**. This specifier uses the **printf-style String Formatting
 syntax**, with the exception that the leading “%” is dropped.''

 and in Python docs you will find that `.` is always used as a decimal
 separate. `localize/unlocalize` doesn't affect strings so everything works
 as expected.
-- 
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/0107018ef292e791-3271df28-3490-407c-9246-eeb7d352e43a-00%40eu-central-1.amazonses.com.

Re: [Django] #35388: force_debug_cursor, assertNumQueries(), and CaptureQueriesContext() doesn't work in async. (was: `force_debug_cursor` does nothing in async)

2024-04-18 Thread Django

#35388: force_debug_cursor, assertNumQueries(), and CaptureQueriesContext() 
doesn't
work in async.
-+-
 Reporter:  James Ostrander  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  connection, db,  | Triage Stage:
  orm, force_debug_cursor, async |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * keywords:  connection, db, orm, force_debug_cursor => connection, db,
 orm, force_debug_cursor, async
 * resolution:   => needsinfo
 * status:  new => closed
 * summary:  `force_debug_cursor` does nothing in async =>
 force_debug_cursor, assertNumQueries(), and CaptureQueriesContext()
 doesn't work in async.
 * type:  Bug => New feature

Comment:

 Replying to [comment:3 James Ostrander]:
 > If the fix is something simple, ...

 No, it's not. I tried really hard few months ago and it's probably not
 doable, check out comments:
 - https://github.com/django/django/pull/14843#issuecomment-1023254514
 - https://github.com/django/django/pull/16543/files#r1115127795

 Marking as "needsinfo", because, as far as I'm aware there is a way to
 move it forward. We can reconsider this decision only if someone provides
 PoC.
-- 
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/0107018ef28d6c8d-e2d8dfb6-494b-4aa9-92d5-77f37371810a-00%40eu-central-1.amazonses.com.

[Django] #35389: stringformat filter in template breaks numeric localization

2024-04-18 Thread Django

#35389: stringformat filter in template breaks numeric localization
-+-
   Reporter:  Danic  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Template   |Version:  5.0
  system |   Keywords:  locale,
   Severity:  Normal |  localization
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 The stringformat filter breaks the numeric localization in the template.

 With these settings

 {{{
 LANGUAGES = [
 ("de", _("German")),
 ("en", _("English")),
 ]
 LANGUAGE_CODE = "de"
 TIME_ZONE = "Europe/Berlin"
 USE_I18N = True
 USE_TZ = True
 }}}

 the following template

 {{{
 {{ 3.14 }}
 {{ 3.14 | localize }}
 {{ 3.14 | unlocalize }}
 {{ 3.14159265359 | stringformat:".2f" }}
 {{ 3.14159265359 | stringformat:".2f" | localize }}
 {{ 3.14159265359 | stringformat:".2f" | unlocalize }}
 }}}


 Should print

 {{{
 3,14
 3,14
 3.14
 3,14
 3,14
 3.14
 }}}

 but factually prints

 {{{
 3,14
 3,14
 3.14
 3.14 <--
 3.14 <--
 3.14
 }}}
-- 
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/0107018ef242ea45-40333a8f-5463-40e9-b482-c4177c7b3cac-00%40eu-central-1.amazonses.com.

Re: [Django] #35382: Low contrast background color for fieldset headings within inline formsets

2024-04-18 Thread Django

#35382: Low contrast background color for fieldset headings within inline 
formsets
---+
 Reporter:  Sarah Boyce|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  5.0
 Severity:  Normal |   Resolution:
 Keywords:  accessibility  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Comment (by Natalia Bidart):

 Looks good! I checked the `base.css` and noticed we have a `--body-fg:
 #333` which also seems like a good option. I would remove the bold though!
-- 
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/0107018ef23d6716-ea875a80-6de6-4676-a8ef-9f59ae606b3c-00%40eu-central-1.amazonses.com.

Re: [Django] #35382: Low contrast background color for fieldset headings within inline formsets

2024-04-18 Thread Django

#35382: Low contrast background color for fieldset headings within inline 
formsets
---+
 Reporter:  Sarah Boyce|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  5.0
 Severity:  Normal |   Resolution:
 Keywords:  accessibility  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Comment (by Sarah Boyce):

 Black `#000`?
 [[Image(suggestion.png)]]
-- 
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/0107018ef232e475-aa44f1ca-bc63-4635-8f87-20438b3fbc0d-00%40eu-central-1.amazonses.com.

Re: [Django] #35382: Low contrast background color for fieldset headings within inline formsets

2024-04-18 Thread Django

#35382: Low contrast background color for fieldset headings within inline 
formsets
---+
 Reporter:  Sarah Boyce|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  5.0
 Severity:  Normal |   Resolution:
 Keywords:  accessibility  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by Sarah Boyce):

 * Attachment "suggestion.png" 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/0107018ef2324e73-50f8188d-e3e8-428d-9407-dc21cc8dcca2-00%40eu-central-1.amazonses.com.

Re: [Django] #35382: Low contrast background color for fieldset headings within inline formsets

2024-04-18 Thread Django

#35382: Low contrast background color for fieldset headings within inline 
formsets
---+
 Reporter:  Sarah Boyce|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  5.0
 Severity:  Normal |   Resolution:
 Keywords:  accessibility  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by Natalia Bidart):

 * component:  Uncategorized => contrib.admin
 * stage:  Unreviewed => Accepted
 * type:  Uncategorized => Bug

Comment:

 Thank you Sarah for the report, it makes sense. I checked and the
 background color is at least 16 years old!

 Do you have any concrete suggestion for the new font color?
-- 
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/0107018ef22c0fab-bce9b92b-0d0d-41e2-ab5f-5b05973d3aa1-00%40eu-central-1.amazonses.com.

Re: [Django] #35386: Incorrect checkbox help text alignment in multi-field rows

2024-04-18 Thread Django

#35386: Incorrect checkbox help text alignment in multi-field rows
-+-
 Reporter:  Adam Johnson |Owner:  Adam
 |  Johnson
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  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:  0|UI/UX:  1
-+-
Changes (by Sarah Boyce):

 * 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/0107018ef22a6b1d-a4ca2500-70f8-442f-8c34-d30f20fc4cd4-00%40eu-central-1.amazonses.com.

Re: [Django] #34976: startproject and startapp should provide feedback

2024-04-18 Thread Django

#34976: startproject and startapp should provide feedback
-+-
 Reporter:  Thibaud Colas|Owner:  Salvo
 Type:   |  Polizzi
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Management |  Version:  dev
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  tutorial, command,   | Triage Stage:  Accepted
  startproject, startapp |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
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/0107018ef2271175-73f4f42c-9e85-4ad6-988f-54810d5d1a1b-00%40eu-central-1.amazonses.com.

Re: [Django] #35388: `force_debug_cursor` does nothing in async

2024-04-18 Thread Django

#35388: `force_debug_cursor` does nothing in async
-+-
 Reporter:  James Ostrander  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  connection, db,  | Triage Stage:
  orm, force_debug_cursor|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by James Ostrander:

Old description:

> Django version: 4.2.11
> Python version: 3.12
>
> Settings:
>
> {{{
> DEBUG=False
> }}}
>
> For Pytest, where DEBUG=False, this removes a means of enabling query
> logging via override.
>

> **SYNC VIEW (WORKING):**
> {{{
> def query_test_sync(request: HttpRequest) -> HttpResponse:
> from django.db import connection
>
> connection.force_debug_cursor = True
>
> a = Thing.objects.first()
> return HttpResponse(f"First thing: {a.id}")
> }}}
>
> Log:
>
> {{{
> web-1   | [18/Apr/2024 14:48:35] "GET /test_query_sync/ HTTP/1.1" 200
> 31
> web-1   | (0.001) SELECT "thing_thing"."name", "thing_thing"."id"
> FROM "thing_thing" ORDER BY "thing_thing"."id" ASC LIMIT 1; args=();
> alias=default
> }}}
>

>
> **ASYNC VIEW (NOT WORKING):**
> {{{
> async def query_test_async(request: HttpRequest) -> HttpResponse:
> from django.db import connection
>
> connection.force_debug_cursor = True
>
> a = await Thing.objects.afirst()
> return HttpResponse(f"First thing: {a.id}")
> }}}
>
> Log:
>
> {{{
> web-1   | [18/Apr/2024 15:00:29] "GET /test_query_async/ HTTP/1.1"
> 200 31
> }}}
>

> Also worth noting: CaptureQueriesContext does not work in an async
> context.

New description:

 Django version: 4.2.11
 Python version: 3.12

 Settings:

 {{{
 DEBUG=False
 LOGGING = {
 "version": 1,
 "disable_existing_loggers": False,
 "handlers": {
 "default": {
 "level": "DEBUG",
 "class": "logging.StreamHandler",
 },
 },
 "loggers": {
 "django.db.backends": {
 "handlers": ["default"],
 "level": "DEBUG",
 "propagate": False,
 },
 },
 }
 }}}

 For Pytest, where DEBUG=False, this removes a means of enabling query
 logging via override.


 **SYNC VIEW (WORKING):**
 {{{
 def query_test_sync(request: HttpRequest) -> HttpResponse:
 from django.db import connection

 connection.force_debug_cursor = True

 a = Thing.objects.first()
 return HttpResponse(f"First thing: {a.id}")
 }}}

 Log:

 {{{
 web-1   | [18/Apr/2024 14:48:35] "GET /test_query_sync/ HTTP/1.1" 200
 31
 web-1   | (0.001) SELECT "thing_thing"."name", "thing_thing"."id" FROM
 "thing_thing" ORDER BY "thing_thing"."id" ASC LIMIT 1; args=();
 alias=default
 }}}



 **ASYNC VIEW (NOT WORKING):**
 {{{
 async def query_test_async(request: HttpRequest) -> HttpResponse:
 from django.db import connection

 connection.force_debug_cursor = True

 a = await Thing.objects.afirst()
 return HttpResponse(f"First thing: {a.id}")
 }}}

 Log:

 {{{
 web-1   | [18/Apr/2024 15:00:29] "GET /test_query_async/ HTTP/1.1" 200
 31
 }}}


 Also worth noting: CaptureQueriesContext does not work in an async
 context.

--
-- 
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/0107018ef21871b1-2eff41c3-0c3f-49f6-83f4-cf87e359f559-00%40eu-central-1.amazonses.com.

Re: [Django] #35388: `force_debug_cursor` does nothing in async

2024-04-18 Thread Django

#35388: `force_debug_cursor` does nothing in async
-+-
 Reporter:  James Ostrander  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  connection, db,  | Triage Stage:
  orm, force_debug_cursor|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by James Ostrander):

 If the fix is something simple, I would be happy to submit a 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/0107018ef1fdc0b8-9a1a3395-6d63-4eb9-bbe0-6e759f3b773d-00%40eu-central-1.amazonses.com.

Re: [Django] #35321: Django Admin in Mobile Safari zooms in on text inputs

2024-04-18 Thread Django

#35321: Django Admin in Mobile Safari zooms in on text inputs
-+-
 Reporter:  Simon Willison   |Owner:  Jason
 Type:   |  Hall
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  css, accessibility,  | Triage Stage:  Accepted
  mobile |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  1
-+-
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/0107018ef1f3e289-88d18f4c-1075-4f5d-9182-21e96d853275-00%40eu-central-1.amazonses.com.

Re: [Django] #24076: Query may fail with pytz exception

2024-04-18 Thread Django

#24076: Query may fail with pytz exception
---+-
 Reporter:  lvella |Owner:  Adam Zapletal
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  1.6
 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/0107018ef1de1886-3830dfe0-0751-4fd5-9882-053179408b43-00%40eu-central-1.amazonses.com.

Re: [Django] #35388: `force_debug_cursor` does nothing in async

2024-04-18 Thread Django

#35388: `force_debug_cursor` does nothing in async
-+-
 Reporter:  James Ostrander  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  connection, db,  | Triage Stage:
  orm, force_debug_cursor|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by James Ostrander):

 * version:  5.0 => 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/0107018ef1c2a849-de7e5953-7467-4cc4-9a3e-bd51699574d1-00%40eu-central-1.amazonses.com.

Re: [Django] #35388: `force_debug_cursor` does nothing in async

2024-04-18 Thread Django

#35388: `force_debug_cursor` does nothing in async
-+-
 Reporter:  jlost|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  connection, db,  | Triage Stage:
  orm, force_debug_cursor|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by jlost:

Old description:

> Django version: 4.2.11
> Python version: 3.12
>
> Settings:
>
> {{{
> DEBUG=False
> }}}
>
> For Pytest, where DEBUG=False, this removes a means of enabling query
> logging via override.
>

>
> {{{
> def query_test_sync(request: HttpRequest) -> HttpResponse:
> from django.db import connection
>
> connection.force_debug_cursor = True
>
> a = Thing.objects.first()
> return HttpResponse(f"First thing: {a.id}")
> }}}
>
> Log:
>
> {{{
> web-1   | [18/Apr/2024 14:48:35] "GET /test_query_sync/ HTTP/1.1" 200
> 31
> web-1   | (0.001) SELECT "thing_thing"."name", "thing_thing"."id"
> FROM "thing_thing" ORDER BY "thing_thing"."id" ASC LIMIT 1; args=();
> alias=default
> }}}
>

>

> {{{
> async def query_test_async(request: HttpRequest) -> HttpResponse:
> from django.db import connection
>
> connection.force_debug_cursor = True
>
> a = await Thing.objects.afirst()
> return HttpResponse(f"First thing: {a.id}")
> }}}
>
> Log:
>
> {{{
> web-1   | [18/Apr/2024 15:00:29] "GET /test_query_async/ HTTP/1.1"
> 200 31
> }}}
>

> Also worth noting: CaptureQueriesContext does not work in an async
> context.

New description:

 Django version: 4.2.11
 Python version: 3.12

 Settings:

 {{{
 DEBUG=False
 }}}

 For Pytest, where DEBUG=False, this removes a means of enabling query
 logging via override.


 **SYNC VIEW (WORKING):**
 {{{
 def query_test_sync(request: HttpRequest) -> HttpResponse:
 from django.db import connection

 connection.force_debug_cursor = True

 a = Thing.objects.first()
 return HttpResponse(f"First thing: {a.id}")
 }}}

 Log:

 {{{
 web-1   | [18/Apr/2024 14:48:35] "GET /test_query_sync/ HTTP/1.1" 200
 31
 web-1   | (0.001) SELECT "thing_thing"."name", "thing_thing"."id" FROM
 "thing_thing" ORDER BY "thing_thing"."id" ASC LIMIT 1; args=();
 alias=default
 }}}



 **ASYNC VIEW (NOT WORKING):**
 {{{
 async def query_test_async(request: HttpRequest) -> HttpResponse:
 from django.db import connection

 connection.force_debug_cursor = True

 a = await Thing.objects.afirst()
 return HttpResponse(f"First thing: {a.id}")
 }}}

 Log:

 {{{
 web-1   | [18/Apr/2024 15:00:29] "GET /test_query_async/ HTTP/1.1" 200
 31
 }}}


 Also worth noting: CaptureQueriesContext does not work in an async
 context.

--
-- 
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/0107018ef1c0b582-3162a507-8b4b-4470-89e0-1debecb85331-00%40eu-central-1.amazonses.com.

[Django] #35388: `force_debug_cursor` does nothing in async

2024-04-18 Thread Django

#35388: `force_debug_cursor` does nothing in async
-+-
   Reporter:  jlost  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  5.0
  layer (models, ORM)|   Keywords:  connection, db,
   Severity:  Normal |  orm, force_debug_cursor
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Django version: 4.2.11
 Python version: 3.12

 Settings:

 {{{
 DEBUG=False
 }}}

 For Pytest, where DEBUG=False, this removes a means of enabling query
 logging via override.



 {{{
 def query_test_sync(request: HttpRequest) -> HttpResponse:
 from django.db import connection

 connection.force_debug_cursor = True

 a = Thing.objects.first()
 return HttpResponse(f"First thing: {a.id}")
 }}}

 Log:

 {{{
 web-1   | [18/Apr/2024 14:48:35] "GET /test_query_sync/ HTTP/1.1" 200
 31
 web-1   | (0.001) SELECT "thing_thing"."name", "thing_thing"."id" FROM
 "thing_thing" ORDER BY "thing_thing"."id" ASC LIMIT 1; args=();
 alias=default
 }}}




 {{{
 async def query_test_async(request: HttpRequest) -> HttpResponse:
 from django.db import connection

 connection.force_debug_cursor = True

 a = await Thing.objects.afirst()
 return HttpResponse(f"First thing: {a.id}")
 }}}

 Log:

 {{{
 web-1   | [18/Apr/2024 15:00:29] "GET /test_query_async/ HTTP/1.1" 200
 31
 }}}


 Also worth noting: CaptureQueriesContext does not work in an async
 context.
-- 
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/0107018ef1bf7c70-fd571cc0-42d2-4c7d-8b15-59939b2b2891-00%40eu-central-1.amazonses.com.

Re: [Django] #22997: Migration fails when removing explicit primary key (Postgres)

2024-04-18 Thread Django

#22997: Migration fails when removing explicit primary key (Postgres)
-+
 Reporter:  a.lloyd.flanagan@…   |Owner:  bcail
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  migrate primary_key  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by bcail):

 * 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/0107018ef1bb2d2d-314ca744-e3de-45a4-80bf-da3a1945b01d-00%40eu-central-1.amazonses.com.

Re: [Django] #32935: Test suite fails with sqlite 3.36 and spatialite 5.

2024-04-18 Thread Django

#32935: Test suite fails with sqlite 3.36 and spatialite 5.
-+--
 Reporter:  David Smith  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  GIS  |  Version:  4.2
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Comment (by Natalia Bidart):

 #35387 is a dupe of this one.
-- 
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/0107018ef18e9c47-4b4cf946-e757-4b50-85ca-147ffbdcbcd1-00%40eu-central-1.amazonses.com.

Re: [Django] #35387: Django's Spatialite backend throws errors with Spatialite 5.0.1

2024-04-18 Thread Django

* cc: David Smith (removed)
* easy: 1 => 0
* resolution: => duplicate
* status: new => closed

Comment:

Nikolas, I missed an important detail from the other Django ticket that
you linked (#32935). Thank you Sarah for pointing this out! And sorry
David for the unnecessary CC.

As per the conversation in #32935, this has been discussed and is not an
issue with Django and is instead, an issue with sqlite3 v.3.36+
compatibility with Spatialite 5.0.1 when not compiled with
`-DSQLITE_ALLOW_ROWID_IN_VIEW` option.

Django is using `InitSpatialMetaDataFull` in 5.0 [https://www.gaia-
gis.it/fossil/libspatialite/info/2ab2aeb5d1c9a0458b64b8afd4be4ce7527b059c
as per the docs for 5.0], specifically

Please remember that now in SpatiaLite-5.0.0 InitSpatialMetaDataFull
represents the preferred method for creating all metadata tables required
by this version.
InitSpatialMetaData is still maintained so to not break historical
compatibility, but should no longer be used.

Some workarounds have been discussed, including downgrading to Spatialite
4.2, upgrade to 5.1, or recomplie sqlite with the flag above.
This is a good discussion on the issue: https://groups.google.com/g
/spatialite-users/c/SnNZt4AGm_o

It seems that the people most impacted are using Ubuntu 22.04 which has
this troubling combination of sqlite and spatialite but Ubuntu 24.04 will
be released soon in a week and uses spatialite 5.1.

In summary, Django would not be incorporating a workaround such as the one
proposed. We might be able to accept a patch that resolves this
compatibility issue ONLY if that doesn't go against official doc
recommendations. But also please consider that any patch for Django would
be targeting Django 5.1 to be released (at the earliest) in August. I
don't think anyone should rely on a patch to Django to solve this issue
for them.
--
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/0107018ef18df7bc-5ec1019e-f696-4ff6-af6f-aa63c0716905-00%40eu-central-1.amazonses.com.

Re: [Django] #35387: Django's Spatialite backend throws errors with Spatialite 5.0.1

2024-04-18 Thread Django

#35387: Django's Spatialite backend throws errors with Spatialite 5.0.1
-+-
 Reporter:  Nikolas N|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  spatialite   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Natalia Bidart):

 * cc: David Smith (added)

Comment:

 David, would you have any advice on this report? Can you reproduce as
 well? Thank you!
-- 
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/0107018ef15a8881-51b48b47-4ac3-4a7c-a292-6dc0d04eb477-00%40eu-central-1.amazonses.com.

Re: [Django] #35194: Postgres 16.2 with _iexact leads to IndeterminateCollation

2024-04-18 Thread Django

#35194: Postgres 16.2 with _iexact leads to IndeterminateCollation
-+-
 Reporter:  Aldalen  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Release blocker  |   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 Sarah Boyce):

 * has_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/0107018ef15a56c7-829c7396-60a5-4806-bee2-010f6cf2e375-00%40eu-central-1.amazonses.com.

Re: [Django] #35387: Django's Spatialite backend throws errors with Spatialite 5.0.1

2024-04-18 Thread Django

#35387: Django's Spatialite backend throws errors with Spatialite 5.0.1
-+-
 Reporter:  Nikolas N|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  spatialite   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Comment (by Natalia Bidart):

 Hello Nikolas, thank you for this ticket! Do you have a link to the
 Spatialite bug or conversation about the issue you describe? Do we know
 exactly which versions are affected? I'm a little concerned that the PR
 hardcodes a single version and there may be more versions affected?
-- 
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/0107018ef1588b13-ac4ca5cd-6ce7-480f-b96d-d5d7b363db07-00%40eu-central-1.amazonses.com.

Re: [Django] #35194: Postgres 16.2 with _iexact leads to IndeterminateCollation

2024-04-18 Thread Django

#35194: Postgres 16.2 with _iexact leads to IndeterminateCollation
-+-
 Reporter:  Aldalen  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Release blocker  |   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 Natalia Bidart):

 * cc: David Sanders (added)

Comment:

 David, I think you have successfully engaged with the PostgreSQL team/devs
 in the past, leading to productive conversations. Would you have some
 availability to reach out to them again to seek their assistance in
 debugging this specific issue we're encountering with PostgreSQL >= 12.18,
 13.14, 14.11, 15.6, 16.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/0107018ef15255de-c87fa60f-dfca-41b3-b386-9adfac692230-00%40eu-central-1.amazonses.com.

Re: [Django] #35386: Incorrect checkbox help text alignment in multi-field rows

2024-04-18 Thread Django

#35386: Incorrect checkbox help text alignment in multi-field rows
---+
 Reporter:  Adam Johnson   |Owner:  Adam Johnson
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  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:  0  |UI/UX:  1
---+
Changes (by Adam Johnson):

 * version:  dev => 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/0107018ef14c0414-344ada50-d811-4de9-9feb-8df51e74f005-00%40eu-central-1.amazonses.com.

Re: [Django] #33497: Database persistent connections do not work with ASGI in 4.0

2024-04-18 Thread Django

#33497: Database persistent connections do not work with ASGI in 4.0
-+-
 Reporter:  Stenkar  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ASGI, Database,  | Triage Stage:  Accepted
  async  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Suraj Shaw):

 * cc: Suraj Shaw (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/0107018ef13bac8c-a66e2e0d-86c0-4829-9f40-ea7e5abfe2db-00%40eu-central-1.amazonses.com.

Re: [Django] #33497: Database persistent connections do not work with ASGI in 4.0

2024-04-18 Thread Django

#33497: Database persistent connections do not work with ASGI in 4.0
-+-
 Reporter:  Stenkar  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ASGI, Database,  | Triage Stage:  Accepted
  async  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Suraj Shaw):

 I have created a  pull request for database connection pool support in
 oracle : https://github.com/django/django/pull/17834
 It would be great if people experiencing the same problem could test this
 with oracle backend (this would probably help in getting it merged).
-- 
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/0107018ef13a7dfe-e6d22ae4-4adc-45a5-a3e6-9fecf56b2ebc-00%40eu-central-1.amazonses.com.

Re: [Django] #35386: Incorrect checkbox help text alignment in multi-field rows

2024-04-18 Thread Django

#35386: Incorrect checkbox help text alignment in multi-field rows
---+
 Reporter:  Adam Johnson   |Owner:  Adam Johnson
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+
Changes (by Natalia Bidart):

 * cc: Tom Carrick (added)
 * stage:  Unreviewed => Accepted
 * ui_ux:  0 => 1

Comment:

 Thank you Adam, great catch!
-- 
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/0107018ef1352af6-96ff7b35-bef1-4ad1-bb35-a061451dce4c-00%40eu-central-1.amazonses.com.

Re: [Django] #35194: Postgres 16.2 with _iexact leads to IndeterminateCollation

2024-04-18 Thread Django

#35194: Postgres 16.2 with _iexact leads to IndeterminateCollation
-+-
 Reporter:  Aldalen  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 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 Simon Charette):

 It is effectively a solution but I'm not convinced this will do more good
 than harm.

 #3575 has been merged 16 years ago this means in between now and then
 thousands of projects were created and added a functional index on
 `UPPER("col")` to make `i(exact|contains|startwith)` use an index and the
 moment they upgrade to a minor version of 5.0 their database will start
 running slow queries as their indices will be unsuables.

 On the other hand we have a bug in a newly introduced feature for a very
 particular use case that might be affecting only a few users (must use
 generated field, must be on a latest version of Postgres, must use
 `i(exact|contains|startwith)`.

 I appreciate the intent to solve this issue but I think we need to dig
 deeper to truly understand ''why'' this is happening before jumping to
 conclusions here as there are no true urgency to get things right here;
 the ''release blocker'' assignment is self-imposed and nothing prevents us
 from deferring a solution to this problem to a future 5.0 release if we
 can't understand why this is happening before the May release as for all
 we know if might be a bug in Postgres itself.

 I tried reaching out on libera.chat#postgres IRC to get an answer but no
 one could answer me their (first time this happens) so I was planing to
 reach out to their mailing list this week but I might run out of time so
 if someone feels comfortable doing so please do.

 To summarize I think we should understand why this is happening before
 taking any potential harmful action here. For all we know many other
 functions and lookups could be affected and this is just the tip of the
 iceberg.
-- 
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/0107018ef121a8ca-7c7d6268-be24-4287-8d76-7eb808070607-00%40eu-central-1.amazonses.com.

Re: [Django] #35386: Incorrect checkbox help text alignment in multi-field rows

2024-04-18 Thread Django

#35386: Incorrect checkbox help text alignment in multi-field rows
---+
 Reporter:  Adam Johnson   |Owner:  Adam Johnson
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  dev
 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
---+
Comment (by Adam Johnson):

 I ran a bisect and confirmed this was a regression in
 96a598356a9ea8c2c05b22cadc12e256a3b295fd, before which checkboxes would be
 densely packed:

 [[Image(https://code.djangoproject.com/raw-
 attachment/ticket/35386/Xnapper-2024-04-18-12.58.34.png, 599px)]]
-- 
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/0107018ef116568d-09149aaf-b7d2-4390-bf41-9142cd5a33dd-00%40eu-central-1.amazonses.com.

Re: [Django] #35386: Incorrect checkbox help text alignment in multi-field rows

2024-04-18 Thread Django

#35386: Incorrect checkbox help text alignment in multi-field rows
---+
 Reporter:  Adam Johnson   |Owner:  Adam Johnson
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  dev
 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 Adam Johnson):

 * Attachment "Xnapper-2024-04-18-12.58.34.png" added.

 previous-dense
-- 
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/0107018ef115fb4b-26d134d8-486e-4b6a-bb48-12fd3109d083-00%40eu-central-1.amazonses.com.

Re: [Django] #34994: Visual regression in admin checkboxes on mobile

2024-04-18 Thread Django

#34994: Visual regression in admin checkboxes on mobile
-+-
 Reporter:  Tom Carrick  |Owner:  Tom
 |  Carrick
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  4.2
 Severity:  Release blocker  |   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 Adam Johnson):

 This is still broken for fieldsets with a checkbox plus another field on
 the same line, like:

 {{{
 class SwitcherAdmin(admin.ModelAdmin):
 fieldsets = [
 (
 None,
 {
 "fields": [
 ("up", "down"),
 ],
 },
 ),
 ]
 }}}

 [[Image(https://code.djangoproject.com/raw-
 attachment/ticket/34994/Xnapper-2024-04-18-12.31.19.png, 640px)]]

 This is due to `checkbox-row` being only applied when there’s a single
 checkbox in the row. I am making a small PR that fixes this issue and
 another, #35386. Follw on that 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/0107018ef10bbe60-5050db8a-1e49-4ba4-83a5-fd4595657fb1-00%40eu-central-1.amazonses.com.

Re: [Django] #35386: Incorrect checkbox help text alignment in multi-field rows

2024-04-18 Thread Django

#35386: Incorrect checkbox help text alignment in multi-field rows
---+
 Reporter:  Adam Johnson   |Owner:  Adam Johnson
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  dev
 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 Adam Johnson):

 * has_patch:  0 => 1
 * owner:  nobody => Adam Johnson
 * status:  new => assigned


Old description:

> For a single checkbox, styles align the help under the checkbox:
>
> ...
>

> When the checkbox appears with any other field in the same line, this is
> undone:
>
> ...
>
> Example admin:
>
> {{{
> from django.contrib import admin
> from example.models import Switcher
>

> class SwitcherAdmin(admin.ModelAdmin):
> fieldsets = [
> (
> None,
> {
> "fields": [
> ("up", "down"),
> ],
> },
> ),
> ]
>

> admin.site.register(Switcher, SwitcherAdmin)
> }}}
>
> (It doesn’t matter if the other field is a checkbox or not.)

New description:

 For a single checkbox, styles align the help under the checkbox:

 [[Image(https://code.djangoproject.com/raw-
 attachment/ticket/35386/Xnapper-2024-04-16-10.31.32.png, 558px)]]


 When the checkbox appears with any other field in the same line, this is
 undone:

 [[Image(https://code.djangoproject.com/raw-
 attachment/ticket/35386/Xnapper-2024-04-16-10.31.15.png, 592px)]]

 Example admin:

 {{{
 from django.contrib import admin
 from example.models import Switcher


 class SwitcherAdmin(admin.ModelAdmin):
 fieldsets = [
 (
 None,
 {
 "fields": [
 ("up", "down"),
 ],
 },
 ),
 ]


 admin.site.register(Switcher, SwitcherAdmin)
 }}}

 (It doesn’t matter if the other field is a checkbox or not.)

 Changing `fieldset.html` so `checkbox-row` is applied unconditionally to
 checkbox-containing field boxes fixes this regression, plus #34994:

 [[Image(https://code.djangoproject.com/raw-
 attachment/ticket/35386/Xnapper-2024-04-16-10.31.01.png, 562px)]]

--
-- 
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/0107018ef10b2b3a-6c841b35-6692-44b9-b3cf-6223855d2390-00%40eu-central-1.amazonses.com.

Re: [Django] #35386: Incorrect checkbox help text alignment in multi-field rows

2024-04-18 Thread Django

#35386: Incorrect checkbox help text alignment in multi-field rows
---+--
 Reporter:  Adam Johnson   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  dev
 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
---+--
Changes (by Adam Johnson):

 * Attachment "Xnapper-2024-04-16-10.31.01.png" added.

 fixed
-- 
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/0107018ef10a69f3-a775eff5-6f2b-4d20-8d32-c14dd84a2bb3-00%40eu-central-1.amazonses.com.

[Django] #35387: Django's Spatialite backend throws errors with Spatialite 5.0.1

2024-04-18 Thread Django

#35387: Django's Spatialite backend throws errors with Spatialite 5.0.1
-+-
   Reporter:  Nikolas N  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  5.0
  layer (models, ORM)|
   Severity:  Normal |   Keywords:  spatialite
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 Spatialite 5.0.1 contains a bug which causes the `SELECT
 InitSpatialMetaDataFull(1)` statement called by django's database wrapper
 to fail with the error:
 {{{
 django.db.utils.OperationalError: error in trigger
 ISO_metadata_reference_row_id_value_insert: no such column: rowid
 }}}

 Although this is primarily a bug in Spatialite, it is expected for Django
 to be compatible with this version of Spatialite, as it is shipping in
 many current distributions, and upgrading to Spatialite 5.1 is not always
 straightforward.

 There is a patch for this issue here:
 https://github.com/django/django/pull/18083

 I was told patches aren't accepted for closed tickets
 (https://code.djangoproject.com/ticket/32935), so I am opening this new
 ticket, as the core issue here with Django + Spatialite 5.0.1 remains
 unresolved.
-- 
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/0107018ef10a03d4-65facf47-8a68-4572-ae88-3234e4a55aac-00%40eu-central-1.amazonses.com.

Re: [Django] #35386: Incorrect checkbox help text alignment in multi-field rows

2024-04-18 Thread Django

#35386: Incorrect checkbox help text alignment in multi-field rows
---+--
 Reporter:  Adam Johnson   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  dev
 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
---+--
Changes (by Adam Johnson):

 * Attachment "Xnapper-2024-04-16-10.31.15.png" added.

 double-incorrect
-- 
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/0107018ef107d715-76c46ba1-1af9-450e-b09b-f70d07f3428a-00%40eu-central-1.amazonses.com.

Re: [Django] #35386: Incorrect checkbox help text alignment in multi-field rows

2024-04-18 Thread Django

#35386: Incorrect checkbox help text alignment in multi-field rows
---+--
 Reporter:  Adam Johnson   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  dev
 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
---+--
Changes (by Adam Johnson):

 * Attachment "Xnapper-2024-04-16-10.31.32.png" added.

 single-correct
-- 
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/0107018ef107a658-834163f2-a3d0-44c3-9f2a-5630a766f429-00%40eu-central-1.amazonses.com.

[Django] #35386: Incorrect checkbox help text alignment in multi-field rows

2024-04-18 Thread Django

#35386: Incorrect checkbox help text alignment in multi-field rows
-+
   Reporter:  Adam Johnson   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.admin  |Version:  dev
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 For a single checkbox, styles align the help under the checkbox:

 ...


 When the checkbox appears with any other field in the same line, this is
 undone:

 ...

 Example admin:

 {{{
 from django.contrib import admin
 from example.models import Switcher


 class SwitcherAdmin(admin.ModelAdmin):
 fieldsets = [
 (
 None,
 {
 "fields": [
 ("up", "down"),
 ],
 },
 ),
 ]


 admin.site.register(Switcher, SwitcherAdmin)
 }}}

 (It doesn’t matter if the other field is a checkbox or not.)
-- 
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/0107018ef1075719-380d34cd-a63c-436f-a69b-7b9e023b7975-00%40eu-central-1.amazonses.com.

Re: [Django] #34994: Visual regression in admin checkboxes on mobile

2024-04-18 Thread Django

#34994: Visual regression in admin checkboxes on mobile
-+-
 Reporter:  Tom Carrick  |Owner:  Tom
 |  Carrick
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  4.2
 Severity:  Release blocker  |   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
-+-
Changes (by Adam Johnson):

 * Attachment "Xnapper-2024-04-18-12.31.19.png" added.

 two checkboxes centred
-- 
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/0107018ef0fc495f-3e4c34b6-a87b-4ddb-be36-22d7247e3198-00%40eu-central-1.amazonses.com.

[Django] #35385: Psiholog. Психолог что лечит.

2024-04-18 Thread Django

#35385: Psiholog. Психолог что лечит.
-+-
   Reporter: |  Owner:  nobody
  LatashaGulley33|
   Type:  New| Status:  new
  feature|
  Component:  Template   |Version:  2.0
  system |   Keywords:  Психолог доктор Все
   Severity:  Release|  психологи сайт Детские психологи в
  blocker|  москве лучшие форум
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 [https://batmanapollo.ru/ Нужно ли психологу медицинское образование]

 [https://batmanapollo.ru/ Прием психолога в москве цена]

 [https://batmanapollo.ru/ Самый лучший психолог в москве]















 - - -

 Очень часто случается так, что люди не понимают на что им в первую очередь
 стоит обратить внимание, какое направление для инвестиции выбрать. Для
 того, чтобы решить эту проблему, необходимо пройти диагностику. Это можно
 сделать при помощи специалиста или самостоятельно. Возможно, вы уже
 знаете, что для вас является самым любимым и интересным делом, которое вам
 бы хотелось развивать и при помощи которого вы бы хотели зарабатывать
 деньги. К сожалению, это не всегда то, чем занимается человек в данный
 момент. Нужно иметь смелость и гибкость, чтобы заниматься тем, что тебе
 нравится и то, что ты любишь. В итоге человек достигает в этом отличных
 результатов. Сервис предлагает несколько психотерапевтов на основе вашей
 анкеты. Если из предложенных вариантов никто не подошел, можно выбрать еще
 раз бесплатно. Формат встреч — онлайн или очно в МосквеЦена: сервис
 бесплатный, о цене за сеанс вы договариваетесь с психотерапевтом. На нашем
 сайте собраны анкеты практикующих специалистов, специализирующихся на
 различных вопросах. Уточните значимые для вас критерии поиска, почитайте
 отзывы о [https://batmanapollo.ru/ Найти психолога в москве отзывы]х,
 прислушайтесь к интуиции, выберите того человека, с которым вам будет
 комфортно общаться и, не откладывая, записывайтесь на консультацию.

 Психологическая помощь заключается в обнаружении и анализе причин
 жизненных сложностей, выявлении подлинного внутреннего потенциала
 личности. Психолог помогает взглянуть на себя и ситуацию объективно и без
 лишних эмоций, рассмотреть разные варианты ее восприятия и отыскать выход.
 Выкинула деньги на ветер в итоге получив абсолютно пассивного "спеца",
 который вообще ничего за сессию не сказал. Ну кроме сакраментального
 "время вышло и давайте я вас запишу на новый сеанс". Я понимаю что
 психолог должен послушать клиента. Но тут реально было ощущение что я
 задорого арендовала кресло для того чтобы посидеть напротив человека.
 Сейчас модно изучать языки программирования и другие технологии, так или
 и[https://batmanapollo.ru/ Запись на прием к психологу]че связанные с
 интернетом и IT. И это неудивительно, потому что такие навыки способны
 принести немалые деньги, если достаточно хорошо ими овладеть. Однако если
 к этому не лежит душа, то лучше себя не заставлять, а подыскать то, что
 будет близко и сможет обеспечить определенный доход или другие
 интересующие "дивиденды". Если же начать изучать что-то только ради денег,
 существует большой риск быстро забросить начатое дело.

 Я не захотела жить наедине со своими ментальными демонами и решила
 покопаться в разнообразии психологических сервисов: их оказалось очень
 много, на любой вкус и цвет, с их помощью вы сможете записаться как на
 очную, так и на онлайн-консультацию. Зигмунд — сервис, который «помогает
 строить комфортные отношения с собой и окружающими». Чтобы вам было легче
 идти к результату, вы получите чек-лист по подготовке к первой сессии,
 гайд обо всех тонкостях психотерапии и тетрадь психотерапии. Эти материалы
 помогут сделать сессии с вашим специалистом еще более эффективными.
 Сервис, изюминкой которого является возможность вести постоянный диалог в
 виде сообщений с вашим психологом в мессенджере. Вы можете растянуть
 общение со специалистом на неделю, либо за два часа переписки обсудить с
 психологом все, что вас беспокоит.

 Основная работа у меня интеллектуальная. Но постоянно тянет что-то
 поделать руками. Видимо, мозг и психика так себя защищают от перегруза и
 выгорания. Пилим периодически с другом по выходным и коммерческие штуки, в
 том числе и для своего бизнеса. Часто это какие-то тиражные вещи, где
 нужно сделать много одинаковых деталей. Это очень хорошо разгружает мозг.
 Строгий отбор специалистов — сервис работает только с самыми опытными.
 Отбор проходят лишь 17% от всех соискателей. Удобный тест упростит поиск
 подходящего

Re: [Django] #35384: Assigning a file without a name property to a FileField results in file getting discarded silently

2024-04-18 Thread Django

#35384: Assigning a file without a name property to a FileField results in file
getting discarded silently
-+-
 Reporter:  john-parton  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  5.0
  (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 Lily Foote):

 * cc: Lily Foote (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/0107018ef08b9701-196bc228-aaf1-4104-b27b-a5473e0f8d23-00%40eu-central-1.amazonses.com.

Re: [Django] #35194: Postgres 16.2 with _iexact leads to IndeterminateCollation

2024-04-18 Thread Django

#35194: Postgres 16.2 with _iexact leads to IndeterminateCollation
-+-
 Reporter:  Aldalen  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Release blocker  |   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 Sarah Boyce):

 * has_patch:  0 => 1

Comment:

 It's an idea, we might get a better idea 
-- 
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/0107018ef040fa06-451b7b09-2b5f-4571-a98d-6a699bc5af07-00%40eu-central-1.amazonses.com.

Re: [Django] #35384: Assigning a file without a name property to a FileField results in file getting discarded silently

2024-04-18 Thread Django

#35384: Assigning a file without a name property to a FileField results in file
getting discarded silently
-+-
 Reporter:  john-parton  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  5.0
  (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 Sarah Boyce):

 * stage:  Unreviewed => Accepted

Comment:

 Thank you for the analysis and discussions 
-- 
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/0107018eefd9a6c1-4f48846a-31cf-4ed6-890a-baf439afcbd1-00%40eu-central-1.amazonses.com.

Re: [Django] #35383: Add support for `IF NOT EXISTS` when creating postgres indexes concurrently

2024-04-18 Thread Django

#35383: Add support for `IF NOT EXISTS` when creating postgres indexes 
concurrently
-+-
 Reporter:  Marcelo  |Owner:  (none)
 Type:  New feature  |   Status:  closed
Component:  contrib.postgres |  Version:  5.0
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  database, postgres,  | Triage Stage:
  index, concurrently|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sarah Boyce):

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

Comment:

 Duplicate of #34729 which was also discussed and resolved as wontfix.
-- 
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/0107018eefd49df4-0ad7ca40-c0f3-446b-8c4d-3fdf7949ede5-00%40eu-central-1.amazonses.com.

44 matches

Mail list logo