2010/9/13 Maciej Fijalkowski <[email protected]>: > On Mon, Sep 13, 2010 at 9:57 AM, Armin Rigo <[email protected]> wrote: >> Hi, >> >> On Sun, Sep 12, 2010 at 9:58 PM, Bea During <[email protected]> wrote: >>> Maybe we should be clear in our documentation somewhere on >>> where we stand regarding RPython >> >> What about renaming it first? There is at least one other project >> that uses the name RPython. What about something like InterpPy or >> InterpPython to make it clear that it's supposed to be used to write >> interpreters? It doesn't sound terrific but I don't really care -- >> so, comments welcome, but please no infinite discussion on the pros >> and cons of various names. >> > > While we're at it, how about splitting the translation toolchain from > pypy interpreter? I don't mean on technical merits, it can still be > the same or mostly the same source codebase, but more on the > conceptual level, to have 2 different websites names etc.
-0. We don't need more websites/trees to maintain. Anyway, it's not clear to me where the split would be, since the translator and the python interpreter are very interdependent. -- Regards, Benjamin _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
