Martin v. Löwis wrote: >> Given that this is all about establishing some common ground between >> implementations I would propose not using a CPython specific term >> here such as PyStructSequence :) The Python docs seem to use structseq >> for sys.float_info. > > Also, why does it have to be a sequence in the first place? Wouldn't > a plain object with named attributes be good enough?
Any object with attributes is good enough. For CPython a structseq provides the necessary feature of a read only object with attributes. I figured out it's the easiest way to archive the goal without creating a new class. > >>> compiler (required): >>> verbose name of the compiler, for example "GCC 4.3.3", "Java >>> HotSpot(TM) Client VM (Apple Inc.)", "Mono JIT compiler version 2.0.1" >> What's the value of this attribute? The main reason I ask is there's >> no way that I know of to determine the JIT being used in .NET. We could >> of course fill in some dummy value here for IronPython but I'm also not >> sure why anyone would use this. > > Also, why is it the name of the JIT compiler, and not the name of the > source language compiler? The term "source language compiler" describes the intent of the field perfectly. Thanks Martin! I was merely guessing what the compiler name may look like on Jython. Christian _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
