For me, that’s not an upgrade path, that’s a removal path. Django will be shipping a superior solution than the try/except: is_configured(). It’s needless churn to ask users to go through a removal path for a feature when we plan to ship an replacement for a feature in short order. That’s why I said it was “out of the ordinary” to advance these pieces in separate releases. I’m not digging in my heels – maybe there’s a compelling reason to do it – I’m just saying I question the reason. Nothing should prevent us from reviewing and approving the work in separate chunks like we did for other complex features.
Super minor point to be debating, so I’m happy to leave it for some other time 