Re: [Django] #35570: groups not shown in iOS

2024-07-01 Thread Django
#35570: groups not shown in iOS --+-- Reporter: Peter Doll|Owner: nobody Type: Bug | Status: closed Component: contrib.auth | Version: 4.0

Re: [Django] #23790: Possible bad interaction between migration dependencies and relabeling apps

2024-07-01 Thread Django
#23790: Possible bad interaction between migration dependencies and relabeling apps -+- Reporter: Aymeric Augustin |Owner: Andy | Miller Type: Bug

Re: [Django] #23790: Possible bad interaction between migration dependencies and relabeling apps

2024-07-01 Thread Django
#23790: Possible bad interaction between migration dependencies and relabeling apps -+- Reporter: Aymeric Augustin |Owner: Andy | Miller Type: Bug

Re: [Django] #23790: Possible bad interaction between migration dependencies and relabeling apps

2024-07-01 Thread Django
#23790: Possible bad interaction between migration dependencies and relabeling apps -+- Reporter: Aymeric Augustin |Owner: Andy | Miller Type: Bug

Re: [Django] #35571: TypeError in assertTemplateUsed when using pathlib.Path as template_name

2024-07-01 Thread Django
#35571: TypeError in assertTemplateUsed when using pathlib.Path as template_name +-- Reporter: Erik Z. |Owner: nobody Type: Bug | Status: close

Re: [Django] #35566: Support get_FOO_display() on GeneratedField

2024-07-01 Thread Django
#35566: Support get_FOO_display() on GeneratedField -+- Reporter: Ronie Martinez |Owner: Sarah | Boyce Type: New feature |

Re: [Django] #23790: Possible bad interaction between migration dependencies and relabeling apps

2024-07-01 Thread Django
#23790: Possible bad interaction between migration dependencies and relabeling apps -+- Reporter: Aymeric Augustin |Owner: Andy | Miller Type: Bug

[Django] #35571: TypeError in assertTemplateUsed when using pathlib.Path as template_name

2024-07-01 Thread Django
#35571: TypeError in assertTemplateUsed when using pathlib.Path as template_name ---+--- Reporter: Erik Z. | Owner: nobody Type: Bug | Status: new

Re: [Django] #35450: Missing documentation: deploying Django in production behind a proxy.

2024-07-01 Thread Django
#35450: Missing documentation: deploying Django in production behind a proxy. -+- Reporter: Klaas van Schelven |Owner: Wassef Type: | Ben Ahmed Cleanup/optimization

Re: [Django] #35470: Separate i18n and l10n globalization settings into two sublists.

2024-07-01 Thread Django
#35470: Separate i18n and l10n globalization settings into two sublists. -+- Reporter: Lufafa Joshua|Owner: Lufafa Type: | Joshua Cleanup/optimization

Re: [Django] #35470: Separate i18n and l10n globalization settings into two sublists.

2024-07-01 Thread Django
#35470: Separate i18n and l10n globalization settings into two sublists. -+- Reporter: Lufafa Joshua|Owner: Lufafa Type: | Joshua Cleanup/optimization

Re: [Django] #35569: Misleading ValidationError wording from `limit_choices_to` violation

2024-07-01 Thread Django
#35569: Misleading ValidationError wording from `limit_choices_to` violation -+- Reporter: Jacob Walls |Owner: Jacob Type: | Walls Cleanup/optimization

[Django] #35570: groups not shown in iOS

2024-07-01 Thread Django
#35570: groups not shown in iOS ---+- Reporter: pitweazle| Owner: (none) Type: Uncategorized| Status: new Component: Error reporting |Versio

Re: [Django] #35566: Support get_FOO_display() on GeneratedField

2024-07-01 Thread Django
#35566: Support get_FOO_display() on GeneratedField -+- Reporter: Ronie Martinez |Owner: Sarah | Boyce Type: New feature |

Re: [Django] #35569: Misleading ValidationError wording from `limit_choices_to` violation (was: Misleading ValidationError from `limit_choices_to` violation)

2024-07-01 Thread Django
#35569: Misleading ValidationError wording from `limit_choices_to` violation -+- Reporter: Jacob Walls |Owner: Jacob Type: | Walls Cleanup/optimization

[Django] #35569: Misleading ValidationError from `limit_choices_to` violation

2024-07-01 Thread Django
#35569: Misleading ValidationError from `limit_choices_to` violation -+- Reporter: Jacob | Owner: Jacob Walls Walls | Type: |

Re: [Django] #35566: Support get_FOO_display() on GeneratedField

2024-07-01 Thread Django
#35566: Support get_FOO_display() on GeneratedField -+- Reporter: Ronie Martinez |Owner: nobody Type: New feature | Status: new Component: Database lay

Re: [Django] #35450: Missing documentation: deploying Django in production behind a proxy.

2024-07-01 Thread Django
#35450: Missing documentation: deploying Django in production behind a proxy. -+- Reporter: Klaas van Schelven |Owner: Wassef Type: | Ben Ahmed Cleanup/optimization

Re: [Django] #35450: Missing documentation: deploying Django in production behind a proxy.

2024-07-01 Thread Django
#35450: Missing documentation: deploying Django in production behind a proxy. -+- Reporter: Klaas van Schelven |Owner: Wassef Type: | Ben Ahmed Cleanup/optimization

Re: [Django] #35451: Documentation: Gunicorn deployment should probably mention the usage of a proxy

2024-07-01 Thread Django
#35451: Documentation: Gunicorn deployment should probably mention the usage of a proxy -+- Reporter: Klaas van Schelven |Owner: Wassef Type: | Ben Ahmed Cleanup/o

Re: [Django] #35566: Support get_FOO_display() on GeneratedField

2024-07-01 Thread Django
#35566: Support get_FOO_display() on GeneratedField -+- Reporter: Ronie Martinez |Owner: nobody Type: New feature | Status: new Component: Database lay

Re: [Django] #35566: Support get_FOO_display() on GeneratedField

2024-07-01 Thread Django
#35566: Support get_FOO_display() on GeneratedField -+- Reporter: Ronie Martinez |Owner: nobody Type: New feature | Status: new Component: Database lay