Issue862707

classification
Title: Carry over __future__ to eval
Type: Severity: normal
Components: None Versions:
Milestone:
process
Status: closed Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: fwierzbicki, lycotic, pedronis
Priority: normal Keywords: patch

Created on 2003-12-19.04:32:31 by lycotic, last changed 2005-07-01.01:11:53 by fwierzbicki.

Files
File name Uploaded Description Edit Remove
patch2 lycotic, 2003-12-19.04:32:32
Messages
msg2313 (view) Author: Randy Brown (lycotic) Date: 2003-12-19.04:32:31
This patch carries over __future__ generator/division 
declarations to eval()/execfile()/etc.  There was some 
support before, but because the flags didn't make it into 
function scopes, they didn't make it all the way through.

eval() also had a special case ignoring this, but it was 
referring to (defunct) support for turning on nested scopes 
(they're always on now).

CPython 2.1 test_long_future.py now passes.

I'd put more direct testing for this in, but I'm not sure 
exactly where.  A test_j*.py in Lib/test? Something in Lib/
test/bugs?
msg2314 (view) Author: Samuele Pedroni (pedronis) Date: 2004-01-05.02:41:28
Logged In: YES 
user_id=61408

thanks,

I know that not getting patches reviewed immediately can be
upsetting. I will review them when I have a first cut at
starting new-style classes support,

it seems I have a stretch of time over the next two months
to start working on that. It's a major road block so ...

I hope it pans out
msg2315 (view) Author: Samuele Pedroni (pedronis) Date: 2005-01-09.20:05:48
Logged In: YES 
user_id=61408

I remember thinking that there's was a slightly better
organization to enable this, anyway there's a failing test
and things can be refactored later.
msg2316 (view) Author: Frank Wierzbicki (fwierzbicki) Date: 2005-07-01.01:11:53
Logged In: YES 
user_id=193969

Applied.
History
Date User Action Args
2003-12-19 04:32:31lycoticcreate