mirror of
				https://github.com/python/cpython.git
				synced 2025-11-04 11:49:12 +00:00 
			
		
		
		
	#403666. Specifically, In codestr, force `c' to be global. It's unclear what the semantics should be for a code object compiled at module scope, but bound and run in a function. In CPython, `c' is global (by accident?) while in Jython, `c' is local. The intent of the test clearly is to make `c' global, so let's be explicit about it. Jython also does not have a __builtins__ name in the module's namespace, so we use a more portable alternative (though I'm not sure why the test requires "__builtins__" in the g namespace). Finally, skip the new.code() test if the new module doesn't have a `code' attribute. Jython will never have this.
		
			
				
	
	
		
			84 lines
		
	
	
	
		
			2.1 KiB
		
	
	
	
		
			Python
		
	
	
	
	
	
			
		
		
	
	
			84 lines
		
	
	
	
		
			2.1 KiB
		
	
	
	
		
			Python
		
	
	
	
	
	
from test_support import verbose, verify
 | 
						|
import sys
 | 
						|
import new
 | 
						|
 | 
						|
class Eggs:
 | 
						|
    def get_yolks(self):
 | 
						|
        return self.yolks
 | 
						|
 | 
						|
print 'new.module()'
 | 
						|
m = new.module('Spam')
 | 
						|
if verbose:
 | 
						|
    print m
 | 
						|
m.Eggs = Eggs
 | 
						|
sys.modules['Spam'] = m
 | 
						|
import Spam
 | 
						|
 | 
						|
def get_more_yolks(self):
 | 
						|
    return self.yolks + 3
 | 
						|
 | 
						|
print 'new.classobj()'
 | 
						|
C = new.classobj('Spam', (Spam.Eggs,), {'get_more_yolks': get_more_yolks})
 | 
						|
if verbose:
 | 
						|
    print C
 | 
						|
print 'new.instance()'
 | 
						|
c = new.instance(C, {'yolks': 3})
 | 
						|
if verbose:
 | 
						|
    print c
 | 
						|
o = new.instance(C)
 | 
						|
verify(o.__dict__ == {},
 | 
						|
       "new __dict__ should be empty")
 | 
						|
del o
 | 
						|
o = new.instance(C, None)
 | 
						|
verify(o.__dict__ == {},
 | 
						|
       "new __dict__ should be empty")
 | 
						|
del o
 | 
						|
 | 
						|
def break_yolks(self):
 | 
						|
    self.yolks = self.yolks - 2
 | 
						|
print 'new.instancemethod()'
 | 
						|
im = new.instancemethod(break_yolks, c, C)
 | 
						|
if verbose:
 | 
						|
    print im
 | 
						|
 | 
						|
verify(c.get_yolks() == 3 and c.get_more_yolks() == 6,
 | 
						|
       'Broken call of hand-crafted class instance')
 | 
						|
im()
 | 
						|
verify(c.get_yolks() == 1 and c.get_more_yolks() == 4,
 | 
						|
       'Broken call of hand-crafted instance method')
 | 
						|
 | 
						|
# It's unclear what the semantics should be for a code object compiled at
 | 
						|
# module scope, but bound and run in a function.  In CPython, `c' is global
 | 
						|
# (by accident?) while in Jython, `c' is local.  The intent of the test
 | 
						|
# clearly is to make `c' global, so let's be explicit about it.
 | 
						|
codestr = '''
 | 
						|
global c
 | 
						|
a = 1
 | 
						|
b = 2
 | 
						|
c = a + b
 | 
						|
'''
 | 
						|
 | 
						|
ccode = compile(codestr, '<string>', 'exec')
 | 
						|
# Jython doesn't have a __builtins__, so use a portable alternative
 | 
						|
import __builtin__
 | 
						|
g = {'c': 0, '__builtins__': __builtin__}
 | 
						|
# this test could be more robust
 | 
						|
print 'new.function()'
 | 
						|
func = new.function(ccode, g)
 | 
						|
if verbose:
 | 
						|
    print func
 | 
						|
func()
 | 
						|
verify(g['c'] == 3,
 | 
						|
       'Could not create a proper function object')
 | 
						|
 | 
						|
# bogus test of new.code()
 | 
						|
# Note: Jython will never have new.code()
 | 
						|
if hasattr(new, 'code'):
 | 
						|
    print 'new.code()'
 | 
						|
    d = new.code(3, 3, 3, 3, codestr, (), (), (),
 | 
						|
                 "<string>", "<name>", 1, "", (), ())
 | 
						|
    # test backwards-compatibility version with no freevars or cellvars
 | 
						|
    d = new.code(3, 3, 3, 3, codestr, (), (), (),
 | 
						|
                 "<string>", "<name>", 1, "")
 | 
						|
    if verbose:
 | 
						|
        print d
 |