First things first. Thanks for replies. I am still crunching.. As I already received a similar question about if the topic is appropriate for PyPy in private email from other person, so I repeat my reply below as-is. Mind you the the discussion here is not "debate". When I say "I expect" - I of course mention my own problem of understanding, but the answer I need is not what should I do, but why it works differently? I am not familiar with exec* calls in Unix, but for me the analogy is misleading, and something like "LXC for Python code" may be a better analogy, because I don't want to replace the current process. What I am interested to know is what kind of code isolation execfile() supports and why it doesn't do full isolation by default? It looks like this is answered, but I need time to validate it. On Wed, Mar 27, 2013 at 1:00 AM, Armin Rigo <arigo@tunes.org> wrote:
Hi all,
Could you please move this debate somewhere else? pypy-dev is not the appropriate place where to discuss the Python language in general (but topics about differences between CPython and PyPy are fine of course). There is already for example http://mail.python.org/mailman/listinfo/python-list .
It looks like python@ is more appropriate for basic questions about the usage of the existing language. My question is about internal mechanism that supports language design. Not only asking about existing behavior, but also about why this behavior can not be changed. I thought that people who are writing Python in Python are more skilled to answer such questions. In the end, I understood that PyPy project was created so that people who can't read C could still understand and experiment with their own language, no? -- anatoly t.