On Thu, Apr 16, 2009 at 13:50 -0600, Maciej Fijalkowski wrote: > On Thu, Apr 16, 2009 at 1:46 PM, holger krekel <[email protected]> wrote: > > Hi Maciej, > > > > On Thu, Apr 16, 2009 at 13:27 -0600, Maciej Fijalkowski wrote: > >> Hello. > >> > >> That might sound a bit like bike sheding, but I would like to talk a > >> bit about naming scheme. > >> > >> What do you think about actually naming PyPy release 2.5 after > >> language version it supports? > >> > >> We can invent suffixes like pypy-2.5-something in order to release > >> still 2.5, but which supports some more > >> things (like JIT?). > > > > i think that PyPy's advances are not too much related to > > language compat issues but rather to better GCs, stackless, > > JITting, optimisations, etc. So i don't see the language > > compat as the central theme. Also, we might be starting > > sometime to release a pypy that can generate interpreters for > > two different CPython versions - how would you name this? > > > > cheers, > > holger > > > > That's exactly the reason why I would like to separate language number from > pypy > advances in other areas, so we can separate two issues. > > It seems unlikely that we can come up with two different python > versions, but even > if we do we can invent new naming scheme. > > I just think pure numbering, like 1.1 is completely meaningless (but > it actually supports > language version 2.5).
version numbers are just meant to indicate and communicate progress. Maybe it's true that the upcoming pypy release is mainly about 2.5 compat, although there also is better cross-platform compilation support, optimizations, stackless, sandboxing and other bits of interest that all not relate much to the "2.5" mem. For the next releases, as you say, it's likely first going to be about the JIT, and i think that's when we should go pypy "2.0", because it's a big step forward. Inventing "2.5-jit-5.0" or something like would be relatively obscure IMO. cheers, holger -- Metaprogramming, Python, Testing: http://tetamap.wordpress.com Python, PyPy, pytest contracting: http://merlinux.eu _______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
