Changes between Initial Version and Version 1 of Ticket #36622, comment 5


Ignore:
Timestamp:
Oct 9, 2025, 2:47:57 PM (10 days ago)
Author:
Clifford Gama

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #36622, comment 5

    initial v1  
    1 Reopening because this issue can be fixed independently of #36504--it neither contradicts nor, strictly speaking, overlap. The reason being that for `override_settings` to work on custom storages, we still need to write a custom signal receiver. It only seems to work now because we're resolving for the first time after calling `override_settings`. However, whatever value is accessed will persist and cannot be overridden again.
     1Reopening because this issue can be fixed independently of #36504--it neither contradicts nor, strictly speaking, overlap. The reason being that for `override_settings` to work on custom storages (#36504), we still need to write a custom signal receiver. The solution proposed here only seems to solve #36504 because we're resolving the lazy object for the first and only time after calling `override_settings`. However, whatever value we get with the first access will persist and cannot be overridden again.
    22
    33The following modification to the docs example should demonstrate:
Back to Top