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 methane
Recipients methane, ncoghlan, rhettinger, xiang.zhang
Date 2016-11-08.06:09:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1478585356.61.0.00899987235569.issue28638@psf.upfronthosting.co.za>
In-reply-to
Content
> The slow import is the case only the first time functools is imported. Later imports will just use the cache (sys.modules).

Yes. But first import time is also important for CLI applications.
That's why mercurial and Bazaar has lazy import system.

Since many stdlib uses functools, many applications may be suffered from
slow functools import even if we remove it from site.py.

>  maybe we don't have to copy the entire namedtuple structure?

https://docs.python.org/3.5/library/functools.html#functools.lru_cache

The doc says it's a namedtuple.  So it should be namedtuple compatible.
History
Date User Action Args
2016-11-08 06:09:16methanesetrecipients: + methane, rhettinger, ncoghlan, xiang.zhang
2016-11-08 06:09:16methanesetmessageid: <1478585356.61.0.00899987235569.issue28638@psf.upfronthosting.co.za>
2016-11-08 06:09:16methanelinkissue28638 messages
2016-11-08 06:09:16methanecreate