Variables can 'leak' through the stack in Python about duckdb

[soerenwolfers]

Feature proposal for context parameter here: #10191

[soerenwolfers]

In a previous discussion at
#10962 (for example MWE2b there) I was told this is expected given that query is lazy. I personally think it should only be lazy in execution of the SQL not in binding variables and hope this new ticket might convince the maintainers (since your ticket is more to the point than previous tickets and discussions started by myself about my confusion with the Python API).

In the meantime, the solution to your problem is supposed to be calling execute on the query. Unfortunately, that's currently broken and tracked at #11224

[Tishj]

I have seen a proposal to add an optional context to be used by sql/execute replacement scans

I think that might be a good addition, or a maximum depth of stacks to traverse in the effort to look up the variable, which would be 1 here.
One difficulty in this is that we traverse both local and global stacks, perhaps both should have a corresponding stack depth setting

That would also tie in to another request I have seen which is to entirely disable replacement scans
#8100
If the traversal depth was set to 0 that would also satisfy that request