Hi Maciej, Armin, On Sun, Oct 21, 2012 at 14:03 +0200, Maciej Fijalkowski wrote: > Hi > > Due to impressive work by Ronan Lamy, we're now able to split RPython > and PyPy. Note that the fact of splitting this is not up to > discussion, however, how we go about it is. During discussions with > Armin we came up with the following plan: > > * We make a copy of pypy repo called rpython. it'll still live under > pypy team on bitbucket. > > * We'll rename toplevel package of pypy to rpython, for the rpython > part. Since we need to change ALL THE IMPORTS, we can do refactorings > of imports now. Proposed changes: > > * to be moved from pypy to rpython: annotation, translator, rlib > * pypy.config must be split somehow, same for tool, bin and for doc > * move pypy.rpython namespace to rpython.rtyper > * move pypy.rpython.lltypesystem to rpython.lltypesystem, same for ootype > * pypy.rpython.memory becomes rpython.gc > * pypy.objspace.flow becomes rpython.flowspace > * testrunner and dotviewer can become independent packages > * _pytest stays with pypy, however for rpython you can use whatever > version of py.test you have installed. rpython test suite should also > however be runnable under current contents of _pytest > > * RPython will come with setup.py and be a "normal" python package
great stuff! Samuele's comments also make sense to me as well (rpython.typer etc.). Will there be a setup.py with pypy to automatically install perequisites (such as RPython, possibly other bits)? FWIW, I think it could help to eventually allow people more easily maintain modular rpython-level pypy modules by depending on a specific pypy version and declaring an entry-point in order to be automatically picked up by the pypy translation process. This way one could install multiple pypy-MODULE* packages, then cause a pypy build and all those modules would become part of the translated pypy-c. (happy to help with this and relate my experiences if wanted). It's not binary compatibility but would be a way to have a user choose modules without having to dive into translation target scripts etc. best, holger > Cheers, > fijal & armin > _______________________________________________ > pypy-dev mailing list > pypy-dev@python.org > http://mail.python.org/mailman/listinfo/pypy-dev > _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
