[Python-Dev] Mysterious Python pyc file corruption problems (original) (raw)
Ethan Furman ethan at stoneleaf.us
Thu May 16 18:44:55 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 ]
On 05/16/2013 09:38 AM, Barry Warsaw wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On May 16, 2013, at 06:22 PM, Christian Heimes wrote:
Are you able to reproduce the issue? Perhaps you could use inotify to track down file activity. It shouldn't affect timing much and you can track if more than one process it writing to the same file. Sadly, no. I've never seen it on any of my own desktops or servers, and none of the bug reporters have been able to provide a reproducible test case. I tried some smaller test cases to see if I could trigger pyc writing race conditions, but failed to reproduce it there either.
Is it happening on the same machines? If so, perhaps a daemon to monitor those files and then scream and shout when one changes. Might help track down what's going on at the time. (Yeah, that does sound like saying 'inotify' but with more words...)
--
Ethan
- 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 ]