Skip to main content

how well do you know python, part 4 

import os

def foo(s):
    f = lambda a: a + "; print '%s'" % os.getcwd()
    exec(f(s))

foo("print 'asdf'")

What error does this give? Why?

This one is pretty tough. I'll put a simpler illustration that gives the same error in the comments as a hint.

(Updated to fix inadvertent SyntaxError in the exec'd string, pointed out by Ian Bicking. Python bails with the error I intended before reaching that point, though.)

Comments

Jonathan Ellis said…
Doh, blogger doesn't allow <pre> in comments... Here it is in nbsp-d glory. (This is the last time I try giving hints. :)

import os

def foo(s):
  f = lambda: os.gtcwd()
  exec(s)

foo("print 'asdf'")
8:51 AM
Anonymous said…
Note that it does print "asdf" in 2.0 and earlier. For extra credit, figure out *why* that was changed in 2.1.
10:55 AM
Ian Bicking said…
Huh. I figured the first one would bail because it would try to execute "print 'asdf'; print /home/ianb'" which is syntactically incorrect. But not so, since there's a syntax error before that, but I had to cheat and run the program to find that out.

I'm guessing the reason for the error is because f doesn't know if "os" is a local or a global function in the presence of an exec that happens inside the scope of the function. E.g., foo("os=None") would make os a local variable, where otherwise it would be a global variable. Or something. If you use "f = lambda os=os: os.getcwd()" you're all good, because "os" doesn't get looked up in the enclosing scope when f() is called (it's already bound, or rebound by the call). But I'm still fuzzy on the reasoning behind the error.
11:29 AM
Anonymous said…
Fredrik wrote: "Note that it does print "asdf" in 2.0 and earlier. For extra credit, figure out *why* that was changed in 2.1."

I can tell you why it won't work in Python 3.0: lambda sucks and will finally be gone. I'd rather have no anonymous methods than a crippled one.
5:35 PM
Anonymous said…
"""I can tell you why it won't work in Python 3.0: lambda sucks and will finally be gone. I'd rather have no anonymous methods than a crippled one."""

It has nothing to do with lambda. The same effect happens when using a regular def statement.
8:48 PM
Anonymous said…
Having been pretty immersed in python bytecode during my latest project, I think I can make a good stab at this one: Python won't allow the unqualified exec because the existence of the nested function with free variables means there's a possibility of some local variables being stored in cells. The exec won't be able to tell which ones are cell variables (so it wouldn't know whether to use STORE_FAST or STORE_DEREF, for example). Free variables and the corresponding local variables in the nesting scope are stored in cells, so both frames can have references.
11:41 AM
Post a Comment

Popular posts from this blog

The Missing Piece in AI Coding: Automated Context Discovery

I recently switched tasks from writing the ColBERT Live! library and related benchmarking tools to authoring BM25 search for Cassandra . I was able to implement the former almost entirely with "coding in English" via Aider . That is: I gave the LLM tasks, in English, and it generated diffs for me that Aider applied to my source files. This made me easily 5x more productive vs writing code by hand, even with AI autocomplete like Copilot. It felt amazing! (Take a minute to check out this short thread on a real-life session with Aider , if you've never tried it.) Coming back to Cassandra, by contrast, felt like swimming through molasses. Doing everything by hand is tedious when you know that an LLM could do it faster if you could just structure the problem correctly for it. It felt like writing assembly without a compiler -- a useful skill in narrow situations, but mostly not a good use of human intelligence today. The key difference in these two sce...
Post a Comment
Read more

A week of Windows Subsystem for Linux

I first experimented with WSL2 as a daily development environment two years ago. Things were still pretty rough around the edges, especially with JetBrains' IDEs, and I ended up buying a dedicated Linux workstation so I wouldn't have to deal with the pain.  Unfortunately, the Linux box developed a heat management problem, and simultaneously I found myself needing a beefier GPU than it had for working on multi-vector encoding , so I decided to give WSL2 another try. Here's some of the highlights and lowlights. TLDR, it's working well enough that I'm probably going to continue using it as my primary development machine going forward. The Good NVIDIA CUDA drivers just work. I was blown away that I ran conda install cuda -c nvidia and it worked the first try. No farting around with Linux kernel header versions or arcane errors from nvidia-smi. It just worked, including with PyTorch. JetBrains products work a lot better now in remote development mod...
Post a Comment
Read more

Why PHP sucks

(July 8 2005) Apparently I got linked by some PHP sites, and while there were a few well-reasoned comments here I mostly just got people who only knew PHP reacting like I told them their firstborn was ugly. These people tended to give variants on one or more themes: All environments have warts, so PHP is no worse than anything else in this respect I can work around PHP's problems, ergo they are not really problems You aren't experienced enough in PHP to judge it yet As to the first, it is true that PHP is not alone in having warts. However, the lack of qualitative difference does not mean that the quantitative difference is insignificant. Similarly, problems can be worked around, but languages/environments designed by people with more foresight and, to put it bluntly, clue, simply don't make the kind of really boneheaded architecture mistakes that you can't help but run into on a daily baisis in PHP. Finally, as I noted in my original introduction, with PHP, ...
30 comments
Read more