Then I see pyvm dwindling to near-zero size, since nearly all the types considered here are seen as official APIs by Jython, IronPython and PyPy.
Also, if it's VM-specific perhaps it ought to have a VM-specific name. Personally, I think they should all move into existing modules -- many will fit in collections (dict_proxy etc.), others in sys (module, function, frame etc.). --Guido On Nov 30, 2007 4:06 PM, Greg Ewing <[EMAIL PROTECTED]> wrote: > Terry Reedy wrote: > > "Christian Heimes" <[EMAIL PROTECTED]> wrote in message > > news:[EMAIL PROTECTED] > > > > | I've started to work on a pyvm module patch today. > > Is there a clear rationale for the dividing line between > sys and pyvm? > > Maybe the distinction should be that pyvm is for things that > could change from one Python implementation to another, > whereas sys is for language-defined things that should > be present in every implementation. > > -- > Greg > > _______________________________________________ > Python-3000 mailing list > Python-3000@python.org > http://mail.python.org/mailman/listinfo/python-3000 > Unsubscribe: > http://mail.python.org/mailman/options/python-3000/guido%40python.org > -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
