You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
The location provided when a warning occurs in a python block is not accurate #430
"1" is still ok but now "36" is replaced by "16" which is still odd.
For sure, in this use case, I just need to search for "\j" and I will find my error but in the case of a message not so clear, then the location of the warning could be far more complicated.
At the end, the ideal would be to have the same information as for an error (either directly the line number in the template or the line number of the start of the block + the line number inside the block).
Activity
sqla-tester commentedon Aug 4, 2026
Mike Bayer has proposed a fix for this issue in the main branch:
Report template location for compile time warnings https://gerrit.sqlalchemy.org/c/sqlalchemy/mako/+/6863
sqla-tester commentedon Aug 4, 2026
Mike Bayer has proposed a fix for this issue in the main branch:
Report template location for compile time warnings https://gerrit.sqlalchemy.org/c/sqlalchemy/mako/+/6864
Report template location for compile time warnings