-
-
Notifications
You must be signed in to change notification settings - Fork 60
[blurb] f-string simulation does not work with closures. #299
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
GitMate.io thinks possibly related issues are #154 (blurb refuse to work without setting EDITOR env), #149 ( |
I ran into this issue also when implementing a similar function and I ended up creating namespace_format to format a string from the locals and globals. But maybe blurb should just use future-fstrings or just drop support for Python 3.5 (which is EOL anyway). |
Dropping Python 3.5 support looks the right way to me too. |
I'm in favor of dropping 3.5 support. (#283) |
In the
throw
function, theraise BlurbError(f("Error in {filename}:{line_number}:\n{s}"))
can't find the filename variable leading to:To reproduce it: invoke blurb, empty the buffer, and close the editor.
I don't think we should try to fix
def f
, maybe simple addnonlocal filename
andnonlocal file_number
so they become visible in the function locals.The text was updated successfully, but these errors were encountered: