Yes, I saw that.  If a function could raise a NoCache exception,  re._compile() could take advantage of it.  But I don't feel good about going down that path (adding coupling between the caching decorator and the cached function).  It would be better to keep the lru_cache API simple.  I already made the mistake of expanding the API for typed=True just to accommodate a single use case (re.compile).