Files
aitbc/.gitea/workflows
aitbc1 7bfceedc3f
All checks were successful
audit / audit (push) Has been skipped
ci-cd / build (push) Has been skipped
ci / build (push) Has been skipped
autofix / fix (push) Has been skipped
python-tests / test (push) Successful in 16s
python-tests / test-specific (push) Has been skipped
security-scanning / audit (push) Has been skipped
test / test (push) Has been skipped
ci-cd / deploy (push) Has been skipped
ci / deploy (push) Has been skipped
fix: resolve f-string escaping issues in Python debugging
F-STRING ESCAPING FIX: Use string concatenation instead of f-strings

Issue:
- SyntaxError: unterminated f-string literal
- f-string escaping conflicts in exec() within YAML
- Complex nested quoting causing parsing errors

Solution:
- Replace f-strings with string concatenation
- Use str(e) instead of f"{e}"
- Simpler string handling in exec() blocks
- Maintain error reporting functionality

Changes:
- print(" src import failed: " + str(e))
- print(" aitbc import failed: " + str(e))
- Removes f-string complexity
- Preserves error message display

Expected results:
- No more SyntaxError with f-strings
- Import debugging should work
- Clear error messages for failed imports
- Workflow should proceed to pytest execution

This should resolve the f-string escaping conflicts and allow
the import debugging to complete successfully.
2026-03-27 20:49:23 +01:00
..