Moshe Zadka wrote: > > Trusting OS-based mtimes for .pyc caching has some inherent problems. > (Clock syncing and similar) Frankly, though I've never been bitten by > this, it does give me an uncomfortable feeling. What if, instead, we'd use > md5- or sha-based approach? I'm willing to bet that the 2^128 chance of > problems is miniscule compared to the real problems clock syncing has > already caused. (I think I remember some problem with .pyc's on IIS, but > I may just be hallucinating) > > Problems: > .pyc size would increase by 24 bytes <wink> Much worse: you'd have to recalculate the MD5-sum every time you import the .pyc file... Frankly, I don't think this is needed at all ;-) -- Marc-Andre Lemburg ______________________________________________________________________ Business: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4