Post #2316379
2025-12-04 05:25 UTC
@adamchainz@fosstodon.org Answering my own question after reading your docs and source code. It looks like django-upgrade doesn't remove it, but that it should be safe for me to do it manually.
Replies (1)
-
@adamchainz@fosstodon.org 2025-12-04 13:22
@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!