On Sun, May 30, 2010 at 00:38 +0200, holger krekel wrote: > On Sat, May 29, 2010 at 23:59 +0200, Antonio Cuni wrote: > > On 29/05/10 22:25, holger krekel wrote: > > > > > I think the idea is to make sys.prefix (and thus virtualenv) work > > > even with a translation in a checkout, i.e. not forcing to copy > > > things to another location (which virtualenv partly does on its own). > > > > yes > > > > > Moreover, keeping app-level modules (and maybe pypy/module at some point) > > > outside the main (interpreter, objspaces, translation and JIT) PyPy tree > > > makes sense to me. e.g. pypy/lang would probably not need to access > > > anything > > > outside such a pypy tree, for example, or am i mistaken? > > > > I agree that keeping app-level modules out of pypy is a good idea (this is > > what I'm doing it, of course :-)), but I don't get what does the reference > > to > > pypy/lang mean in this context. > > pyrolog for example doesn't use lib_pypy or pypy/module, does it?
sorry, i meant prolog, gameboy, etc ... i.e. the projects in pypy/lang holger _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
