Changes between Version 2 and Version 3 of Ticket #36445, comment 8


Ignore:
Timestamp:
Jun 11, 2025, 9:31:59 AM (3 months ago)
Author:
Thomas

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #36445, comment 8

    v2 v3  
    77- https://github.com/django/django/commit/6fc620b4a8e91839b93af2b52d80bdbd5f8a1fcc was introduced in `5.2.3`. After this commit the test fails again.
    88
    9 I've checked `Value.for_save`, and it is indeed `False` in `5.2.2` and `True` in `5.2.3` for the `Value` in the `When` condition. So, I understand why #36453 may have been closed as a duplicate of this one: it sounds like the same change may be responsible. My only concern is that the bug in this ticket only covers one of the symptoms of that change (that may or may not be a regression), but not the one I'm experiencing (which I really hope is considered a regression), and that addressing this symptom will not fix the behavior that's been broken in my case. Let me know if I'm taking this ticket off-topic and I'll re-open my ticket and continue there.
     9I've checked `Value.for_save`, and it is indeed `False` in `5.2.2` and `True` in `5.2.3` for the `Value` in the `When` condition. So, I understand why #36453 may have been closed as a duplicate of this one: it sounds like the same change may be responsible. My only concern is that the bug in this ticket only covers one of the side-effects of that change (that may or may not be a regression), but not the one I'm experiencing (which I really hope is considered a regression), and that addressing this side-effect will not fix the behavior that's been broken in my case. Let me know if I'm taking this ticket off-topic and I'll re-open my ticket and continue there.
Back to Top