curious about put python code in rust code vs include_str

current case:

pros:

Test code is in the same file, no context change, no error message from editor.

cons:

edit the python code feels like txt.

No file, test, or entry point is named. First locate the current Python test code and how it is embedded in Rust, then compare the two approaches in the affected tests. Done requires a decided, documented convention and agreement on which approach to use.

Written by the indexing model from the issue text.