mirror of
https://github.com/python/cpython.git
synced 2024-11-24 17:47:13 +01:00
bc32024769
If a module has a future statement enabling nested scopes, they are also enable for the exec statement and the functions compile() and execfile() if they occur in the module. If Python is run with the -i option, which enters interactive mode after executing a script, and the script it runs enables nested scopes, they are also enabled in interactive mode. XXX The use of -i with -c "from __future__ import nested_scopes" is not supported. What's the point? To support these changes, many function variants have been added to pythonrun.c. All the variants names end with Flags and they take an extra PyCompilerFlags * argument. It is possible that this complexity will be eliminated in a future version of the interpreter in which nested scopes are not optional. |
||
---|---|---|
.. | ||
.cvsignore | ||
atof.c | ||
bltinmodule.c | ||
ceval.c | ||
codecs.c | ||
compile.c | ||
dup2.c | ||
dynload_aix.c | ||
dynload_beos.c | ||
dynload_dl.c | ||
dynload_hpux.c | ||
dynload_mac.c | ||
dynload_next.c | ||
dynload_os2.c | ||
dynload_shlib.c | ||
dynload_stub.c | ||
dynload_win.c | ||
errors.c | ||
exceptions.c | ||
fmod.c | ||
frozen.c | ||
frozenmain.c | ||
future.c | ||
getargs.c | ||
getcompiler.c | ||
getcopyright.c | ||
getcwd.c | ||
getmtime.c | ||
getopt.c | ||
getplatform.c | ||
getversion.c | ||
graminit.c | ||
hypot.c | ||
import.c | ||
importdl.c | ||
importdl.h | ||
marshal.c | ||
memmove.c | ||
modsupport.c | ||
mystrtoul.c | ||
pyfpe.c | ||
pystate.c | ||
pythonmain.c | ||
pythonrun.c | ||
sigcheck.c | ||
strdup.c | ||
strerror.c | ||
strtod.c | ||
structmember.c | ||
symtable.c | ||
sysmodule.c | ||
thread_beos.h | ||
thread_cthread.h | ||
thread_foobar.h | ||
thread_lwp.h | ||
thread_nt.h | ||
thread_os2.h | ||
thread_pth.h | ||
thread_pthread.h | ||
thread_sgi.h | ||
thread_solaris.h | ||
thread_wince.h | ||
thread.c | ||
traceback.c |