[Python-Dev] Mysterious Python pyc file corruption problems
Greg Ewing
greg.ewing at canterbury.ac.nz
Fri May 17 00:27:01 CEST 2013
More information about the Python-Dev mailing list
Fri May 17 00:27:01 CEST 2013
- Previous message: [Python-Dev] Mysterious Python pyc file corruption problems
- Next message: [Python-Dev] Mysterious Python pyc file corruption problems
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Guido van Rossum wrote: > This reminds me of the following bug, which can happen when two > processes are both writing the .pyc file and a third is reading it. > ... I think all the errors are > actually explainable from this scenario. The second writer will still carry on to write a valid .pyc file, though, won't it? So this wouldn't result in a permanently broken .pyc file being left behind, which is what the original problem description seemed say was happening. -- Greg
- Previous message: [Python-Dev] Mysterious Python pyc file corruption problems
- Next message: [Python-Dev] Mysterious Python pyc file corruption problems
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list