Mailman 3 July 2003 - pypy-dev

stale link
by Laura Creighton July 7, 2003

July 7, 2003

in http://codespeak.net/pypy/doc/sprintinfo/LouvainLaNeuveReport.html 'iterobject' is a stale link.

3 2

side "sprint"
by holger krekel July 7, 2003

July 7, 2003

hello pypy, some people already know it. I am hosting a small sprint at the same location as the first PyPy-Sprint, the Trillke-Gut in Hildesheim (germany) between 12th and 19th of July. This coding week will not focus primarily on pypy but more on the codespeak-infrastructure and whatever (python) programming tasks. Jens-Uwe and me plan among other things to enhance the codespeak server configuration and i have some pypy-related tasks on my list: - generate a pypy "documentation overview" which should show which document was updated last and by whom etc.pp. - implement functional tests for codespeak services (subversion/web/mail integration) - enhance the wiki, maybe convert it to ReST and use/enhance Subwiki from Greg Stein?! - enhance testing of pypy and have an automatically generated "status" webpage which shows which revision broke which tests under which object space etc.pp. - look to enhance the tool/test.py and unittest-infrastructure If you have any suggestions (the smaller the better!) or comments feel free to reply to this post. Everybody will be welcome between 12th and 19th of July. Actually, this week will also be interesting because musicians, writers and other artists will also meet and be productive (kind of trying the sprint-model in non-computer areas) and on 19th there is a big party. So this will probably be unlike the other more coding-intensive sprints. Actually, I don't expect many of the former pypy-sprinters because Goethenburg and and Louvain-La-Neuve/ EuroPython have been pretty intense and took a lot of time from everyone in the last two month. Of course there is enough room so you can probably join even on short-notice. And sorry for not posting this earlier but i was/am ill and had to care for some other stuff first. If you need more detailed information about the sprint-location and how to get there contact me privately. cheers, holger

2 1

Re: [pypy-dev] Annotating space status
by Samuele Pedroni July 7, 2003

July 7, 2003

At 19:31 04.07.2003 -0400, Guido van Rossum wrote: > > >I have a feeling that the real problem here may be that the value > > >stack isn't properly cloned, which means that the frames stored in > > >knownframes will share their objects with the frame being modified as > > >part of the current frame evaluation. I'd bet that if you properly > > >clone the value stack using clonecells(), Samuele's hack (adding a > > >'changed' flag to the W_ConstantIterator class) would no longer be > > >necessary. > > > > > >Wishing I had time to code this up, > > > > makes sense, done. > >Thanks, cool. r = self.codetest("def f(a):\n" " x = [1,2]\n" " if a:\n" " x.append(3)\n" " else:\n" " x.append(3)\n" " return x", 'f',[W_Anything()]) print r this prints W_Constant([1, 2, 3, 3]) the first obvious fix works up to: r = self.codetest("def f(a):\n" " x = [1,2]\n" " y = x\n" " if a:\n" " x.append(3)\n" " else:\n" " x.append(3)\n" " return y", 'f',[W_Anything()]) if we care about this, it seems that state cloning should be done on the state as a whole caring for identity like pickling or deepcopy do.

4 8

will anything break if we rename pypy/trunk/doc/EU funding
by Laura Creighton July 6, 2003

July 6, 2003

to to pypy/trunk/doc/EU_funding? My tools cannot easily tolerate spaces in filenames. Laura

2 1

suggestion for infastructure Sprint
by Laura Creighton July 6, 2003

July 6, 2003

While I am thinking of it ... I would like it if automatically generated pypy docs also came with a 'click here to get to the PyPy home page' link. Laura

2 1

OSCON paper
by Laura Creighton July 6, 2003

July 6, 2003

I am refactoring it, with an eye to producing something which is more like an introduction to PyPy. This can then get used in part for the EU funding proposal, while I can make slides out of it for OSCON. As for slides -- if any of you have any pictures which you would like used, let me know. Otherwise I am going to select some: if you are going to present a paper from a team, it helps to show pictures so people get to' know who the team is beyond a long list of names on the Paper. I would also like to use Armin's slide of: <WHY> <HOW> <HOW SLOW> Can I have it, please? I also think that the dis example is rather instructive, but I can't remember exactly what you ran. I think that, as a presentation, it would work to first run a CPython version, and then start the PyPy version. Then start to answer questions from the audience about PyPy and wait for the expected cheer when we start to get output. What do you think? Too corny? Also is there any code which you would like to be shown? It is difficult now for me to see PyPy with fresh eyes, so it is hard for me to see where I should begin to explain PyPy code wise. Ah well, to work where I will try to install of this on a fresh machine. Laura

2 1

Re: [pypy-dev] Annotating space status
by Samuele Pedroni July 4, 2003

July 4, 2003

At 16:05 04.07.2003 -0400, Guido van Rossum wrote: > > For the problem with W_ConstantIterator I'm a bit confused. Where is > > the code that allows more than just one frame to be saved for the > > same bytecode position? In other words I don't understand how this > > code can unroll the loops in the helpers. > >I have a feeling that the real problem here may be that the value >stack isn't properly cloned, which means that the frames stored in >knownframes will share their objects with the frame being modified as >part of the current frame evaluation. I'd bet that if you properly >clone the value stack using clonecells(), Samuele's hack (adding a >'changed' flag to the W_ConstantIterator class) would no longer be >necessary. > >Wishing I had time to code this up, makes sense, done.

2 1

RE: [pypy-dev] website update / pypy developments
by roccomoretti＠netscape.net July 4, 2003

July 4, 2003

holger krekel <hpk(a)trillke.net> wrote: > After some discussions especially with Armin > i now think that we should promote as a goal to > > dynamically tie into/adapt arbritrary C-Libraries and > operation system calls. > > The latter would basically mean that you could use Python directly to > drive your favourite OS. Think rapidly specializing for whatever > embedded device without even a libc and doing that with 99% of the > code beeing written in Python. I'm a little unclear by what you mean by this goal. As best I can tell, you envision being able to put a shared library facade over pypy functions, and then have the C/whatever library function calls be able to seamlessly call into pypy without recompilation. e.g. we could write a glibc facade which runs pypy 'under the hood' and drive precompiled linux programs with pypy. Is this getting close to the idea? ... If so, you are either insanely brilliant, or insanely insane - though I'd lean toward the former. What-will-they-think-up-next-ly 'ers -Rocco __________________________________________________________________ McAfee VirusScan Online from the Netscape Network. Comprehensive protection for your entire computer. Get your free trial today! http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397 Get AOL Instant Messenger 5.1 free of charge. Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promo=380455

3 3

Re: [pypy-dev] Annotating space status
by Samuele Pedroni July 4, 2003

July 4, 2003

At 15:18 02.07.2003 -0400, Guido van Rossum wrote: > > the problem is our fix-point condition which is mostly based purely > > on types, and that we are trying to have it both ways, doing some > > mixture of constant propagation (normal eval) and type propagation, > > if you consider code like this: > > > > x = 0 > > while True: > > x = x + 2 > > > > type propagation can end, but constant evaluation will give an > > infinite loop. > > > > So we should clarify what we really want. > > > > One possibility is optinally instead of using types to decide > > fix-points, we stop if some bytecode (position) has been encountered > > more than N times. > >Right. We could differentiate this by using the differentiation of >object space and execution context for evaluation of internal helpers. > >Those helpers want constant evaluation, and they already get a >different object space (a subclass of the annotating object space). >The space controls the execution context, and the execution context >controls whether we check for fix-point conditions. > >The "real" code would continue to use the "normal" annotation space >and would do full type propagation. another problem is that for the momement we unify between different invocation of a same function but we don't reflow the information trough the entire call-graph, we just traverse some part of it as needed: r = self.codetest("def f():\n" " x = g(1)\n" " y = g('1')\n" " return x\n" # vs. return y "def g(y):\n" " return y\n", 'f', []) print r in the 'return x' case r is W_Constant(1) in the 'return y' case r is W_Anything() this is sort of bogus, and here too we should clarify what we want: - reflow type info through the call-graph somehow (this means more code complexity) and get in both cases W_Anything() - don't unify beetween different invocation of a same function: maybe that's enough for our purposes and get W_Constant(1), W_Constant('1') respectively.

3 3

Builtin Modules, Annotation Space
by roccomoretti＠netscape.net July 4, 2003

July 4, 2003

Hello all, I've made some updates to the interpreter internals to generalize builtin module loading (with an eye toward getting an os module). These changes pass all tests on trivial and standard object spaces, but cause test_all.py to crash under -A during the ObjSpace initilization (it doesn't even get to the "Running tests under ..."). My best guess is that when I'm working with wrapped objects in the initilization code, I'm running afoul of what AnnObjSpace is doing, probably in the same way that running the interpreter app-level helper functions under AnnObjSpace does not work. (We want the code to execute, not be translated.) How should the people working on the interpreter internals deal with wrapped objects, such that we don't run afoul of AnnObjSpace? Are there guidelines as to what operations are allowed when? For those who want to take a look, the diff of my changes should be attached. (I'm not commiting it yet for obvious reasons.) -Rocco __________________________________________________________________ McAfee VirusScan Online from the Netscape Network. Comprehensive protection for your entire computer. Get your free trial today! http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397 Get AOL Instant Messenger 5.1 free of charge. Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promo=380455 Index: interpreter/test/test_main.py =================================================================== --- interpreter/test/test_main.py (revision 1082) +++ interpreter/test/test_main.py (working copy) @@ -21,7 +21,7 @@ def checkoutput(expected_output,f,*args): space = test.objspace() - w_sys = space.get_builtin_module(space.wrap("sys")) + w_sys = space.w_sys w_oldout = space.getattr(w_sys, space.wrap("stdout")) capture.reset() space.setattr(w_sys, space.wrap("stdout"), space.wrap(capture)) Index: interpreter/baseobjspace.py =================================================================== --- interpreter/baseobjspace.py (revision 1082) +++ interpreter/baseobjspace.py (working copy) @@ -1,6 +1,6 @@ from executioncontext import ExecutionContext, OperationError, NoValue import pyframe, threadlocals -import pypy.module.builtin +import pypy.module __all__ = ['ObjSpace', 'OperationError', 'NoValue', 'PyPyError'] @@ -18,30 +18,46 @@ def __init__(self): "Basic initialization of objects." self.w_modules = self.newdict([]) + self.w_builtin_module_names = self.newlist([]) self.appfile_helpers = {} self.initialize() def make_builtins(self): + import pypy.module.builtin self.builtin = pypy.module.builtin.Builtin(self) self.w_builtin = self.builtin.wrap_base() + # self.builtins must be set before wrap_appfile (or wrap_me) is called. self.w_builtins = self.getattr(self.w_builtin, self.wrap("__dict__")) self.builtin.wrap_appfile(self.w_builtin) + w_name = self.getattr(self.w_builtin, self.wrap("__name__")) + self.setitem(self.w_modules, w_name, self.w_builtin) + self.call_function(self.getattr(self.w_builtin_module_names, + self.wrap('append')), + w_name) + + def make_builtin_modules(self): + #Note - self.w_builtins must be set before calling this function + for filename, classname, spacelist in pypy.module._builtin_modules: + if self.__class__.__name__ in spacelist: + pypy_ = __import__('pypy.module.'+filename) + file_ = getattr(getattr(pypy_,'module'),filename) + module = getattr(file_, classname)(self) #Call class with space + if module is None: + continue + w_module = module.wrap_me() + w_name = self.getattr(w_module, self.wrap("__name__")) + self.setitem(self.w_modules, w_name, w_module) + self.call_function(self.getattr(self.w_builtin_module_names, + self.wrap('append')), + w_name) + def make_sys(self): - import pypy.module.sysmodule - self.sys = pypy.module.sysmodule.Sys(self) - self.w_sys = self.sys.wrap_me() + self.w_sys = self.getitem(self.w_modules,self.wrap("sys")) self.setattr(self.w_sys, self.wrap("modules"), self.w_modules) - - # XXX use a dictionary in the future - def get_builtin_module(self, w_name): - name = self.unwrap(w_name) - if name == '__builtin__': - return self.w_builtin - elif name == 'sys': - return self.w_sys - return None - + self.setattr(self.w_sys, self.wrap("builtin_module_names"), + self.w_builtin_module_names) + def initialize(self): """Abstract method that should put some minimal content into the w_builtins.""" Index: module/test/test_sysmodule.py =================================================================== --- module/test/test_sysmodule.py (revision 1082) +++ module/test/test_sysmodule.py (working copy) @@ -4,7 +4,7 @@ class SysTests(test.TestCase): def setUp(self): self.space = test.objspace() - self.sys_w = self.space.get_builtin_module(self.space.wrap("sys")) + self.sys_w = self.space.w_sys def tearDown(self): pass @@ -12,6 +12,36 @@ s = self.space self.failUnless_w(s.getattr(self.sys_w, s.wrap("stdout"))) +class SysAppTests(test.AppTestCase): + def setUp(self): + self.space = test.objspace() + + def test_sys_in_modules(self): + import sys + modules = sys.modules + self.failUnless('sys' in modules, "An entry for sys " + "is not in sys.modules.") + sys2 = sys.modules['sys'] + self.failUnless(sys is sys2, "import sys is not sys.modules[sys].") + + def test_builtin_in_modules(self): + import sys + modules = sys.modules + self.failUnless('__builtin__' in modules, "An entry for __builtin__ " + "is not in sys.modules.") + import __builtin__ + builtin2 = sys.modules['__builtin__'] + self.failUnless(__builtin__ is builtin2, "import __builtin__ " + "is not sys.modules[__builtin__].") + + def test_builtin_module_names(self): + import sys + names = sys.builtin_module_names + self.failUnless('sys' in names, + "sys is not listed as a builtin module.") + self.failUnless('__builtin__' in names, + "__builtin__ is not listed as a builtin module.") + if __name__ == '__main__': test.main() Index: module/__init__.py =================================================================== --- module/__init__.py (revision 1082) +++ module/__init__.py (working copy) @@ -0,0 +1,17 @@ + +_all_spaces = ['TrivialObjSpace','StdObjSpace', + 'AnnotationObjSpace','HelperObjSpace'] + +# A list of (filename, classname, [applicable spaces]) tuples +# describing the builtin modules (pypy.interpreter.extmodule.BuiltinModule) +# availible in the pypy.module directory. + +# classname should be a classname of a callable in 'filename' that returns +# an unwrapped builtin module (pypy.interpreter.extmodule.BuiltinModule +# instance) - it returns unwrapped None if the builtin module is not to +# be loaded. (e.g. this is the wrong platform.) + +#Note: the builtin module is special cased for bootstrapping reasons. + +_builtin_modules = [('sysmodule','Sys',_all_spaces), + ] Index: module/builtin.py =================================================================== --- module/builtin.py (revision 1082) +++ module/builtin.py (working copy) @@ -42,10 +42,6 @@ except executioncontext.OperationError,e: if not e.match(space, space.w_KeyError): raise - w_mod = space.get_builtin_module(w_modulename) - if w_mod is not None: - space.setitem(space.w_modules,w_modulename,w_mod) - return w_mod import os, __future__ for path in space.unwrap(space.getattr(space.w_sys, w('path'))): Index: objspace/trivial.py =================================================================== --- objspace/trivial.py (revision 1082) +++ objspace/trivial.py (working copy) @@ -152,6 +152,7 @@ newstuff[c.__name__] = c newstuff.update(self.clone_exception_hierarchy()) self.make_builtins() + self.make_builtin_modules() self.make_sys() # insert these into the newly-made builtins for key, w_value in newstuff.items(): Index: objspace/std/objspace.py =================================================================== --- objspace/std/objspace.py (revision 1082) +++ objspace/std/objspace.py (working copy) @@ -176,6 +176,7 @@ for_builtins.update(self.clone_exception_hierarchy()) self.make_builtins() + self.make_builtin_modules() self.make_sys() # insert stuff into the newly-made builtins Index: objspace/ann/objspace.py =================================================================== --- objspace/ann/objspace.py (revision 1082) +++ objspace/ann/objspace.py (working copy) @@ -36,6 +36,7 @@ if isinstance(c, types.TypeType) or isinstance(c, types.ClassType): setattr(self, 'w_'+n, self.wrap(c)) self.make_builtins() + self.make_builtin_modules() self.make_sys() # Service methods whose interface is in the abstract base class

1 0