Re: [Django] #12096: Model fields are not accessible as attributes of the model class

[Django]

#12096: Model fields are not accessible as attributes of the model class
-+-
 Reporter:  sejo |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  model, docstrings,   | Triage Stage:  Accepted
  attributes |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 Since `DeferredAttribute`
 
[https://github.com/django/django/commit/7f51876f99851fdc3fef63aecdfbcffa199c26b9
 #diff-35c61cb049d39b2e890f12f8c1f9583fb8ca351a8495718b5375a7120f775d05R700
 are systematically added as model class attributes] (#26207) this would be
 a simple matter of adjusting a few `__get__(instance=None)` case to return
 `self.field` (`DeferredAttribute` and the three classes of
 `related_descriptors`).

 The only remaining concern here is backward compatibility.
 
[https://github.com/django/django/blob/e30d6678421b7573a1995f61521f14348c9b2a17/django/db/models/fields/related_descriptors.py#L900-L905
 The only documented pattern of accessing a field attribute] from the class
 is for `ManyToMany.through` via `ManyToManyDescriptor.through` but there
 might be valid use cases in the wild for expecting descriptors to be
 returned that this change could break. As long as we document this change
 and that it's still possible to retrieve descriptors by doing
 `ModelClass.__dict__.get('descriptor')` I think we should be fine though.

 Beyond the documentation benefits this could pave the way for interesting
 features that the verbosity of `Model._meta.get_field` such as SQLAlchemy-
 esque lookups (e.g.
 `Book.objects.filter(Book.title.contains(Book.author.name))` ) but most
 importantly it would restore the most intuitive pattern for field
 retrieval.

-- 
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/010701829a70e8d2-29309a3b-5610-4f10-8beb-6f375488c84d-00%40eu-central-1.amazonses.com.

Re: [Django] #11156: Unnecessary savepoints with Oracle

[Django]

#11156: Unnecessary savepoints with Oracle
-+-
 Reporter:  Richard Davies   |Owner:  (none)
   |
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  oracle savepoints| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

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


Comment:

 I'm going to wont-fix this one.

 No conversation update for the past 9 years and still no performance
 benchmarks demonstrating that it is a change worth the extra complexity it
 introduces.

 The transaction logic is already complex and Oracle has proven to be the
 hardest backend to support for the past years. I'm far from convinced than
 attempting to take advantage of this
 [https://docs.oracle.com/cd/E11882_01/server.112/e40540/transact.htm#CNCPT1115
 statement-level atomicity feature] will bring more benefits than the
 maintenance burden it will incur.

-- 
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/010701829a31221d-a57b3571-d02b-4509-ab16-d80b5c915524-00%40eu-central-1.amazonses.com.

Re: [Django] #28296: Add support for aggregation through subqueries

[Django]

#28296: Add support for aggregation through subqueries
-+-
 Reporter:  László Károlyi   |Owner:  B
 |  Martsberger
 Type:  New feature  |   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:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 #10621 was a 13 years old duplicate.

-- 
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/010701829a1e7469-ebd36fc7-a29c-48cf-9a40-56502772ae3c-00%40eu-central-1.amazonses.com.

Re: [Django] #10621: Add a way to have an aggregate() result as a queryset

[Django]

#10621: Add a way to have an aggregate() result as a queryset
-+-
 Reporter:  Malcolm Tredinnick   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 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 Simon Charette):

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


Comment:

 #28296 is a duplicate which happens to have more up-to-date discussion and
 and associated patch so I'll close this one as a duplicate.

-- 
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/010701829a1d2518-ad449214-aeb3-40f4-892b-1a8fb7d2979f-00%40eu-central-1.amazonses.com.

Re: [Django] #33920: Document that LOGGING_CONFIG callback is not called when LOGGING dict is not set.

[Django]

#33920: Document that LOGGING_CONFIG callback is not called when LOGGING dict is
not set.
-+-
 Reporter:  Craig de Stigter |Owner:  Kinza-
 Type:   |  Raza
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  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 Kinza-Raza):

 * owner:  nobody => Kinza-Raza
 * 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/01070182987fafab-67ba65dd-9526-4427-bb0d-4fe13a5c5ec2-00%40eu-central-1.amazonses.com.

Re: [Django] #33920: Document that LOGGING_CONFIG callback is not called when LOGGING dict is not set.

[Django]

#33920: Document that LOGGING_CONFIG callback is not called when LOGGING dict is
not set.
--+
 Reporter:  Craig de Stigter  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  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
--+

Comment (by Kinza-Raza):

 I'd like to take this up.

-- 
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/01070182987e17e0-f1b93064-9665-4658-8e3e-e68e3ecfbb34-00%40eu-central-1.amazonses.com.

Re: [Django] #28678: Multipart parser should decode those JSON parts that are flagged as such

[Django]

#28678: Multipart parser should decode those JSON parts that are flagged as such
-+-
 Reporter:  Facundo Batista  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  HTTP handling|  Version:  1.11
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz):

 Replying to [comment:2 timtaiwanliim]:
 > > it could be backwards incompatible (data could now be a different type
 in request.POST, correct?).
 >
 > Not so.
 > Only if the parts have http header "content-type: application/json",
 > then those parts become dict (the desired type; currently of str
 > type).
 > For the parts (of multiparts) that do not have "content-type" header,
 > the results remain as str type.

 That's indeed the backwards compatibility issue: typically, current code
 expects a `str` and call `json.loads(data)` to convert it to a Python
 structure. If suddenly the data is another Python structure (dict, list,
 etc.), the same code will suddenly crash with an error like `TypeError:
 the JSON object must be str, bytes or bytearray, not dict`. Do you have an
 idea to avoid that issue?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018298322f47-f92d2e33-815e-474c-8c5e-204639dec8e9-00%40eu-central-1.amazonses.com.

Re: [Django] #26511: Document KeyTextTransform() and KeyTransform().

[Django]

#26511: Document KeyTextTransform() and KeyTransform().
-+-
 Reporter:  Eoin Murray  |Owner:
 Type:   |  AllenJonathan
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  postgres, jsonb  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  nobody => AllenJonathan
 * needs_better_patch:  1 => 0
 * status:  new => assigned


Comment:

 [https://github.com/django/django/pull/15956 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/0107018297382ea9-5c3ab392-1ccd-4b30-a16b-241cd6700bec-00%40eu-central-1.amazonses.com.

Re: [Django] #32519: Add support for using key and path transforms in update() for JSONFields.

[Django]

#32519: Add support for using key and path transforms in update() for 
JSONFields.
-+-
 Reporter:  Baptiste Mispelon|Owner:  Kamil
 |  Turek
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (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 Kamil Turek):

 * owner:  (none) => Kamil Turek
 * 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/0107018296a31ebe-84f45f33-af58-4969-a7b9-d889322aba84-00%40eu-central-1.amazonses.com.

Re: [Django] #33090: Extend sensitive post parameter filtering to be applicable to exceptions in middleware.

[Django]

#33090: Extend sensitive post parameter filtering to be applicable to 
exceptions in
middleware.
-+
 Reporter:  Carlton Gibson   |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Error reporting  |  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
-+

Comment (by Carlton Gibson):

 Thanks Daniele, no problem. Take care.

-- 
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/01070182966bd788-14dd3696-f23f-4b3e-a838-37505f47dc9c-00%40eu-central-1.amazonses.com.

Re: [Django] #33922: New version of pytz is breaking Django 3.2.x

[Django]

#33922: New version of pytz is breaking Django 3.2.x
-+--
 Reporter:  Denny Biasiolli  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Uncategorized|  Version:  3.2
 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 Carlton Gibson):

 This looks like a duplicate of #33814, related to the move to use
 `ZoneInfo`.

 Your system likely doesn't have the timezone database installed, so `pip
 install tzdata` should resolve it for you.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701829669ba5c-a61f5e3b-f7b0-466b-939e-bfb33174ab11-00%40eu-central-1.amazonses.com.