Post #2316380
2025-12-04 13:22 UTC
@stuartm@fosstodon.org the fixer initially did that, but I removed it because it’s unsafe - if the settings file sets any other global default, the attribute is needed, and Django-upgrade can’t tell what your global setting is because it operates file at a time and doesn’t run your code (settings files can have all kind of funkiness to actually determine their values). So yeah, manual removal is the route there!
Replies (0)
No replies.