suspect-devices/circuitpython/tests/bench/var-8.1-namedtuple-5th.py, branch esp-extra-scripts CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=esp-extra-scripts 2016-05-02T11:15:11+00:00 tests: Update for _io/_collections module having been renamed. 2016-05-02T11:15:11+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-05-02T11:15:11+00:00 urn:sha1:8c35f3979c38bc8a29a22e7a61d33f87ff856124 py: Use sequence of strings for named tuple initialization 2015-01-01T12:53:23+00:00 stijn stinos@zoho.com 2014-12-20T15:37:40+00:00 urn:sha1:12340147b0ace7c1feeaf36b618c92652bdb849f - remove single string initialization style - take list of strings instead - store list in the type for fast lookup tests/bench: Add testcases for lookup in 5-el instance and namedtuple. 2014-05-07T19:34:00+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2014-05-07T18:33:36+00:00 urn:sha1:6638ea9ca37377a8136fb25f64f7c7710f641cd2 ... and we have not that bad mapping type after all - lookup time is ~ the same as in one-attr instance. My namedtuple implementation on the other hand degrades awfully. So, need to rework it. First observation is that named tuple fields are accessed as attributes, so all names are interned at the program start. Then, really should store field array as qstr[], and do quick 32/64 bit scan thru it.