Re: [Django] #29026: Make makemigrations scriptable / script-friendly

[Django]

#29026: Make makemigrations scriptable / script-friendly
-+-
 Reporter:  Chris Jerdonek   |Owner:  Jacob
 |  Walls
 Type:  New feature  |   Status:  assigned
Component:  Migrations   |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  makemigrations,scripting,stderr,stdout|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * 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/067.fc766d35696471984b2299a666748e8f%40djangoproject.com.

Re: [Django] #28619: Handle ValidationError in model saving in admin change views

[Django]

#28619: Handle ValidationError in model saving in admin change views
---+--
 Reporter:  Daniel Hahler  |Owner:  heba1108
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  1.11
 Severity:  Normal |   Resolution:  wontfix
 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 Jerome Leclanche):

 Replying to [comment:1 Simon Charette]:
 > Raising `ValidationError` during model save isn't a pattern used
 anywhere else in the code base. I'm not sure the admin should be different
 in this regard.

 Actually, it kind of is. ModelForm's `_post_clean` hook usage is a hack
 specifically there to work around the inability to raise ValidationError
 during save.

 In the library I'm working on, an object is created in an upstream API
 once the model has been validated locally. When this happens, the upstream
 API does its own field validation. The only way to properly raise form
 errors in that scenario was to hook into `_post_clean()`.

-- 
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/065.e916113c8a6df862973b15beac0d4fdb%40djangoproject.com.

Re: [Django] #26803: Add a statistics option to makemessages

[Django]

#26803: Add a statistics option to makemessages
--+
 Reporter:  Vlastimil Zíma|Owner:  (none)
 Type:  New feature   |   Status:  new
Component:  Internationalization  |  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 Mariusz Felisiak):

 * owner:  Sergey Kolosov => (none)
 * status:  assigned => new


-- 
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/063.07b86f42f613afa91566270ed8cdd514%40djangoproject.com.

Re: [Django] #19544: IntegrityError during ManyToMany add() on Oracle or for user-defined through relationships.

[Django]

#19544: IntegrityError during ManyToMany add() on Oracle or for user-defined
through relationships.
-+-
 Reporter:  German M. Bravo  |Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
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 Mariusz Felisiak):

 * owner:  Simon Charette => (none)
 * status:  assigned => new


-- 
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/064.c80879219a867a5140e5ce30e0612bfc%40djangoproject.com.

Re: [Django] #27055: Model form with geometry widgets has invalid html

[Django]

#27055: Model form with geometry widgets has invalid html
--+
 Reporter:  Antonis Christofides  |Owner:  (none)
 Type:  Bug   |   Status:  new
Component:  GIS   |  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 Mariusz Felisiak):

 * owner:  Antonis Christofides => (none)
 * status:  assigned => new


-- 
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/064.e45ac1273655caece90e51b67078637f%40djangoproject.com.

Re: [Django] #24125: TemplateDetailView in admindocs requires a single Django templates engine

[Django]

#24125: TemplateDetailView in admindocs requires a single Django templates 
engine
-+-
 Reporter:  Aymeric Augustin |Owner:  Kai
 |  Richard König
 Type:  Bug  |   Status:  closed
Component:  contrib.admindocs|  Version:  dev
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  multiple-template-   | Triage Stage:  Accepted
  engines|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


Comment:

 Replying to [comment:4 Tim Graham]:
 > I don't think so many people will hit this issue that it's even worth
 documenting.

 I agree with Tim.

-- 
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/067.2deaa766086f7b2ed1cb63fc7901995d%40djangoproject.com.

Re: [Django] #16149: Allow disabling choices in a

[Django]

#16149: Allow disabling choices in a 
---+
 Reporter:  Jody McIntyre  |Owner:  (none)
 Type:  New feature|   Status:  new
Component:  Forms  |  Version:  1.3
 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 Mariusz Felisiak):

 * owner:  Jody McIntyre => (none)
 * status:  assigned => new


-- 
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/064.08f591f3c69c6aa1c772c4d7a5d4744f%40djangoproject.com.

Re: [Django] #29222: Substr on NULL values returns incorrect results with pattern lookups.

[Django]

#29222: Substr on NULL values returns incorrect results with pattern lookups.
-+-
 Reporter:  Mariusz Felisiak |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Oracle   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  Mariusz Felisiak => (none)
 * status:  assigned => new


Old description:

> feb683c4c2c5ecfb61e4cb490c3e357450c0c0e8 revealed an unrelated issue on
> Oracle. `SUBSTR(NULL, x, y)` returns `NULL` on Oracle which can be
> concatenate with other strings, hence if we use it with pattern lookups
> then all rows match an query, e.g.
>
> - `__startswith=Substr(sth, x, y)` -> `LIKE SUBSTR(sth, x, y) || '%'` ->
> `LIKE '%'`,
> - `__endswith=Substr(sth, x, y)` -> `LIKE '%' || SUBSTR(sth, x, y)` ->
> `LIKE '%'`,
> - `__contains=Substr(sth, x, y)` -> `LIKE '%' || SUBSTR(sth, x, y) || '%'
> ` -> `LIKE '%%'`,
>
> which is unexpected.
>
> ''"Although Oracle treats zero-length character strings as nulls,
> concatenating a zero-length character string with another operand always
> results in the other operand, so null can result only from the
> concatenation of two null strings. However, this may not continue to be
> true in future versions of Oracle Database. To concatenate an expression
> that might be null, use the NVL function to explicitly convert the
> expression to a zero-length string."'' (see
> [https://docs.oracle.com/database/121/SQLRF/operators003.htm#SQLRF51158
> documentation]).

New description:

 feb683c4c2c5ecfb61e4cb490c3e357450c0c0e8 revealed an unrelated issue on
 Oracle. `SUBSTR(NULL, x, y)` returns `NULL` on Oracle which can be
 concatenate with other strings, hence if we use it with pattern lookups
 then all rows match an query, e.g.

 - `__startswith=Substr(sth, x, y)` -> `LIKE SUBSTR(sth, x, y) || '%'` ->
 `LIKE '%'`,
 - `__endswith=Substr(sth, x, y)` -> `LIKE '%' || SUBSTR(sth, x, y)` ->
 `LIKE '%'`,
 - `__contains=Substr(sth, x, y)` -> `LIKE '%' || SUBSTR(sth, x, y) || '%'
 ` -> `LIKE '%%'`,

 which is unexpected.

 ''"Although Oracle treats zero-length character strings as nulls,
 concatenating a zero-length character string with another operand always
 results in the other operand, so null can result only from the
 concatenation of two null strings. However, this may not continue to be
 true in future versions of Oracle Database. To concatenate an expression
 that might be null, use the NVL function to explicitly convert the
 expression to a zero-length string."'' (see
 [https://docs.oracle.com/en/database/oracle/oracle-database/21/sqlrf
 /Concatenation-Operator.html#GUID-08C10738-706B-4290-B7CD-C279EBC90F7E]).

--

-- 
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/065.61c619c3afd98ffd6d145856eb85d8ca%40djangoproject.com.

Re: [Django] #24928: Add UUIDField, RangeField, JSONField, etc to database introspection

[Django]

#24928: Add UUIDField, RangeField, JSONField, etc to database introspection
-+-
 Reporter:  Markus Holtermann|Owner:  (none)
 Type:  New feature  |   Status:  new
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
-+-
Changes (by Mariusz Felisiak):

 * owner:  Claude Paroz => (none)
 * status:  assigned => new


-- 
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/065.7d0176132882a7f1f0056d43f563e082%40djangoproject.com.

Re: [Django] #25704: Response time in WSGIRequestHandler.log_request

[Django]

#25704: Response time in WSGIRequestHandler.log_request
---+
 Reporter:  Andrei Fokau   |Owner:  (none)
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  dev
 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 Mariusz Felisiak):

 * owner:  Andrei Fokau => (none)
 * status:  assigned => new


-- 
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/065.e7e5585c5fdbc862a06a760bd3a6a951%40djangoproject.com.

Re: [Django] #7556: inspectdb fails in MySql if a table references a table outside the current schema

[Django]

#7556: inspectdb fails in MySql if a table references a table outside the 
current
schema
-+-
 Reporter:  brockweaver  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  dev
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mysql foreign key| Triage Stage:  Accepted
  schema inspectdb   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  brockweaver => (none)
 * status:  assigned => new


-- 
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/069.6e67540e28144bd40599da8fb75e017c%40djangoproject.com.

Re: [Django] #30801: Improve guidance for making good use of signals.

[Django]

#30801: Improve guidance for making good use of signals.
--+
 Reporter:  Aymeric Augustin  |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  dev
 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 Mariusz Felisiak):

 * owner:  Caio Ariede => (none)
 * status:  assigned => new


-- 
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/067.69d99f536e8af013ce8d96630c1036d5%40djangoproject.com.

Re: [Django] #33391: Clarify Aggregate.empty_result_set_value docs.

[Django]

#33391: Clarify Aggregate.empty_result_set_value docs.
-+-
 Reporter:  Claude Paroz |Owner:  Mariusz
 Type:   |  Felisiak
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  4.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 Mariusz Felisiak ):

 In [changeset:"fe59bf202d35467e3e4a169c1aac979b713a020a" fe59bf2]:
 {{{
 #!CommitTicketReference repository=""
 revision="fe59bf202d35467e3e4a169c1aac979b713a020a"
 [4.0.x] Fixed #33391 -- Clarified Aggregate.empty_result_set_value docs.

 Backport of 4400d8568ad5695c46e8de45635a82a27a26b871 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/065.44569e8004bd0adeb31a867bb96c37e3%40djangoproject.com.

Re: [Django] #33391: Clarify Aggregate.empty_result_set_value docs.

[Django]

#33391: Clarify Aggregate.empty_result_set_value docs.
-+-
 Reporter:  Claude Paroz |Owner:  Mariusz
 Type:   |  Felisiak
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  4.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 GitHub ):

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


Comment:

 In [changeset:"4400d8568ad5695c46e8de45635a82a27a26b871" 4400d856]:
 {{{
 #!CommitTicketReference repository=""
 revision="4400d8568ad5695c46e8de45635a82a27a26b871"
 Fixed #33391 -- Clarified Aggregate.empty_result_set_value docs.
 }}}

-- 
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/065.f680174a1d74ff489cf8f7d4133868ff%40djangoproject.com.

Re: [Django] #33379: Add minimum database version checks

[Django]

#33379: Add minimum database version checks
-+-
 Reporter:  Tim Graham   |Owner:  Hasan
 |  Ramezani
 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
-+-
Changes (by Mariusz Felisiak):

 * 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/067.08f4f76b5f3940c910ac159fddf068ba%40djangoproject.com.

Re: [Django] #33391: Clarify Aggregate.empty_result_set_value docs.

[Django]

#33391: Clarify Aggregate.empty_result_set_value docs.
-+-
 Reporter:  Claude Paroz |Owner:  Mariusz
 Type:   |  Felisiak
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 [https://github.com/django/django/pull/15263 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/065.6e77faa102553c5198987a35de7ce6a9%40djangoproject.com.

Re: [Django] #33391: Clarify Aggregate.empty_result_set_value docs.

[Django]

#33391: Clarify Aggregate.empty_result_set_value docs.
-+-
 Reporter:  Claude Paroz |Owner:  Mariusz
 Type:   |  Felisiak
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * owner:  nobody => Mariusz Felisiak
 * status:  new => assigned
 * stage:  Accepted => Ready for checkin


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.dc4481d99601d394801ab701b4e22c1f%40djangoproject.com.

Re: [Django] #14296: 'manage.py test' failing for apps that access read-only databases

[Django]

#14296: 'manage.py test' failing for apps that access read-only databases
---+-
 Reporter:  kthhrv |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  1.2
 Severity:  Normal |   Resolution:  needsinfo
 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 Jacob Walls):

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


Comment:

 It's likely that the use case from comment:14 is solved through the
 combination of setting `'TEST': {'MIGRATE': False}` (new in 3.1) and the
 fix for #23273 (merged for 4.1) to skip creating the `django_migrations`
 table.

 Setting back to `needsinfo` in case someone has details to add around the
 interaction of read-only databases with the test runner.

-- 
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/064.b108821679e6902ae9bdbd2d17dc5e35%40djangoproject.com.

Re: [Django] #33391: Clarify Aggregate.empty_result_set_value docs.

[Django]

#33391: Clarify Aggregate.empty_result_set_value docs.
--+
 Reporter:  Claude Paroz  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  4.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 Claude Paroz):

 * has_patch:  0 => 1


Comment:

 Ah thanks, now I understand (even the original sentence!). The new
 proposal is a lot better!

-- 
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/065.95a7f3b4e3b3405d93f523540623e86f%40djangoproject.com.

Re: [Django] #33379: Add minimum database version checks

[Django]

#33379: Add minimum database version checks
-+-
 Reporter:  Tim Graham   |Owner:  Hasan
 |  Ramezani
 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:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Hasan Ramezani):

 * needs_better_patch:  1 => 0


Comment:

 [https://github.com/django/django/pull/15244 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/067.806305a59fddaa9e888e5c29b06afcdc%40djangoproject.com.

Re: [Django] #33401: Error in Django Tutorial # 4

[Django]

#33401: Error in Django Tutorial # 4
-+-
 Reporter:  Frank Claessen   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  4.0
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  django tutorial 4| Triage Stage:
  reverse|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * resolution:  fixed => invalid
 * component:  Uncategorized => Documentation


-- 
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/071.c45ed07ceaff1a1d3a33f640a3ffacb6%40djangoproject.com.

Re: [Django] #33401: Error in Django Tutorial # 4

[Django]

#33401: Error in Django Tutorial # 4
-+-
 Reporter:  frankclaessen|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Uncategorized|  Version:  4.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  django tutorial 4| Triage Stage:
  reverse|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by frankclaessen):

 * cc: frankclaessen (added)
 * status:  new => closed
 * has_patch:  0 => 1
 * resolution:   => fixed


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.e8bc6a10541f125f2de49110afe7685d%40djangoproject.com.

[Django] #33401: Error in Django Tutorial # 4

[Django]

#33401: Error in Django Tutorial # 4
-+-
   Reporter: |  Owner:  nobody
  frankclaessen  |
   Type:  Bug| Status:  new
  Component: |Version:  4.0
  Uncategorized  |   Keywords:  django tutorial 4
   Severity:  Normal |  reverse
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 On page 49 part of views.py is changed and at the end of

 def vote ...:

 there is a redirect as follows:

 return HttpResponseRedirect(reverse('polls:results', args=(question.id,)))

 There is an error however that shows that question.id is in fact empty
 The correct line therefore has to be:

 return HttpResponseRedirect(reverse('polls:results', args=(question_id,)))

 The error is caused by the reverse part by the way, not by the redirect

-- 
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/056.7a2bcec9a3800e5f9249dba7ee2ae086%40djangoproject.com.

Re: [Django] #32243: Clarify docs on manually setting and saving a FileField.

[Django]

#32243: Clarify docs on manually setting and saving a FileField.
-+-
 Reporter:  Gordon Wrigley   |Owner:  Joshua
 Type:   |  Massover
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  3.1
 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 Joshua Massover):

 Replying to [comment:9 Mariusz Felisiak]:
 > See [https://github.com/django/django/pull/15245#issuecomment-1002670888
 comment].

 Updated the 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/065.8313bc9b9eb4691c1a4bc938f13acd4d%40djangoproject.com.

Re: [Django] #33397: Arithmetic operations on DateField/DateTimeField/DurationField expressions are buggy.

[Django]

#33397: Arithmetic operations on DateField/DateTimeField/DurationField 
expressions
are buggy.
-+-
 Reporter:  Luke Plant   |Owner:  Luke
 |  Plant
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.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:  0|UI/UX:  0
-+-
Changes (by Egor R):

 * cc: Egor R (added)


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.b81d57033d7d3b4b3836d8fdbe90e0d1%40djangoproject.com.

Re: [Django] #33400: assertTemplateUsed()/assertTemplateNotUsed() used as context managers ignore count and msg_prefix parameters. (was: assertTemplateUsed as context manager does not respect count pa

[Django]

#33400: assertTemplateUsed()/assertTemplateNotUsed() used as context managers
ignore count and msg_prefix parameters.
---+
 Reporter:  karyon |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  4.0
 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 Mariusz Felisiak):

 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the report. Only `template_name` is used in
 
[https://docs.djangoproject.com/en/stable/topics/testing/tools/#django.test.SimpleTestCase.assertTemplateUsed
 documented] calls, however it sounds reasonable to honor `msg_prefix` and
 `count` when these methods are used as context managers.

 Would you like to provide a patch?

-- 
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/064.a4b77d8f2ed3cecbc87f701d4be99a13%40djangoproject.com.

[Django] #33400: assertTemplateUsed as context manager does not respect count parameter

[Django]

#33400: assertTemplateUsed as context manager does not respect count parameter
-+
   Reporter:  karyon |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Testing framework  |Version:  4.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  |
-+
 See
 
[https://github.com/django/django/blob/cb383753c0e0eb52306e1024d32a782549c27e61/django/test/testcases.py#L659
 the code of assertTemplateUsed]: if it's used as a context manager, the
 count parameter is entirely unused. The
 
[https://docs.djangoproject.com/en/4.0/topics/testing/tools/#django.test.SimpleTestCase.assertTemplateUsed
 documentation on assertTemplateUsed] does not mention that.

 The context manager capability was added in
 [https://github.com/django/django/commit/a678e9ea65 a678e9ea65] 10 years
 ago. The count parameter was added in
 
[https://github.com/django/django/commit/17c18844561431aabed89c3bd48de951db7d13ab
 #diff-7833da5b45a68d00834388d97dd5c4413e3796497c7bc5e0cc2621b08a2d0df1R543
 17c188445] 8 years ago.

-- 
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/049.3b5823188114772ffeb6d724beec1c94%40djangoproject.com.

Re: [Django] #19515: Increase the max_length of Redirect.old_path/new_path

[Django]

#19515: Increase the max_length of Redirect.old_path/new_path
--+
 Reporter:  s.shanabrook@…|Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.redirects |  Version:  dev
 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 Mariusz Felisiak):

 * owner:  Saul Shanabrook => (none)
 * status:  assigned => new


-- 
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/080.145a5af4774f160c2ea896baccd35af4%40djangoproject.com.

Re: [Django] #32502: Replace SQLite schema table rebuild by ALTER functions when supported

[Django]

#32502: Replace SQLite schema table rebuild by ALTER functions when supported
--+
 Reporter:  Simon Charette|Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  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 Mariusz Felisiak):

 * owner:  Mariusz Felisiak => (none)
 * status:  assigned => new


-- 
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/067.c0aa5841de0cd9bed5336c338a07d7cd%40djangoproject.com.

Re: [Django] #33391: Clarify Aggregate.empty_result_set_value docs. (was: Meaning of empty_result_set_value documentation)

[Django]

#33391: Clarify Aggregate.empty_result_set_value docs.
--+
 Reporter:  Claude Paroz  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  4.0
 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 Mariusz Felisiak):

 * stage:  Unreviewed => Accepted


Comment:

 `Aggregate.empty_result_set_value` defaults to `None` which is fine for
 most (all?) aggregates, so I'd clarify this in docs, e.g.:
 {{{#!diff
 diff --git a/docs/ref/models/expressions.txt
 b/docs/ref/models/expressions.txt
 index 5ea7f9f0aa..208b810048 100644
 --- a/docs/ref/models/expressions.txt
 +++ b/docs/ref/models/expressions.txt
 @@ -418,9 +418,8 @@ The ``Aggregate`` API is as follows:

  .. versionadded:: 4.0

 -Override
 :attr:`~django.db.models.Expression.empty_result_set_value` to
 -``None`` since most aggregate functions result in ``NULL`` when
 applied
 -to an empty result set.
 +Defaults to ``None`` since most aggregate functions result in
 ``NULL``
 +when applied to an empty result set.

  The ``expressions`` positional arguments can include expressions,
 transforms of
  the model field, or the names of model fields. They will be converted to
 a
 }}}

-- 
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/065.2786ff4d4134189bdd0ba50e7f4630b7%40djangoproject.com.

Re: [Django] #27753: Cleanups when no supported version of Django supports Python 2 anymore

[Django]

#27753: Cleanups when no supported version of Django supports Python 2 anymore
--+
 Reporter:  Aymeric Augustin  |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Utilities |  Version:  dev
 Severity:  Normal|   Resolution:  fixed
 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 GitHub ):

 In [changeset:"a21a63cc288ba51bcf8c227a49de6f5bb9a72cc3" a21a63cc]:
 {{{
 #!CommitTicketReference repository=""
 revision="a21a63cc288ba51bcf8c227a49de6f5bb9a72cc3"
 Refs #27753 -- Removed unused django.utils.text._replace_entity() and
 _entity_re.

 Unused since 157ab32f3446da7fa1f9d716509c290069a2a156.
 }}}

-- 
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/067.f3152c687de4e4079c2c84804deaee0b%40djangoproject.com.

Re: [Django] #33398: ModelAdmin.empty_value_display example in docs should use list_display.

[Django]

#33398: ModelAdmin.empty_value_display example in docs should use list_display.
-+-
 Reporter:  Michael  |Owner:  Michael
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  4.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:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


Comment:

 Fixed in eb901681ab58c008f7bbbe555e5f43f8e0893bd3 and
 b93fb3d6be944bd196a6a7be576f0622c4e3f59c.

-- 
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/068.305712b0b6f3f5f77385cce75c62b43c%40djangoproject.com.

Re: [Django] #33398: ModelAdmin.empty_value_display example in docs should use list_display.

[Django]

#33398: ModelAdmin.empty_value_display example in docs should use list_display.
-+-
 Reporter:  Michael  |Owner:  Michael
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  nobody => Michael
 * status:  new => assigned
 * has_patch:  0 => 1
 * stage:  Accepted => Ready for checkin


Comment:

 [https://github.com/django/django/pull/15259 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/068.6482469595dae61fd73e731f63d22d41%40djangoproject.com.

Re: [Django] #33398: ModelAdmin.empty_value_display example in docs should use list_display.

[Django]

#33398: ModelAdmin.empty_value_display example in docs should use list_display.
--+
 Reporter:  Michael   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  4.0
 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
--+

Comment (by Mariusz Felisiak):

 IMO it's not important to mention `readonly_fields` in
 `ModelAdmin.empty_value_display` docs, it's already documented in the
 `display()` decorator. I would only change `fields` to `list_display`:
 {{{#!diff
 diff --git a/docs/ref/contrib/admin/index.txt
 b/docs/ref/contrib/admin/index.txt
 index 7b97ee5638..4449afaaa6 100644
 --- a/docs/ref/contrib/admin/index.txt
 +++ b/docs/ref/contrib/admin/index.txt
 @@ -249,7 +249,7 @@ subclass::
  from django.contrib import admin

  class AuthorAdmin(admin.ModelAdmin):
 -fields = ('name', 'title', 'view_birth_date')
 +list_display = ('name', 'title', 'view_birth_date')

  @admin.display(empty_value='???')
  def view_birth_date(self, obj):
 }}}

-- 
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/068.8b1018940699a3abfeab8116ed3ae13f%40djangoproject.com.

Re: [Django] #13251: Add ability to know where an object was deleted from to pre/post delete signals

[Django]

#13251: Add ability to know where an object was deleted from to pre/post delete
signals
-+-
 Reporter:  skoom|Owner:  Marcelo
 |  Galigniana
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  signals  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1
 * needs_tests:  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/063.6de0ba9349186d3608a33863f07da330%40djangoproject.com.

Re: [Django] #33398: ModelAdmin.empty_value_display example in docs should use list_display.

[Django]

#33398: ModelAdmin.empty_value_display example in docs should use list_display.
--+
 Reporter:  Michael   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  4.0
 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
--+

Comment (by Michael):

 Sure I will create a patch, before I submit it, would you please review
 the following, because I am not 100% sure I understand how the readonly
 functionality works for the `empty_value`:

 Change from:
 {{{

 You can also override ``empty_value_display`` for all admin pages with
 :attr:`AdminSite.empty_value_display`, or for specific fields like
 this::

 from django.contrib import admin

 class AuthorAdmin(admin.ModelAdmin):
 fields = ('name', 'title', 'view_birth_date')

 @admin.display(empty_value='???')
 def view_birth_date(self, obj):
 return obj.birth_date
 }}}

 To:

 {{{
 You can also override ``empty_value_display`` for all admin pages with
 :attr:`AdminSite.empty_value_display`.

 To override just a specific ``list_display`` field, or one of the
 ``readonly_fields``, one can do so like this::

 from django.contrib import admin

 class AuthorAdmin(admin.ModelAdmin):
 list_display = ('name', 'title', 'view_birth_date')
 readonly_fields = ('view_birth_date', )
 fields = ('name', 'title', 'view_birth_date')

 @admin.display(empty_value='???')
 def view_birth_date(self, obj):
 return obj.birth_date
 }}}

-- 
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/068.70647329a7a5d62f235b256c155e401f%40djangoproject.com.

Re: [Django] #33397: Arithmetic operations on DateField/DateTimeField/DurationField expressions are buggy.

[Django]

#33397: Arithmetic operations on DateField/DateTimeField/DurationField 
expressions
are buggy.
-+-
 Reporter:  Luke Plant   |Owner:  Luke
 |  Plant
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.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:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * cc: Simon Charette (added)


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.f3481f071c6fc6ee945eebbadacac1c0%40djangoproject.com.

Re: [Django] #27936: Add some clarifications to "Spanning multi-valued relationships"

[Django]

#27936: Add some clarifications to "Spanning multi-valued relationships"
-+-
 Reporter:  Thomas Güttler   |Owner:  Jacob
 Type:   |  Walls
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  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
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"c46e996307b58439eb82343356129a1b971d05ee" c46e996]:
 {{{
 #!CommitTicketReference repository=""
 revision="c46e996307b58439eb82343356129a1b971d05ee"
 [4.0.x] Fixed #27936 -- Rewrote spanning multi-valued relationships docs.

 Backport of 6174814dbe04fb6668aa212a6cdbca765a8b0522 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/065.846791ea6def4db7fb01b50d22069b58%40djangoproject.com.

Re: [Django] #27936: Add some clarifications to "Spanning multi-valued relationships"

[Django]

#27936: Add some clarifications to "Spanning multi-valued relationships"
-+-
 Reporter:  Thomas Güttler   |Owner:  Jacob
 Type:   |  Walls
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"6174814dbe04fb6668aa212a6cdbca765a8b0522" 6174814d]:
 {{{
 #!CommitTicketReference repository=""
 revision="6174814dbe04fb6668aa212a6cdbca765a8b0522"
 Fixed #27936 -- Rewrote spanning multi-valued relationships docs.
 }}}

-- 
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/065.f5d6e869df09ef7d119942df4571da57%40djangoproject.com.

Re: [Django] #31335: Renaming a ForeignKey included in an index, and removing UniqueConstraint, Index with ForeignKey fails on MySQL.

[Django]

#31335: Renaming a ForeignKey included in an index, and removing 
UniqueConstraint,
Index with ForeignKey fails on MySQL.
-+-
 Reporter:  Stephen Finucane |Owner:  Sergey
 |  Fursov
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  3.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1
 * needs_tests:  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/068.b310203bd5bc1ede57d9234bfb91f8be%40djangoproject.com.