On May 20, 2011, at 01:41 PM, Andreas Röhler wrote: >think we should get the execfile issue fixed with next release too.
Definitely. Sorry for letting this one get buried in my inbox, but I've now commented on the issue. >What about introducing a var indicating the python version the code is >intended to? +1 >In case that var isn't set, the python version which py-execute-region would >call, may be queried on the fly. > >Should I look for this? Yes please! python-mode.el should know whether the file it's visiting is Python 2 or Python 3, probably in a local variable which could be set automatically if you can find a decent clue (e.g. #!/usr/bin/python3). You might want to think of other ways to set this (file local variables, or auto-mode-alist perhaps?) Once you have that, then the mode can do all sorts of version-specific things, like doing different font-locking, or firing off a different Python shell, etc. In this specific case, you could run different Python code, as described in my bug comment. I think this would be a really valuable feature for python-mode.el. Cheers, -Barry
signature.asc
Description: PGP signature
_______________________________________________ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
