Re: [Django] #897: Bi-Directional ManyToMany in Admin

[Django]

#897: Bi-Directional ManyToMany in Admin
---+
 Reporter:  anonymous  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:
 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
---+
Description changed by khaled5321:

Old description:

> Allow amnytomany relationships to be defined both ways
> E.G
>
> {{{
> class ItemType(meta.Model):
> name = meta.CharField(maxlength=100)
> descritpion = meta.CharField(maxlength=250)
>
> class PropertyType(meta.Model):
> name = meta.CharField(maxlength=100)
> itemtypes = meta.ManyToManyField(ItemType)
> }}}
>
> Excellent. When I make a new property type in the admin screens I get a
> mutiselect window for item types.
>
> What I want to be able to do however is have this work back the other
> way too so that whe I create a new item i can specify what property
> types apply.
>
> Thanks

New description:

 Allow manytomany relationships to be defined both ways
 E.G

 {{{
 class ItemType(meta.Model):
 name = meta.CharField(maxlength=100)
 descritpion = meta.CharField(maxlength=250)

 class PropertyType(meta.Model):
 name = meta.CharField(maxlength=100)
 itemtypes = meta.ManyToManyField(ItemType)
 }}}

 Excellent. When I make a new property type in the admin screen I get a
 multiselect window for item types.

 What I want to be able to do however is have this work back the other
 way too so that when I create a new item I can specify what property
 types apply.

 Thanks

--

-- 
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/010701895b7e9af0-959ec9de-8330-45d1-9bef-1221200b5fc1-00%40eu-central-1.amazonses.com.

[Django] #34714: Async support for get_object_or_404

[Django]

#34714: Async support for get_object_or_404
-+-
   Reporter: |  Owner:  nobody
  patagoniapy|
   Type:  New| Status:  new
  feature|
  Component:  Database   |Version:  4.2
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I couldn't find any tickets regarding plans for async support in the
 Django shortcut `get_object_or_404`.

 Is there currently any blocking issues on creating an `agetobject_or_404`?

-- 
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/010701895b5df9bd-c4412379-6506-44b2-bb7c-2810b4b49455-00%40eu-central-1.amazonses.com.

Re: [Django] #34713: Sitemap index performance regression

[Django]

#34713: Sitemap index performance regression
--+--
 Reporter:  Christoph Krybus  |Owner:  nobody
 Type:  Uncategorized |   Status:  new
Component:  contrib.sitemaps  |  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 Christoph Krybus):

 * version:  4.1 => 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/010701895b500dec-a828a481-6767-4d53-add9-0dafb867ae73-00%40eu-central-1.amazonses.com.

[Django] #34713: Sitemap index performance regression

[Django]

#34713: Sitemap index performance regression
+
   Reporter:  Christoph Krybus  |  Owner:  nobody
   Type:  Uncategorized | Status:  new
  Component:  contrib.sitemaps  |Version:  4.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 |
+
 In django 4.1+  was added to sitemap index
 (https://code.djangoproject.com/ticket/25916)

 One consequence of this is that django loads now the whole queryset into
 memory in order to determine the lastmod value for each sitemap entry in
 the sitemap index. In django versions < 4.1 this was not the case, the
 paginator just needed to know the number of elements to generate links to
 the sitemaps.

 My sitemap has ~1.5M entries, it worked OK in django 4.0, in django 4.1
 the VM comes to a standstill.

 There seem to be no way to disable this new feature without also disabling
 lastmod on single entries. As a workaround I'm overriding the whole view
 right now.

 For the vast majority of sites the worse performance should not be a
 problem, but maybe there could be a setting or at least an overridable
 parameter to disable it?

 The index view
 
https://github.com/django/django/blob/4.2.3/django/contrib/sitemaps/views.py#L65
 has already a variable called all_indexes_lastmod maybe it could be
 initialized by a new index view argument? Something like
 `enable_index_lastmod=True`.

-- 
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/010701895b4ea1a5-793a909f-1b93-4eb0-b239-535edc7e8938-00%40eu-central-1.amazonses.com.

Re: [Django] #34709: charset should be ignored for the application/x-www-form-urlencoded content type.

[Django]

#34709: charset should be ignored for the application/x-www-form-urlencoded 
content
type.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  HTTP handling|  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 Shamil, this ticket is already assign to me. We're discussing an
 acceptable approach.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701895aa4a2c5-0fbc5287-5bf4-45dd-8d06-356cfdc3d770-00%40eu-central-1.amazonses.com.

Re: [Django] #34699: Filtering on annotated TruncSecond expression gives unexpected result.

[Django]

#34699: Filtering on annotated TruncSecond expression gives unexpected result.
-+-
 Reporter:  Stefan   |Owner:  Francesco
 Type:   |  Panico
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 I'm pretty sure it's not a valid ticket, but couldn't find quickly find a
 proper justification. Any change to the current behavior would be backward
 incompatible.

-- 
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/010701895aa36fbd-4f80c165-2761-465b-8020-412011e95ded-00%40eu-central-1.amazonses.com.

Re: [Django] #33620: Accessibility in pipeline

[Django]

#33620: Accessibility in pipeline
-+-
 Reporter:  Sarah Abderemane |Owner:  Tushar
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility, ux,   | Triage Stage:  Accepted
  ui, admin  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by Tushar):

 Hi folks, I have made a draft PR to communicate my approach, would love to
 have some feedback there. PR link -
 https://github.com/django/django/pull/17074

-- 
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/010701895a7c0e9d-bd1eb3b4-bb99-4d1e-b4c6-58dc2e39b35b-00%40eu-central-1.amazonses.com.

Re: [Django] #34692: django.forms.renderers.get_default_renderer()'s template loader cache is not being reset on autoloads.

[Django]

#34692: django.forms.renderers.get_default_renderer()'s template loader cache is
not being reset on autoloads.
+---
 Reporter:  Andrew  |Owner:  Priyank Panchal
 Type:  Bug |   Status:  assigned
Component:  Forms   |  Version:  4.2
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+---

Comment (by Amir Karimi):

 Replying to [comment:6 Mariusz Felisiak]:
 > Replying to [comment:5 Amir Karimi]:
 > > It seems if we don't want to add some codes like the above, we have to
 change the flow of creation of the default renderer's engine. The default
 engine is not included in the
 > > {{{
 > > engines.all()
 > > }}}
 > >
 > > @MariuszFelisiak
 > > Do you think it is worth changing the flow? I suggest letting it be
 solved in the simplest way.
 >
 > I'm not sure what are you proposing. We didn't reject any proposition.

 Yeah. I just wanted to think about its optimal solution. I concluded that
 maybe there is no cleaner way to solve this issue than simply coding as
 suggested.

-- 
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/010701895a4bde1c-6e7e4bc2-5df4-4907-a82d-695066606314-00%40eu-central-1.amazonses.com.

Re: [Django] #34711: form.has_changed() is always True for IntegerChoices Enum Model Field

[Django]

#34711: form.has_changed() is always True for IntegerChoices Enum Model Field
+--
 Reporter:  GHPS|Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Forms   |  Version:  4.2
 Severity:  Normal  |   Resolution:  needsinfo
 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 GHPS):

 As suggested I completely started from scratch[1].
 The project is as barebone as it can be.

 But the problem still remains - form.has_changed() is alway True for
 IntegerChoice enums. Even for different browsers (Firefox/Chrome) or
 platforms (Linux/Android)

 The sample code is ready to run: The database has three entries which
 can be viewed under local URL /test/[1,2,3]/. Pressing the save button
 will always trigger the message that the eAsset field has been changed.

 1: https://github.com/GHPS/Django-Enum-Bug

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701895a0d4ea3-dd2a838c-8b39-4ef6-a6f0-335ab8fad65d-00%40eu-central-1.amazonses.com.

Re: [Django] #34036: Low text contrast over light blue backgrounds in admin light theme

[Django]

#34036: Low text contrast over light blue backgrounds in admin light theme
-+-
 Reporter:  Thibaud Colas|Owner:  Mariana
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  color contrast, ux |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
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/01070189595daba0-ff296f85-908d-45b0-aff3-a26d70b25797-00%40eu-central-1.amazonses.com.

Re: [Django] #34712: Prevent misconfiguration of `STORAGES` setting (was: Improve misconfiguration of `STORAGES` setting)

[Django]

#34712: Prevent misconfiguration of `STORAGES` setting
-+-
 Reporter:  Bruno Alla   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070189593b0d17-1c61070c-a246-4d9d-a458-7e402efade22-00%40eu-central-1.amazonses.com.

[Django] #34712: Improve misconfiguration of `STORAGES` setting

[Django]

#34712: Improve misconfiguration of `STORAGES` setting
+
   Reporter:  Bruno Alla|  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:  4.2
   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 new `STORAGES` setting added in #26029 is great and super flexible.
 While trying to migrate Cookiecutter Django to use it [1], I noticed that
 it's quite easy to break the configuration of one of the storages: if I
 want to override only one of the 2 default storages (e.g. staticfiles),
 then I might be tempted to set:

 {{{
 STORAGES = {
 "staticfiles": {"BACKEND": "MyCustomStorage"},
 }
 }}}

 Which would raise a `InvalidStorageError` when trying to upload a
 `FileField` somewhere. AFAIK, nothing warns the user of this
 misconfiguration until this point.

 I think that one might assume that the dictionary defined by the user
 would be "merged" with the default value. I'm assuming that implementing
 behaviour could be considered too much of breaking change to the behaviour
 etablished in 4.2, but I think the documentation could outline better the
 existing behaviour when only one storage is defined by the user.

 Another thing that could be maybe be added is a deployment check, to make
 sure that both `default` and `staticfiles` storages are present in the
 setting.

 [1] https://github.com/cookiecutter/cookiecutter-django/pull/4457

-- 
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/010701895936b89b-980ebf08-53b5-4263-90ae-b90d712a23be-00%40eu-central-1.amazonses.com.

Re: [Django] #34709: charset should be ignored for the application/x-www-form-urlencoded content type.

[Django]

#34709: charset should be ignored for the application/x-www-form-urlencoded 
content
type.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  HTTP handling|  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Shamil Abdulaev):

 * cc: Shamil Abdulaev (added)


Comment:

 Greetings to you! I would like to tackle this bug and solve it!)

-- 
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/0107018959096b50-54bfc80b-1df6-43cb-ba59-9ea74efa9d96-00%40eu-central-1.amazonses.com.

Re: [Django] #34692: django.forms.renderers.get_default_renderer()'s template loader cache is not being reset on autoloads.

[Django]

#34692: django.forms.renderers.get_default_renderer()'s template loader cache is
not being reset on autoloads.
+---
 Reporter:  Andrew  |Owner:  Priyank Panchal
 Type:  Bug |   Status:  assigned
Component:  Forms   |  Version:  4.2
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+---
Changes (by Priyank Panchal):

 * owner:  nobody => Priyank Panchal
 * 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/0107018959048c89-fe3693a0-cb03-412b-90e3-6a306833c81a-00%40eu-central-1.amazonses.com.

Re: [Django] #33143: Block import-time queries

[Django]

#33143: Block import-time queries
-+-
 Reporter:  Adam Johnson |Owner:  Florian
 Type:   |  Zimmermann
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Florian Zimmermann):

 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018958aa5188-c49a428f-359e-4144-a84c-0bfba7b7eeca-00%40eu-central-1.amazonses.com.