Author serhiy.storchaka
Recipients mschmitzer, serhiy.storchaka, vstinner
Date 2015-01-08.13:49:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1420724957.47.0.630876402735.issue23191@psf.upfronthosting.co.za>
In-reply-to
Content
It is easy to make fnmatch caching thread safe without locks. Here is a patch.

The problem with fnmatch is that the caching is implicit and a user don't know that any lock are needed. So either the need of the lock should be explicitly documented, or fnmatch should be made thread safe. The second option looks more preferable to me.

In 3.x fnmatch is thread safe because thread safe lru_cache is used.
History
Date User Action Args
2015-01-08 13:49:17serhiy.storchakasetrecipients: + serhiy.storchaka, vstinner, mschmitzer
2015-01-08 13:49:17serhiy.storchakasetmessageid: <1420724957.47.0.630876402735.issue23191@psf.upfronthosting.co.za>
2015-01-08 13:49:17serhiy.storchakalinkissue23191 messages
2015-01-08 13:49:17serhiy.storchakacreate