Python’s evolution is often about making the "obvious" way to do things the only way to do things. While Issue #122982 might seem like a minor administrative tweak in the CPython GitHub, it reflects the core philosophy of maintaining a stable, readable, and developer-friendly language.
Originally, the plan was to move toward a full error or a more aggressive deprecation schedule. However, Issue #122982 proposes . This extension serves a few key purposes: 122982
Large codebases and libraries need time to refactor code that might be legacy or automatically generated. Python’s evolution is often about making the "obvious"
is_active = True status = ~is_active # Returns -2, triggers warning Use code with caution. Copied to clipboard is_active = True status = not is_active # Returns False Use code with caution. Copied to clipboard Conclusion However, Issue #122982 proposes
Rapidly turning a warning into a hard error can break environments. A longer warning period ensures developers see the notice without their builds immediately failing.