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 serhiy.storchaka
Recipients ethan.furman, giampaolo.rodola, loewis, palaviv, rhettinger, serhiy.storchaka
Date 2017-04-09.07:28:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1491722909.79.0.871317049033.issue26860@psf.upfronthosting.co.za>
In-reply-to
Content
namedtuple's attribute access was optimized in recent years. In 3.7 it is 30% faster than in 3.4. So now it is only 3x times slower compared to a plain tuple. On other hand, os.walk() and os.fwalk() was optimized too. In 3.7 they are up to 3.5x times faster than in 3.4 (with hot caches). I didn't make measurements, but I expect that using namedtuples with os.walk() can decrease its performance at least by few percents.

My main concern is that this feature will increase the complexity of the documentation of the os module (very little) and may encourage writing less clear code (but this is just my own preference, others can found new style more clear).
History
Date User Action Args
2017-04-09 07:28:29serhiy.storchakasetrecipients: + serhiy.storchaka, loewis, rhettinger, giampaolo.rodola, ethan.furman, palaviv
2017-04-09 07:28:29serhiy.storchakasetmessageid: <1491722909.79.0.871317049033.issue26860@psf.upfronthosting.co.za>
2017-04-09 07:28:29serhiy.storchakalinkissue26860 messages
2017-04-09 07:28:29serhiy.storchakacreate