[Python-Dev] future and eval() (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Sun Oct 2 03:22:07 EDT 2016
- Previous message (by thread): [Python-Dev] __future__ and eval()
- Next message (by thread): [Python-Dev] __future__ and eval()
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 1 October 2016 at 22:18, Chris Angelico <rosuav at gmail.com> wrote:
On Sat, Oct 1, 2016 at 10:17 PM, Chris Angelico <rosuav at gmail.com> wrote:
So I'd call it a feature, but possibly one that warrants a mention in the exec and eval docs. To clarify: This is documented under future, but not under exec/eval. I'm just suggesting adding another cross-reference.
The most appropriate cross-reference would probably be to the compile() docs rather than the language reference though: https://docs.python.org/2/library/functions.html#compile
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message (by thread): [Python-Dev] __future__ and eval()
- Next message (by thread): [Python-Dev] __future__ and eval()
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]