[Guido] > I was watching file modification times on my Windows box (strange > hobby, I know :-), and I noticed that after a fresh install of Python, > the .pyc files seem to be written when the first code that imports the > corresponding module runs, rather than all of the .pyc files being > compiled at once by the installer. Wasn't there code in the installer > that precompiles all modules? Not in the PLabs Windows installer, no. > I know the Unix install does this, and I vaguely remember that the > Windows installer did this too -- or was it only the Win32all > installer??? Probably the latter, then. > If there's code to do that in the Windows installer now, it seems it's > not working. There isn't, so it's working fine <wink>. > If there isn't such code, perhaps there should be? Why? Not that increasing installation time and disk consumption aren't worthy goals ...
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