mirror of
https://github.com/python/cpython.git
synced 2025-08-31 14:07:50 +00:00
Merged revisions 55270-55324 via svnmerge from
svn+ssh://pythondev@svn.python.org/python/branches/p3yk ........ r55271 | fred.drake | 2007-05-11 10:14:47 -0700 (Fri, 11 May 2007) | 3 lines remove jpeg, panel libraries for SGI; there is more IRIX stuff left over, I guess that should be removed too, but will leave for someone who is sure ........ r55280 | fred.drake | 2007-05-11 19:11:37 -0700 (Fri, 11 May 2007) | 1 line remove mention of file that has been removed ........ r55301 | brett.cannon | 2007-05-13 17:38:05 -0700 (Sun, 13 May 2007) | 4 lines Remove rexec and Bastion from the stdlib. This also eliminates the need for f_restricted on frames. This in turn negates the need for PyEval_GetRestricted() and PyFrame_IsRestricted(). ........ r55303 | brett.cannon | 2007-05-13 19:22:22 -0700 (Sun, 13 May 2007) | 2 lines Remove the md5 and sha modules. ........ r55305 | george.yoshida | 2007-05-13 19:45:55 -0700 (Sun, 13 May 2007) | 2 lines fix markup ........ r55306 | neal.norwitz | 2007-05-13 19:47:57 -0700 (Sun, 13 May 2007) | 1 line Get the doc building again after some removals. ........ r55307 | neal.norwitz | 2007-05-13 19:50:45 -0700 (Sun, 13 May 2007) | 1 line Get test_pyclbr passing again after getstatus was removed from commands. This "test case" was weird since it was just importing a seemingly random module. Remove the import ........ r55322 | brett.cannon | 2007-05-14 14:09:20 -0700 (Mon, 14 May 2007) | 3 lines Remove the compiler package. Will eventually need a mechanism to byte compile an AST. ........
This commit is contained in:
parent
827b055ffe
commit
a8add0ec5e
68 changed files with 52 additions and 9866 deletions
|
@ -1562,13 +1562,6 @@ opcodes = [
|
|||
the object is updated via
|
||||
|
||||
anyobject.__dict__.update(argument)
|
||||
|
||||
This may raise RuntimeError in restricted execution mode (which
|
||||
disallows access to __dict__ directly); in that case, the object
|
||||
is updated instead via
|
||||
|
||||
for k, v in argument.items():
|
||||
anyobject[k] = v
|
||||
"""),
|
||||
|
||||
I(name='INST',
|
||||
|
@ -1604,11 +1597,7 @@ opcodes = [
|
|||
calling __init__() is current wisdom). In this case, an instance of
|
||||
an old-style dummy class is created, and then we try to rebind its
|
||||
__class__ attribute to the desired class object. If this succeeds,
|
||||
the new instance object is pushed on the stack, and we're done. In
|
||||
restricted execution mode it can fail (assignment to __class__ is
|
||||
disallowed), and I'm not really sure what happens then -- it looks
|
||||
like the code ends up calling the class object's __init__ anyway,
|
||||
via falling into the next case.
|
||||
the new instance object is pushed on the stack, and we're done.
|
||||
|
||||
Else (the argtuple is not empty, it's not an old-style class object,
|
||||
or the class object does have a __getinitargs__ attribute), the code
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue