And the proposed workarounds for this aren’t great. There’s naught to be done but make sure people who need to know, know:
- precompiling sources can silence this one, but this will increase CI/CD runtimes significantly (in aggregate) for some projects that run CI/CD on every development commit
- you can’t filter this properly, but you can supress all SyntaxWarnings as a category. If you do this, you may miss other things with a better signal to noise ratio, use a linter in conjunction.
- Unless there is a process change to commit to actually understanding this use, you should assume this may happen again and transition away from using python’s warning systems. If you want to avoid that being neccessary, as I would, the other thing that can be done is propose process changes to prevent repeats of this. I have started that in another thread