Repository navigation
turn Cylc 7 deprecated syntax warnings into errors #7367
Description
Activity
Not really a standard thing in my experience... Is it just because we have a particularly stubborn user base? 😅
Somewhat yes, but also partially the result of Cylc's, perhaps, not so clear deprecation timeframes. We've added new warnings recently(ish) which pertain to longer timeframes than some existing warnings, but haven't (until now) differentiated these in a user-facing way. Given the complexity of multiple changes (Cylc 7->8, 8.x deprecations, Rose -> Cylc-Rose, Python 2->3, Jinja2, 2.x->3.0->3.1) which necessitively overlapped (and the lack of a deprecation schedule until now) I think it's reasonable for us to raise the precedence of warnings that will soon become critical to raise them above the background noise to reduce the likelyhood of users getting caught off-guard.
Address this point:
From #7278
PRs to follow up on: