This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author brett.cannon
Recipients Arfrever, brett.cannon, eric.araujo, eric.snow, loewis, ncoghlan, pitrou
Date 2012-04-26.23:52:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1335484321.9.0.895610443199.issue14673@psf.upfronthosting.co.za>
In-reply-to
Content
So I'm w/ Antoine that a dict would be better so that the other VMs can add whatever they want into that object (e.g. Jython could specify what JVM they are running against) without causing confusion as to what some index means to each VM. The mutability of it is not important IMO.

As for the other implementations using importlib, they all plan to with (hopefully) no direct modification, but whether they support bytecode I don't know (I think Jython has talked about it, but who knows).

And pertaining to whether this is useful outside of importlib, I suspect it is. We already have 'jython' as an "OS" type to work around some differences. Adding this attribute would more clearly delineate when another VM is being used that might require working around some difference without overloading os.name (e.g. PyPy implementing something differently in their 1.7 release of Python 2.7 but is subsequently fixed in their 1.8 release).
History
Date User Action Args
2012-04-26 23:52:01brett.cannonsetrecipients: + brett.cannon, loewis, ncoghlan, pitrou, eric.araujo, Arfrever, eric.snow
2012-04-26 23:52:01brett.cannonsetmessageid: <1335484321.9.0.895610443199.issue14673@psf.upfronthosting.co.za>
2012-04-26 23:52:01brett.cannonlinkissue14673 messages
2012-04-26 23:52:01brett.cannoncreate