date:20240620

Re: [Django] #35334: Update Oracle backend supports_sequence_reset = True

2024-06-20 Thread Django

#35334: Update Oracle backend supports_sequence_reset = True
-+-
 Reporter:  David Sanders|Owner:
 Type:   |  amultani1234
  Cleanup/optimization   |   Status:  assigned
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 amultani1234):

 * owner:  nobody => amultani1234
 * 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/01070190398db813-7c81a159-6639-4b72-832e-a16674b6d4df-00%40eu-central-1.amazonses.com.

Re: [Django] #35543: Contribution: new management commands for contrib.auth (grantpermissions, revokepermissions)

2024-06-20 Thread Django

#35543: Contribution: new management commands for contrib.auth 
(grantpermissions,
revokepermissions)
--+--
 Reporter:  Florian Schieder  |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  contrib.auth  |  Version:  5.0
 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 Florian Schieder):

 Thank you very much for the quick response – I agree the ticket system is
 the wrong place to handle this proposal for the time being so I created a
 new [https://forum.djangoproject.com/t/contribution-new-management-
 commands-for-contrib-auth-grantpermissions-revokepermissions/32304 forum
 topic].
-- 
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/010701903980a699-93786945-b6d2-492a-873d-e6eea5d68c8c-00%40eu-central-1.amazonses.com.

Re: [Django] #35546: Modernize contributing pages to aling with current requirement of having an accepted ticket for non trivial changes

2024-06-20 Thread Django

#35546: Modernize contributing pages to aling with current requirement of 
having an
accepted ticket for non trivial changes
--+
 Reporter:  Natalia Bidart|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Sarah Boyce):

 * 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/0107019039506186-596aba26-bb96-44aa-aee9-1f57e727d376-00%40eu-central-1.amazonses.com.

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

2024-06-20 Thread Django

#28900: QuerySet.values() and values_list() for compound queries fails with
annotation.
-+-
 Reporter:  elliott-omosheye |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  union, values| 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
 * owner:  (none) => 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/01070190394860ec-8facc244-e9f9-4184-8e14-e19e73f2694f-00%40eu-central-1.amazonses.com.

Re: [Django] #35545: Fix create_permissions LookupErrors

2024-06-20 Thread Django

#35545: Fix create_permissions LookupErrors
--+
 Reporter:  Csirmaz Bendegúz  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  5.1
 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
--+
Description changed by Csirmaz Bendegúz:

Old description:

> [https://code.djangoproject.com/ticket/35408 #35408] introduced a bug in
> {{{contrib.auth}}}'s {{{create_permissions}}} function
> ([https://github.com/django/django/pull/18105 PR], commit
> {{{d2c5a30e5a8595d06c4a70ff0f66032fee0d3c8e}}}).
> Since this function is called by the {{{post_migrate}}} signal, it
> affects the {{{migrate}}} command.
> The function raises unexpected {{{LookupError}}} s on Windows systems.
>
> {{{
> Operations to perform:
>   Apply all migrations: admin, auth, contenttypes, dev, sessions
> Running migrations:
>   Applying dev.0001_initial... OK
> Traceback (most recent call last):
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\apps\registry.py", line 158, in get_app_config
> return self.app_configs[app_label]
>^^^
> KeyError: 'dev'
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>   File "C:\Users\csirm\PycharmProjects\django-dev\django_dev\manage.py",
> line 22, in 
> main()
>   File "C:\Users\csirm\PycharmProjects\django-dev\django_dev\manage.py",
> line 18, in main
> execute_from_command_line(sys.argv)
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\core\management\__init__.py", line 442, in
> execute_from_command_line
> utility.execute()
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\core\management\__init__.py", line 436, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\core\management\base.py", line 413, in run_from_argv
> self.execute(*args, **cmd_options)
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\core\management\base.py", line 459, in execute
> output = self.handle(*args, **options)
>  ^
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\core\management\base.py", line 107, in wrapper
> res = handle_func(*args, **kwargs)
>   
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\core\management\commands\migrate.py", line 384, in handle
> emit_post_migrate_signal(
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\core\management\sql.py", line 52, in
> emit_post_migrate_signal
> models.signals.post_migrate.send(
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\dispatch\dispatcher.py", line 189, in send
> response = receiver(signal=self, sender=sender, **named)
>^
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\contrib\auth\management\__init__.py", line 78, in
> create_permissions
> ctypes = ContentType.objects.db_manager(using).get_for_models(
>  ^
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\contrib\contenttypes\models.py", line 93, in
> get_for_models
> ct._meta.apps.get_model(ct.app_label, ct.model)._meta, []
> ^^^
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\apps\registry.py", line 208, in get_model
> app_config = self.get_app_config(app_label)
>  ^^
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\apps\registry.py", line 165, in get_app_config
> raise LookupError(message)
> LookupError: No installed app with label 'dev'.
> }}}

New description:

 [https://code.djangoproject.com/ticket/35408 #35408] introduced a bug in
 {{{contrib.auth}}}'s {{{create_permissions}}} function
 ([https://github.com/django/django/pull/18105 PR], commit
 {{{d2c5a30e5a8595d06c4a70ff0f66032fee0d3c8e}}}).
 Since this function is called by the {{{post_migrate}}} signal, it affects
 the {{{migrate}}} command.
 The function raises unexpected {{{Look

Re: [Django] #35464: Fieldsets defined for TabularInlines are ignored

2024-06-20 Thread Django

#35464: Fieldsets defined for TabularInlines are ignored
-+-
 Reporter:  Natalia Bidart   |Owner:  Maryam
 Type:   |  Yusuf
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Maryam Yusuf):

 * owner:  nobody => Maryam Yusuf
 * 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/0107019037b747bf-d04022d7-b2a2-4a27-a193-dd13e01c7d0f-00%40eu-central-1.amazonses.com.

Re: [Django] #35530: `django.contrib.auth.login` inconsistently guards `request.user`

2024-06-20 Thread Django

#35530: `django.contrib.auth.login` inconsistently guards `request.user`
-+-
 Reporter:  Jaap Roes|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.auth |  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 Jaap Roes):

 Just to be clear, these tests I provided are not supposed to pass. They're
 just examples of reasonable scenarios that break as soon as the `user`
 argument to `login` is `None`.

 Calling `login` with `None` just doesn't make sense in my opinion. The
 function signature also doesn't imply that the user is optional, or
 allowed to be `None` in the first place.
-- 
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/01070190377078a4-ab1f1bdd-348e-4685-911c-90553ba85176-00%40eu-central-1.amazonses.com.

Re: [Django] #35530: `django.contrib.auth.login` inconsistently guards `request.user`

2024-06-20 Thread Django

#35530: `django.contrib.auth.login` inconsistently guards `request.user`
-+-
 Reporter:  Jaap Roes|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.auth |  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 Jaap Roes):

 Thanks. The reason I filed this issue is because I tasked myself with
 describing how Django's authentication and login flow works. This bit
 stuck out as particularly confusing and basically unexplainable. I haven't
 been able to come up with a rational use case where passing in `None` for
 the `user` argument will make `login` behave in a way that I would expect.

 I removed the confusing bit:

 {{{
 if user is None:
 user = request.user
 }}}

 then ran the tests again.

 The only test that breaks is
 
[https://github.com/django/django/blob/20c2d625d3d5062e43918d1d7b6f623202491dd4/tests/async/test_async_auth.py#L36-L43
 async def test_alogin_without_user(self):], which is a test for the async
 wrapper of this function.

 Based on this test I have created another testcase that shows the issue
 when `request.user` is `AnonymousUser` (which is common when
 `AuthenticationMiddleware` is used).

 {{{
 async def test_alogin_without_user_anonymous_request(self):
 request = HttpRequest()
 request.user = AnonymousUser()
 request.session = await self.client.asession()
 await alogin(request, None)
 user = await aget_user(request)
 self.assertIsInstance(user, User)
 self.assertEqual(user.username, self.test_user.username)
 }}}

 This will fail with an `AttributeError: 'AnonymousUser' object has no
 attribute '_meta'`.

 Another way this function will fail is when `request.user` is absent (i.e.
 `AuthenticationMiddleware` is not in use):

 {{{
 async def test_alogin_without_user_or_request_user(self):
 request = HttpRequest()
 request.session = await self.client.asession()
 await alogin(request, None)
 user = await aget_user(request)
 self.assertIsInstance(user, User)
 self.assertEqual(user.username, self.test_user.username)
 }}}

 This will fail with an `AttributeError: 'HttpRequest' object has no
 attribute 'user'`.

 Setting `request.user = None` and passing in `user=None` will do the same
 thing as just removing the `if user is None` test and fail with
 `AttributeError: 'NoneType' object has no attribute '_meta'`.

 There seems no real reason for this behaviour to exists. The only thing
 touching this code in the Django code base is a recently added test for
 the async wrapper. The code branch only works in very specific
 circumstances, and does not fail gracefully if these circumstances are not
 met.

 Not sure if this is enough background to make you open this ticket again?
-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070190376a0373-0b8fee97-9a95-4efe-aefc-89d978d71544-00%40eu-central-1.amazonses.com.

Re: [Django] #35547: reset_queries cannot be imported from django.db

2024-06-20 Thread Django

#35547: reset_queries cannot be imported from django.db
-+-
 Reporter:  AjmalPonneth |Owner:
 Type:   |  AjmalPonneth
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 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
-+-
Comment (by AjmalPonneth):

 PR: https://github.com/django/django/pull/18292
-- 
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/01070190371cc0ab-4b4d48a7-9aa6-4803-a324-42d87f707da4-00%40eu-central-1.amazonses.com.

[Django] #35547: reset_queries cannot be imported from django.db

2024-06-20 Thread Django

#35547: reset_queries cannot be imported from django.db
-+-
   Reporter: |  Owner:  AjmalPonneth
  AjmalPonneth   |
   Type: | Status:  assigned
  Cleanup/optimization   |
  Component:  Database   |Version:  5.0
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 Currently, the reset_queries method cannot be imported from `django.db`.
-- 
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/0107019037101c11-c910a983-e067-4afb-ad50-e7fcb1220630-00%40eu-central-1.amazonses.com.

[Django] #35546: Modernize contributing pages to aling with current requirement of having an accepted ticket for non trivial changes

2024-06-20 Thread Django

#35546: Modernize contributing pages to aling with current requirement of 
having an
accepted ticket for non trivial changes
+
   Reporter:  Natalia Bidart|  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |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 |
+
 Following some feedback from https://github.com/django/django/pull/17389,
 there are some parts in these docs:

 https://docs.djangoproject.com/en/dev/internals/contributing/bugs-and-
 features/
 https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
 /submitting-patches/

 that could benefit from being more explicit about the need to have an
 accepted ticket when working on non trivial changes.

 Specifically, I think that this paragraph is misleading:

 "As with most open-source projects, code talks. If you are willing to
 write the code for the feature yourself or, even better, if you’ve already
 written it, it’s much more likely to be accepted. Fork Django on GitHub,
 create a feature branch, and show us your work!"

 And also the patch review checklist should explicitly mention that an
 accepted ticket is required to get reviews/discussion in a GH 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/0107019036e1d911-b948f28e-7d54-442b-93bb-aaabf2dbebb4-00%40eu-central-1.amazonses.com.

Re: [Django] #35545: Fix create_permissions LookupErrors

2024-06-20 Thread Django

#35545: Fix create_permissions LookupErrors
--+
 Reporter:  Csirmaz Bendegúz  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  5.1
 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 Natalia Bidart):

 * cc: Adam Johnson (added)
 * stage:  Unreviewed => Accepted

Comment:

 Thank you Csirmaz for this report!

 I can confirm I can reproduce in a simple Django project:
 {{{
 $  python -Wall manage.py migrate generator
 Operations to perform:
   Apply all migrations: generator
 Running migrations:
   Applying generator.0001_initial... OK
 Traceback (most recent call last):
   File "/home/nessita/fellowship/django/django/apps/registry.py", line
 158, in get_app_config
 return self.app_configs[app_label]
^^^
 KeyError: 'generator'

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File "/home/nessita/fellowship/checklist-generator/manage.py", line 22,
 in 
 main()
   File "/home/nessita/fellowship/checklist-generator/manage.py", line 18,
 in main
 execute_from_command_line(sys.argv)
   File
 "/home/nessita/fellowship/django/django/core/management/__init__.py", line
 442, in execute_from_command_line
 utility.execute()
   File
 "/home/nessita/fellowship/django/django/core/management/__init__.py", line
 436, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/nessita/fellowship/django/django/core/management/base.py",
 line 413, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/home/nessita/fellowship/django/django/core/management/base.py",
 line 459, in execute
 output = self.handle(*args, **options)
  ^
   File "/home/nessita/fellowship/django/django/core/management/base.py",
 line 107, in wrapper
 res = handle_func(*args, **kwargs)
   
   File
 "/home/nessita/fellowship/django/django/core/management/commands/migrate.py",
 line 384, in handle
 emit_post_migrate_signal(
   File "/home/nessita/fellowship/django/django/core/management/sql.py",
 line 52, in emit_post_migrate_signal
 models.signals.post_migrate.send(
   File "/home/nessita/fellowship/django/django/dispatch/dispatcher.py",
 line 189, in send
 response = receiver(signal=self, sender=sender, **named)
^
   File
 "/home/nessita/fellowship/django/django/contrib/auth/management/__init__.py",
 line 78, in create_permissions
 ctypes = ContentType.objects.db_manager(using).get_for_models(
  ^
   File
 "/home/nessita/fellowship/django/django/contrib/contenttypes/models.py",
 line 93, in get_for_models
 ct._meta.apps.get_model(ct.app_label, ct.model)._meta, []
 ^^^
   File "/home/nessita/fellowship/django/django/apps/registry.py", line
 208, in get_model
 app_config = self.get_app_config(app_label)
  ^^
   File "/home/nessita/fellowship/django/django/apps/registry.py", line
 165, in get_app_config
 raise LookupError(message)
 LookupError: No installed app with label 'generator'.
 }}}
-- 
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/0107019036ca80e2-1a9119be-a230-4531-9297-6faa56ccaf7f-00%40eu-central-1.amazonses.com.

Re: [Django] #22712: Consider not using built-in functions as parameters

2024-06-20 Thread Django

#22712: Consider not using built-in functions as parameters
-+-
 Reporter:  Richard Eames|Owner:  Andreu
 Type:   |  Vallbona
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  1.6
 Severity:  Normal   |   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 Natalia Bidart):

 * needs_better_patch:  0 => 1
 * needs_docs:  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/010701903696d201-d9529db6-a33d-4dd7-b321-834add438de2-00%40eu-central-1.amazonses.com.

Re: [Django] #35545: Fix create_permissions LookupErrors

2024-06-20 Thread Django

#35545: Fix create_permissions LookupErrors
--+--
 Reporter:  Csirmaz Bendegúz  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  5.1
 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
--+--
Description changed by Csirmaz Bendegúz:

Old description:

> [https://code.djangoproject.com/ticket/35408 #35408] introduced a bug in
> contrib.auth's create_permissions function
> ([https://github.com/django/django/pull/18105 PR], commit
> d2c5a30e5a8595d06c4a70ff0f66032fee0d3c8e ).
> Since this function is called by the post migrate signal, it affects the
> migrate command.
> The function raises unexpected LookupErrors on Windows systems.
>
> {{{
> Operations to perform:
>   Apply all migrations: admin, auth, contenttypes, dev, sessions
> Running migrations:
>   Applying dev.0001_initial... OK
> Traceback (most recent call last):
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\apps\registry.py", line 158, in get_app_config
> return self.app_configs[app_label]
>^^^
> KeyError: 'dev'
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>   File "C:\Users\csirm\PycharmProjects\django-dev\django_dev\manage.py",
> line 22, in 
> main()
>   File "C:\Users\csirm\PycharmProjects\django-dev\django_dev\manage.py",
> line 18, in main
> execute_from_command_line(sys.argv)
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\core\management\__init__.py", line 442, in
> execute_from_command_line
> utility.execute()
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\core\management\__init__.py", line 436, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\core\management\base.py", line 413, in run_from_argv
> self.execute(*args, **cmd_options)
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\core\management\base.py", line 459, in execute
> output = self.handle(*args, **options)
>  ^
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\core\management\base.py", line 107, in wrapper
> res = handle_func(*args, **kwargs)
>   
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\core\management\commands\migrate.py", line 384, in handle
> emit_post_migrate_signal(
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\core\management\sql.py", line 52, in
> emit_post_migrate_signal
> models.signals.post_migrate.send(
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\dispatch\dispatcher.py", line 189, in send
> response = receiver(signal=self, sender=sender, **named)
>^
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\contrib\auth\management\__init__.py", line 78, in
> create_permissions
> ctypes = ContentType.objects.db_manager(using).get_for_models(
>  ^
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\contrib\contenttypes\models.py", line 93, in
> get_for_models
> ct._meta.apps.get_model(ct.app_label, ct.model)._meta, []
> ^^^
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\apps\registry.py", line 208, in get_model
> app_config = self.get_app_config(app_label)
>  ^^
>   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
> packages\django\apps\registry.py", line 165, in get_app_config
> raise LookupError(message)
> LookupError: No installed app with label 'dev'.
> }}}

New description:

 [https://code.djangoproject.com/ticket/35408 #35408] introduced a bug in
 {{{contrib.auth}}}'s {{{create_permissions}}} function
 ([https://github.com/django/django/pull/18105 PR], commit
 {{{d2c5a30e5a8595d06c4a70ff0f66032fee0d3c8e}}}).
 Since this function is called by the {{{post_migrate}}} signal, it affects
 the {{{migrate}}} command.
 The function raises unexpected {{{LookupError}}} s on Windows system

[Django] #35545: Fix create_permissions LookupErrors

2024-06-20 Thread Django

#35545: Fix create_permissions LookupErrors
+
   Reporter:  Csirmaz Bendegúz  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  contrib.auth  |Version:  5.1
   Severity:  Release blocker   |   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 [https://code.djangoproject.com/ticket/35408 #35408] introduced a bug in
 contrib.auth's create_permissions function
 ([https://github.com/django/django/pull/18105 PR], commit
 d2c5a30e5a8595d06c4a70ff0f66032fee0d3c8e ).
 Since this function is called by the post migrate signal, it affects the
 migrate command.
 The function raises unexpected LookupErrors on Windows systems.

 {{{
 Operations to perform:
   Apply all migrations: admin, auth, contenttypes, dev, sessions
 Running migrations:
   Applying dev.0001_initial... OK
 Traceback (most recent call last):
   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
 packages\django\apps\registry.py", line 158, in get_app_config
 return self.app_configs[app_label]
^^^
 KeyError: 'dev'

 During handling of the above exception, another exception occurred:

 Traceback (most recent call last):
   File "C:\Users\csirm\PycharmProjects\django-dev\django_dev\manage.py",
 line 22, in 
 main()
   File "C:\Users\csirm\PycharmProjects\django-dev\django_dev\manage.py",
 line 18, in main
 execute_from_command_line(sys.argv)
   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
 packages\django\core\management\__init__.py", line 442, in
 execute_from_command_line
 utility.execute()
   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
 packages\django\core\management\__init__.py", line 436, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
 packages\django\core\management\base.py", line 413, in run_from_argv
 self.execute(*args, **cmd_options)
   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
 packages\django\core\management\base.py", line 459, in execute
 output = self.handle(*args, **options)
  ^
   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
 packages\django\core\management\base.py", line 107, in wrapper
 res = handle_func(*args, **kwargs)
   
   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
 packages\django\core\management\commands\migrate.py", line 384, in handle
 emit_post_migrate_signal(
   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
 packages\django\core\management\sql.py", line 52, in
 emit_post_migrate_signal
 models.signals.post_migrate.send(
   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
 packages\django\dispatch\dispatcher.py", line 189, in send
 response = receiver(signal=self, sender=sender, **named)
^
   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
 packages\django\contrib\auth\management\__init__.py", line 78, in
 create_permissions
 ctypes = ContentType.objects.db_manager(using).get_for_models(
  ^
   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
 packages\django\contrib\contenttypes\models.py", line 93, in
 get_for_models
 ct._meta.apps.get_model(ct.app_label, ct.model)._meta, []
 ^^^
   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
 packages\django\apps\registry.py", line 208, in get_model
 app_config = self.get_app_config(app_label)
  ^^
   File "C:\Users\csirm\PycharmProjects\django-dev\venv\Lib\site-
 packages\django\apps\registry.py", line 165, in get_app_config
 raise LookupError(message)
 LookupError: No installed app with label 'dev'.
 }}}
-- 
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/010701903672d937-e5a2acd4-da9c-4260-846f-296ff88f876a-00%40eu-central-1.amazonses.com.

Re: [Django] #35461: Tutorial instructions for adding django-debug-toolbar are misleading.

2024-06-20 Thread Django

#35461: Tutorial instructions for adding django-debug-toolbar are misleading.
-+-
 Reporter:  dawbert  |Owner:  Rosana
 Type:   |  Rufer
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  5.0
 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 Sarah Boyce):

 * 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/010701903653d604-9cf3e522-f9b3-4178-94ae-cbe49d3eb626-00%40eu-central-1.amazonses.com.

Re: [Django] #35544: Readonly Widget Template

2024-06-20 Thread Django

#35544: Readonly Widget Template
-+-
 Reporter:  Sven R. Kunze|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  widget readonly  | Triage Stage:
  admin  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Sven R. Kunze:

Old description:

> Hi everyone, recently I came across the following issue which already saw
> some attention on StackOverflow.
>
> All solutions I've seen so far circumvent a limitation of Django widgets:
> these are not really aware of a readonly situation. There are specialized
> readonly widgets for certain situations however there is no generic path
> for a Widget designer to specify how a readonly version of a widget would
> look like. Additionally there's is no easy way to override that behavior
> (see my last response on the SO issue) in admin.
>
> Admin, however, is just part of Django, so I would rather see a more
> general approach here. Therefore, I propose the following.
>
> Couldn't we define a ReadonlyAwareInput that allows the following:
>
> {{{
> class ReadonlyAwareInput(Input):
> template_name = "django/forms/widgets/input.html"
> readonly_template_name = "django/forms/widgets/readonly_input.html"
> # new
>
> def __init__(self, attrs=None, is_readonly=False):
> self.is_readonly= is_readonly
> if attrs is not None:
> attrs = attrs.copy()
> self.input_type = attrs.pop("type", self.input_type)
> super().__init__(attrs)
>
> def get_context(self, name, value, attrs):
> context = super().get_context(name, value, attrs)
> context["widget"]["type"] = self.input_type
> context["is_readonly"] = self.is_readonly
> return context
>

> class PreviewFileInput(ReadonlyAwareInput):
> template_name = "django/forms/widgets/preview_file.html"
> readonly_template_name =
> "django/forms/widgets/readonly_preview_file.html"  # override new
> readonly_template_name
>
> def get_context(self, name, value, attrs):
>  # as usual
> }}}
>
> I am not sure if Admin's display_for_field could be replaced completely
> by such a system. I my gut feeling is that it would allow customizing a
> lot more.
>
> What do you think about that solution?
>

> Also see
> - https://forum.djangoproject.com/t/feature-request-discussion-custom-
> rendering-for-readonly-fields-in-admin/32009
> - https://code.djangoproject.com/ticket/30577
> - https://stackoverflow.com/questions/14832739/django-admin-how-to-
> display-widget-on-readonly-field

New description:

 Hi everyone, recently I came across the following issue which already saw
 some attention on StackOverflow.

 All solutions I've seen so far circumvent a limitation of Django widgets:
 these are not really aware of a readonly situation. There are specialized
 readonly widgets for certain situations however there is no generic path
 for a Widget designer to specify how a readonly version of a widget would
 look like. Additionally there's is no easy way to override that behavior
 (see my last response on the SO issue) in admin.

 Admin, however, is just part of Django, so I would rather see a more
 general approach here. Therefore, I propose the following.

 Couldn't we define a ReadonlyAwareInput that allows the following:

 {{{
 class ReadonlyAwareInput(Input):
 template_name = "django/forms/widgets/input.html"
 readonly_template_name = "django/forms/widgets/readonly_input.html"  #
 new

 def __init__(self, attrs=None, is_readonly=False):
 self.is_readonly= is_readonly
 if attrs is not None:
 attrs = attrs.copy()
 self.input_type = attrs.pop("type", self.input_type)
 super().__init__(attrs)

 def get_context(self, name, value, attrs):
 context = super().get_context(name, value, attrs)
 context["widget"]["type"] = self.input_type
 context["is_readonly"] = self.is_readonly  # new for usage in
 template as well
 return context

 def render(self, name, value, attrs=None, renderer=None):
 """Render the widget as an HTML string."""
 context = self.get_context(name, value, attrs)
 if self.is_readonly:
 return self._render(self.readonly_template_name, context,
 renderer)
 return self._render(self.template_name, context, renderer)


 class PreviewFileInput(ReadonlyAwareInput):
 template_name = "django/forms/widgets/preview

[Django] #35544: Readonly Widget Template

2024-06-20 Thread Django

#35544: Readonly Widget Template
-+-
   Reporter:  Sven R.|  Owner:  nobody
  Kunze  |
   Type:  New| Status:  new
  feature|
  Component:  Forms  |Version:  dev
   Severity:  Normal |   Keywords:  widget readonly
   Triage Stage: |  admin
  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Hi everyone, recently I came across the following issue which already saw
 some attention on StackOverflow.

 All solutions I've seen so far circumvent a limitation of Django widgets:
 these are not really aware of a readonly situation. There are specialized
 readonly widgets for certain situations however there is no generic path
 for a Widget designer to specify how a readonly version of a widget would
 look like. Additionally there's is no easy way to override that behavior
 (see my last response on the SO issue) in admin.

 Admin, however, is just part of Django, so I would rather see a more
 general approach here. Therefore, I propose the following.

 Couldn't we define a ReadonlyAwareInput that allows the following:

 {{{
 class ReadonlyAwareInput(Input):
 template_name = "django/forms/widgets/input.html"
 readonly_template_name = "django/forms/widgets/readonly_input.html"  #
 new

 def __init__(self, attrs=None, is_readonly=False):
 self.is_readonly= is_readonly
 if attrs is not None:
 attrs = attrs.copy()
 self.input_type = attrs.pop("type", self.input_type)
 super().__init__(attrs)

 def get_context(self, name, value, attrs):
 context = super().get_context(name, value, attrs)
 context["widget"]["type"] = self.input_type
 context["is_readonly"] = self.is_readonly
 return context


 class PreviewFileInput(ReadonlyAwareInput):
 template_name = "django/forms/widgets/preview_file.html"
 readonly_template_name =
 "django/forms/widgets/readonly_preview_file.html"  # override new
 readonly_template_name

 def get_context(self, name, value, attrs):
  # as usual
 }}}

 I am not sure if Admin's display_for_field could be replaced completely by
 such a system. I my gut feeling is that it would allow customizing a lot
 more.

 What do you think about that solution?


 Also see
 - https://forum.djangoproject.com/t/feature-request-discussion-custom-
 rendering-for-readonly-fields-in-admin/32009
 - https://code.djangoproject.com/ticket/30577
 - https://stackoverflow.com/questions/14832739/django-admin-how-to-
 display-widget-on-readonly-field
-- 
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/01070190365010c5-be416829-ac53-4885-8864-8c8ba0330e6e-00%40eu-central-1.amazonses.com.

Re: [Django] #35540: Admin login form padding issue

2024-06-20 Thread Django

#35540: Admin login form padding issue
---+-
 Reporter:  Sarah Boyce|Owner:  Anthony Kugel
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  5.1
 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:  1
---+-
Changes (by Natalia Bidart):

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

Comment:

 Another great catch, thank you Sarah! Confirmed that 5.0 is not 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/01070190364380b2-0b0f01ac-22a9-4b0c-8a8d-73d4e6df6142-00%40eu-central-1.amazonses.com.

Re: [Django] #35539: SearchVector GinIndex raises IMMUTABLE error (was: contrib/postgres/search.py COALESCE breaks GIN Index creation on PostgreSQL 15)

2024-06-20 Thread Django

#35539: SearchVector GinIndex raises IMMUTABLE error
--+
 Reporter:  Alastair D'Silva  |Owner:  (none)
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  5.0
 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 Sarah Boyce):

 * cc: Mariusz Felisiak, Simon Charette (added)
 * stage:  Unreviewed => Accepted
 * summary:
 contrib/postgres/search.py COALESCE breaks GIN Index creation on
 PostgreSQL 15
 => SearchVector GinIndex raises IMMUTABLE error

Comment:

 Thank you for the report, was able to replicate the error 👍
 I believe this is a valid bug, I've never used these before myself but
 looks like it's being used
 [https://docs.djangoproject.com/en/5.0/ref/contrib/postgres/search/#performance
 as documented]

 Here is my "rough" test if it gives anyone a starting point

 {{{#!diff
 --- a/tests/postgres_tests/test_indexes.py
 +++ b/tests/postgres_tests/test_indexes.py
 @@ -379,6 +379,19 @@ class SchemaTests(PostgreSQLTestCase):
  editor.remove_index(Scene, index)
  self.assertNotIn(index_name,
 self.get_constraints(Scene._meta.db_table))

 +def test_search_vector_gin_index(self):
 +index_name = "search_vector_gin"
 +index = GinIndex(SearchVector("field"), name=index_name)
 +with connection.schema_editor() as editor:
 +editor.add_index(TextFieldModel, index)
 +table = TextFieldModel._meta.db_table
 +constraints = self.get_constraints(table)
 +self.assertIn(index_name, constraints)
 +self.assertIn(constraints[index_name]["type"], GinIndex.suffix)
 +with connection.schema_editor() as editor:
 +editor.remove_index(TextFieldModel, index)
 +self.assertNotIn(index_name, self.get_constraints(table))
 +
  def test_cast_search_vector_gin_index(self):
 }}}
-- 
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/010701903634c0f2-ccaaedd2-6ad1-42bb-bc0f-b172cdc1eb5e-00%40eu-central-1.amazonses.com.

Re: [Django] #35541: Admin changelist total row css issue

2024-06-20 Thread Django

#35541: Admin changelist total row css issue
---+
 Reporter:  Sarah Boyce|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  5.1
 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 Natalia Bidart):

 * stage:  Unreviewed => Accepted

Comment:

 Great catch Sarah, thank you! As far as I can see this is an issue in 5.0
 and 4.2 as well, so not a release blocker for 5.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/010701903619f869-0a9a02a0-73ce-42a1-b9df-f8a056ff7192-00%40eu-central-1.amazonses.com.

Re: [Django] #35543: Contribution: new management commands for contrib.auth (grantpermissions, revokepermissions)

2024-06-20 Thread Django

#35543: Contribution: new management commands for contrib.auth 
(grantpermissions,
revokepermissions)
--+--
 Reporter:  Florian Schieder  |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  contrib.auth  |  Version:  5.0
 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
--+--
Changes (by Sarah Boyce):

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

Comment:

 Hi Florian, thank you for raising this ticket!

 For new feature requests, the recommended path forward is to first propose
 and discuss the idea on the [https://forum.djangoproject.com/c/internals/5
 Django Forum]. You'll reach a wider audience and likely get extra feedback
 👍

 I'll close the ticket for now, but if there is a community agreement for
 this, you are welcome to come back to the ticket and point to the forum
 topic, so we can then re-open it. For more details, please see
 [https://docs.djangoproject.com/en/stable/internals/contributing/bugs-and-
 features/#requesting-features the documented guidelines for requesting
 features].
-- 
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/010701903618cd9d-fdb4d25c-c0cb-4172-b42a-e43e1cc69e2a-00%40eu-central-1.amazonses.com.

Re: [Django] #35461: Tutorial instructions for adding django-debug-toolbar are misleading.

2024-06-20 Thread Django

#35461: Tutorial instructions for adding django-debug-toolbar are misleading.
-+-
 Reporter:  dawbert  |Owner:  Rosana
 Type:   |  Rufer
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  5.0
 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/01070190360cb9ad-d9c6ddf0-4ba5-4cf3-8159-58faf0a11763-00%40eu-central-1.amazonses.com.

[Django] #35543: Contribution: new management commands for contrib.auth (grantpermissions, revokepermissions)

2024-06-20 Thread Django

#35543: Contribution: new management commands for contrib.auth
(grantpermissions,
revokepermissions)
+
Reporter: Florian Schieder | Owner: nobody
Type: New feature | Status: new
Component: contrib.auth |Version: 5.0
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 |
+
Dear Django team,

I developed two management commands `grantpermissions` and
`revokepermissions` for our CMS based on Django CMS.
That was very useful to simply grant plugin permissions for many plugins
across different CMS instances.

Under the hood, plugin permissions are entirely based on
`django.contrib.auth.models.Permission`,
`django.contrib.auth.models.Group` and
`django.contrib.contenttypes.models.ContentType`.
Therefore the commands I implemented are fully independent from our own
CMS solution as well as it does not depend on Django CMS.

The only dependencies are the `contenttypes` and `auth` contrib
applications. Thus I decided to contribute those commands and the related
unit tests to the Django project.

I create this ticket to collect feedback if this sounds like a rational
contribution and if you are interested in it by filing a PR against the
`django` GitHub repository.

yours sincerely,
Florian Schieder from Germany
--
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/0107019036014210-e86c4121-1553-4aeb-87d9-52898baf4872-00%40eu-central-1.amazonses.com.

[Django] #35542: BoundField's label and help_text and renderer should be properties not class members

2024-06-20 Thread Django

#35542: BoundField's label and help_text and renderer should be properties not
class members
-+-
   Reporter: |  Owner:  Christophe Henry
  Christophe Henry   |
   Type: | Status:  assigned
  Uncategorized  |
  Component:  Forms  |Version:  5.0
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 `BoundField` exposes
 [https://github.com/django/django/blob/main/django/forms/boundfield.py#L23
 label]
 [https://github.com/django/django/blob/main/django/forms/boundfield.py#L27
 help_text] and
 [https://github.com/django/django/blob/main/django/forms/boundfield.py#L28
 renderer], all of them are copies of underlying members of `Field` and
 `Form`.

 This is a bit misleanding since you can modify `Field`s member in `Form`'s
 `__init__` [https://docs.djangoproject.com/en/5.0/ref/forms/fields
 /#fields-which-handle-relationships like documented here] but any
 modification of `help_text`, `label` or `renderer` after
 `super().__init__` won't be reflected on the bound which can leand to
 incomprehensible behavior  in templates
-- 
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/0107019035a87941-7616b385-fbbd-4d31-9f8e-fbc0e9247147-00%40eu-central-1.amazonses.com.

Re: [Django] #35540: Admin login form padding issue

2024-06-20 Thread Django

#35540: Admin login form padding issue
---+-
 Reporter:  Sarah Boyce|Owner:  Anthony Kugel
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  5.1
 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 Anthony Kugel):

 * owner:  nobody => Anthony Kugel
 * 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/010701903574cab8-bd570aa8-4460-4fc4-bb74-5d22d85afc8c-00%40eu-central-1.amazonses.com.

Re: [Django] #35541: Admin changelist total row css issue

2024-06-20 Thread Django

#35541: Admin changelist total row css issue
---+--
 Reporter:  Sarah Boyce|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  5.1
 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
---+--
Description changed by Sarah Boyce:

Old description:

> The border of the total row extends longer than the table
>
> [[Image(image-20240620-132817.png)]]
>
> This would fix it for me (needs further testing)
> {{{#!diff
> --- a/django/contrib/admin/static/admin/css/base.css
> +++ b/django/contrib/admin/static/admin/css/base.css
> @@ -1119,7 +1119,6 @@ a.deletelink:focus, a.deletelink:hover {
>  line-height: 22px;
>  margin: 0;
>  border-top: 1px solid var(--hairline-color);
> -width: 100%;
>  }
> }}}
>
> [[Image(image-20240620-132917.png)]]
>
> Please update `docs/intro/_images/admin04t.png` with the lastest css

New description:

 The border of the total row extends longer than the table

 [[Image(image-20240620-132817.png)]]

 This would fix it for me (needs further testing)
 {{{#!diff
 --- a/django/contrib/admin/static/admin/css/base.css
 +++ b/django/contrib/admin/static/admin/css/base.css
 @@ -1119,7 +1119,6 @@ a.deletelink:focus, a.deletelink:hover {
  line-height: 22px;
  margin: 0;
  border-top: 1px solid var(--hairline-color);
 -width: 100%;
  }
 }}}

 [[Image(image-20240620-132917.png)]]

 I also believe the following related images should be updated with the
 lastest css:
 - `docs/intro/_images/admin04t.png`
 - `docs/intro/_images/admin06t.png`
 - `docs/intro/_images/admin12t.png`

--
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35541#comment:3>
Django <https://code.djangoproject.com/>
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/0107019035709e45-e6c17089-b497-45c1-83d9-e91ef27c37b5-00%40eu-central-1.amazonses.com.

Re: [Django] #35541: Admin changelist total row css issue

2024-06-20 Thread Django

#35541: Admin changelist total row css issue
---+--
 Reporter:  Sarah Boyce|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  5.1
 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 Sarah Boyce):

 * easy:  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/010701903569bbab-ec304cef-a3c5-4033-a8cb-9a13a0292653-00%40eu-central-1.amazonses.com.

Re: [Django] #35541: Admin changelist total row css issue

2024-06-20 Thread Django

#35541: Admin changelist total row css issue
---+--
 Reporter:  Sarah Boyce|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  5.1
 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
---+--
Description changed by Sarah Boyce:

Old description:

> The border of the total row extends longer than the table
>
> This would fix it for me (needs further testing)
> {{{#!diff
> --- a/django/contrib/admin/static/admin/css/base.css
> +++ b/django/contrib/admin/static/admin/css/base.css
> @@ -1119,7 +1119,6 @@ a.deletelink:focus, a.deletelink:hover {
>  line-height: 22px;
>  margin: 0;
>  border-top: 1px solid var(--hairline-color);
> -width: 100%;
>  }
> }}}
>
> Please update `docs/intro/_images/admin04t.png` with the lastest css

New description:

 The border of the total row extends longer than the table

 [[Image(image-20240620-132817.png)]]

 This would fix it for me (needs further testing)
 {{{#!diff
 --- a/django/contrib/admin/static/admin/css/base.css
 +++ b/django/contrib/admin/static/admin/css/base.css
 @@ -1119,7 +1119,6 @@ a.deletelink:focus, a.deletelink:hover {
  line-height: 22px;
  margin: 0;
  border-top: 1px solid var(--hairline-color);
 -width: 100%;
  }
 }}}

 [[Image(image-20240620-132917.png)]]

 Please update `docs/intro/_images/admin04t.png` with the lastest css

--
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35541#comment:1>
Django <https://code.djangoproject.com/>
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/01070190356989eb-a58d396c-314e-4639-9f30-1c0e4caf2b93-00%40eu-central-1.amazonses.com.

Re: [Django] #35541: Admin changelist total row css issue

2024-06-20 Thread Django

#35541: Admin changelist total row css issue
---+--
 Reporter:  Sarah Boyce|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  5.1
 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 Sarah Boyce):

 * Attachment "image-20240620-132917.png" added.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/35541>
Django <https://code.djangoproject.com/>
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/0107019035687fb9-0de0c7e6-5ef0-4973-adb0-21648c245846-00%40eu-central-1.amazonses.com.

Re: [Django] #35541: Admin changelist total row css issue

2024-06-20 Thread Django

#35541: Admin changelist total row css issue
---+--
 Reporter:  Sarah Boyce|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  5.1
 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 Sarah Boyce):

 * Attachment "image-20240620-132817.png" added.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/35541>
Django <https://code.djangoproject.com/>
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/010701903567944d-18f39205-c487-47fa-9fa0-12141996f7c3-00%40eu-central-1.amazonses.com.

[Django] #35541: Admin changelist total row css issue

2024-06-20 Thread Django

#35541: Admin changelist total row css issue
-+
   Reporter:  Sarah Boyce|  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.admin  |Version:  5.1
   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  |
-+
 The border of the total row extends longer than the table

 This would fix it for me (needs further testing)
 {{{#!diff
 --- a/django/contrib/admin/static/admin/css/base.css
 +++ b/django/contrib/admin/static/admin/css/base.css
 @@ -1119,7 +1119,6 @@ a.deletelink:focus, a.deletelink:hover {
  line-height: 22px;
  margin: 0;
  border-top: 1px solid var(--hairline-color);
 -width: 100%;
  }
 }}}

 Please update `docs/intro/_images/admin04t.png` with the lastest css
-- 
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/0107019035672534-138295a5-0767-480f-86cb-3d693cb7be8f-00%40eu-central-1.amazonses.com.

Re: [Django] #35540: Admin login form padding issue

2024-06-20 Thread Django

#35540: Admin login form padding issue
---+--
 Reporter:  Sarah Boyce|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  5.1
 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
---+--
Description changed by Sarah Boyce:

Old description:

> If you look at the tutorial with an older screenshot of the Django admin,
> we're expecting some padding below the login button:
> https://docs.djangoproject.com/en/5.0/intro/tutorial02/#start-the-
> development-server
>

> Suggested update:
> {{{#!diff
> diff --git a/django/contrib/admin/static/admin/css/login.css
> b/django/contrib/admin/static/admin/css/login.css
> index 389772f5bc..805a34b5bd 100644
> --- a/django/contrib/admin/static/admin/css/login.css
> +++ b/django/contrib/admin/static/admin/css/login.css
> @@ -21,7 +21,7 @@
>  }
>
>  .login #content {
> -padding: 20px 20px 0;
> +padding: 20px;
>  }
>
>  .login #container {
> }}}
>

> Whoever picks this up should also update the image
> `docs/intro/_images/admin01.png` so that it has the latest styles 👍

New description:

 If you look at the tutorial with an older screenshot of the Django admin,
 we're expecting some padding below the login button:
 https://docs.djangoproject.com/en/5.0/intro/tutorial02/#start-the-
 development-server

 Current

 [[Image(image-20240620-130503.png)]]


 Suggested update:
 {{{#!diff
 diff --git a/django/contrib/admin/static/admin/css/login.css
 b/django/contrib/admin/static/admin/css/login.css
 index 389772f5bc..805a34b5bd 100644
 --- a/django/contrib/admin/static/admin/css/login.css
 +++ b/django/contrib/admin/static/admin/css/login.css
 @@ -21,7 +21,7 @@
  }

  .login #content {
 -padding: 20px 20px 0;
 +padding: 20px;
  }

  .login #container {
 }}}

 After

 [[Image(image-20240620-130526.png)]]

 Whoever picks this up should also update the image
 `docs/intro/_images/admin01.png` so that it has the latest styles 👍

--
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35540#comment:1>
Django <https://code.djangoproject.com/>
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/0107019035545588-3c2eb373-c9c5-45b1-993f-99c933c718d9-00%40eu-central-1.amazonses.com.

Re: [Django] #35540: Admin login form padding issue

2024-06-20 Thread Django

#35540: Admin login form padding issue
---+--
 Reporter:  Sarah Boyce|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  5.1
 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 Sarah Boyce):

 * Attachment "image-20240620-130526.png" added.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/35540>
Django <https://code.djangoproject.com/>
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/010701903552a74d-38afc17d-276d-4c6a-8578-6e16701ca949-00%40eu-central-1.amazonses.com.

Re: [Django] #35540: Admin login form padding issue

2024-06-20 Thread Django

#35540: Admin login form padding issue
---+--
 Reporter:  Sarah Boyce|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  5.1
 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 Sarah Boyce):

 * Attachment "image-20240620-130503.png" added.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/35540>
Django <https://code.djangoproject.com/>
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/0107019035524f8b-22e4a4f1-db74-490e-baec-7af1c2b5a474-00%40eu-central-1.amazonses.com.

[Django] #35540: Admin login form padding issue

2024-06-20 Thread Django

#35540: Admin login form padding issue
-+
   Reporter:  Sarah Boyce|  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.admin  |Version:  5.1
   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  |
-+
 If you look at the tutorial with an older screenshot of the Django admin,
 we're expecting some padding below the login button:
 https://docs.djangoproject.com/en/5.0/intro/tutorial02/#start-the-
 development-server


 Suggested update:
 {{{#!diff
 diff --git a/django/contrib/admin/static/admin/css/login.css
 b/django/contrib/admin/static/admin/css/login.css
 index 389772f5bc..805a34b5bd 100644
 --- a/django/contrib/admin/static/admin/css/login.css
 +++ b/django/contrib/admin/static/admin/css/login.css
 @@ -21,7 +21,7 @@
  }

  .login #content {
 -padding: 20px 20px 0;
 +padding: 20px;
  }

  .login #container {
 }}}


 Whoever picks this up should also update the image
 `docs/intro/_images/admin01.png` so that it has the latest styles 👍
-- 
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/01070190355146c0-5b0677c7-d7f8-48eb-99b8-458421b4c52c-00%40eu-central-1.amazonses.com.

Re: [Django] #35074: Altering spatial_index does not actually create/drop the index

2024-06-20 Thread Django

#35074: Altering spatial_index does not actually create/drop the index
--+
 Reporter:  Mário Falcão  |Owner:  Mariusz Felisiak
 Type:  Bug   |   Status:  assigned
Component:  GIS   |  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:  0
--+
Comment (by Sarah Boyce <42296566+sarahboyce@…>):

 In [changeset:"adb72fa85423eba238d472a8abfbb65bbc2132d5" adb72fa8]:
 {{{#!CommitTicketReference repository=""
 revision="adb72fa85423eba238d472a8abfbb65bbc2132d5"
 [5.1.x] Refs #35074 -- Avoided failed attempts to remove spatial indexes
 on nullable fields on MySQL.

 MySQL doesn't support spatial indexes on NULL columns, so there is no
 point in removing them.

 Backport of 20c2d625d3d5062e43918d1d7b6f623202491dd4 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/01070190350b2608-b257d3a2-5a43-409d-b0b4-acf5e58f2673-00%40eu-central-1.amazonses.com.

Re: [Django] #35074: Altering spatial_index does not actually create/drop the index

2024-06-20 Thread Django

#35074: Altering spatial_index does not actually create/drop the index
--+
 Reporter:  Mário Falcão  |Owner:  Mariusz Felisiak
 Type:  Bug   |   Status:  assigned
Component:  GIS   |  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:  0
--+
Comment (by Sarah Boyce <42296566+sarahboyce@…>):

 In [changeset:"20c2d625d3d5062e43918d1d7b6f623202491dd4" 20c2d62]:
 {{{#!CommitTicketReference repository=""
 revision="20c2d625d3d5062e43918d1d7b6f623202491dd4"
 Refs #35074 -- Avoided failed attempts to remove spatial indexes on
 nullable fields on MySQL.

 MySQL doesn't support spatial indexes on NULL columns, so there is no
 point in removing 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/010701903508d92e-ab4903f9-46a4-4fc4-b53e-56fed2194297-00%40eu-central-1.amazonses.com.

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

2024-06-20 Thread Django

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

 * needs_better_patch:  1 => 0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107019034d8fca4-6c65159b-3a25-42e5-93de-50db8475c4bf-00%40eu-central-1.amazonses.com.

Re: [Django] #35537: Use a namedtuple for email attachments and alternatives

2024-06-20 Thread Django

#35537: Use a namedtuple for email attachments and alternatives
-+-
 Reporter:  Sarah Boyce  |Owner:  Jake
 Type:   |  Howard
  Cleanup/optimization   |   Status:  closed
Component:  Core (Mail)  |  Version:  dev
 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
-+-
Changes (by Sarah Boyce <42296566+sarahboyce@…>):

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

Comment:

 In [changeset:"aba0e541caaa086f183197eaaca0ac20a730bbe4" aba0e54]:
 {{{#!CommitTicketReference repository=""
 revision="aba0e541caaa086f183197eaaca0ac20a730bbe4"
 Fixed #35537 -- Changed EmailMessage.attachments and
 EmailMultiAlternatives.alternatives to use namedtuples.

 This makes it more descriptive to pull out the named fields.
 }}}
-- 
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/010701903499f801-1165b780-469c-43e9-bf86-9d7920aec1ce-00%40eu-central-1.amazonses.com.

Re: [Django] #35404: Admin fieldset multiple flexbox regressions

2024-06-20 Thread Django

#35404: Admin fieldset multiple flexbox regressions
-+-
 Reporter:  minusf   |Owner:  Vaarun
 |  Sinha
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:  css admin fieldset   | Triage Stage:  Accepted
  accessibility  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Comment (by Sarah Boyce <42296566+sarahboyce@…>):

 In [changeset:"ba81b3f0a35c7753419b4adcf0daca64466c930c" ba81b3f0]:
 {{{#!CommitTicketReference repository=""
 revision="ba81b3f0a35c7753419b4adcf0daca64466c930c"
 [5.1.x] Refs #35404 -- Fixed padding of admin fieldset checkbox label.

 Backport of 9691a00d5839e6137a2716526277013af9ee97ff 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/0107019034982080-e27e1ff2-4ac2-45d3-9181-e071bf9e99a1-00%40eu-central-1.amazonses.com.

Re: [Django] #35404: Admin fieldset multiple flexbox regressions

2024-06-20 Thread Django

#35404: Admin fieldset multiple flexbox regressions
-+-
 Reporter:  minusf   |Owner:  Vaarun
 |  Sinha
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:  css admin fieldset   | Triage Stage:  Accepted
  accessibility  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Comment (by Sarah Boyce <42296566+sarahboyce@…>):

 In [changeset:"9691a00d5839e6137a2716526277013af9ee97ff" 9691a00d]:
 {{{#!CommitTicketReference repository=""
 revision="9691a00d5839e6137a2716526277013af9ee97ff"
 Refs #35404 -- Fixed padding of admin fieldset checkbox label.
 }}}
-- 
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/0107019034960a4b-8cf64e17-48c5-41ba-ac30-de59b1810205-00%40eu-central-1.amazonses.com.

Re: [Django] #35441: Context autoescape parameter is not documented

2024-06-20 Thread Django

#35441: Context autoescape parameter is not documented
-+-
 Reporter:  Roman Donchenko  |Owner:  John
 Type:   |  Higgins
  Cleanup/optimization   |   Status:  closed
Component:  Template system  |  Version:  5.0
 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 Sarah Boyce <42296566+sarahboyce@…>):

 In [changeset:"874fea63b477851d5902200ab3f7ed139c1c9cd2" 874fea6]:
 {{{#!CommitTicketReference repository=""
 revision="874fea63b477851d5902200ab3f7ed139c1c9cd2"
 [5.1.x] Fixed #35441 -- Documented Context and RequestContext keyword
 arguments.

 Backport of 60acad933d66e116c89150d3eb9040f62ca871a1 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/010701903494ea06-f9f0f27a-664e-4c49-bcfa-9c3da313ce06-00%40eu-central-1.amazonses.com.

Re: [Django] #35441: Context autoescape parameter is not documented

2024-06-20 Thread Django

#35441: Context autoescape parameter is not documented
-+-
 Reporter:  Roman Donchenko  |Owner:  John
 Type:   |  Higgins
  Cleanup/optimization   |   Status:  closed
Component:  Template system  |  Version:  5.0
 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
-+-
Changes (by Sarah Boyce <42296566+sarahboyce@…>):

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

Comment:

 In [changeset:"60acad933d66e116c89150d3eb9040f62ca871a1" 60acad93]:
 {{{#!CommitTicketReference repository=""
 revision="60acad933d66e116c89150d3eb9040f62ca871a1"
 Fixed #35441 -- Documented Context and RequestContext keyword arguments.
 }}}
-- 
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/010701903491fbf6-167a3e14-0ccd-4492-95de-d10a058bb679-00%40eu-central-1.amazonses.com.

44 matches

Mail list logo