[issue34846] Runtime failure with Failed to import site module

Change by Irit Katriel : -- resolution: -> rejected stage: -> resolved status: pending -> closed ___ Python tracker ___ ___ Python

[issue34846] Runtime failure with Failed to import site module

Irit Katriel added the comment: It doesn't look like there is enough information here to do anything about this, and there has been no response from the OP to follow-up questions. I think we need to close it. -- nosy: +iritkatriel status: open -> pending

[issue34846] Runtime failure with Failed to import site module

Terry J. Reedy added the comment: Unless this is seen as a possible security issue, this will not be fixed in 3.5. If possible test in later versions. By 'was running for a long time without issue', do you mean 'ran many times before this run'? (As opposed to 'a long time in this run'?) D

[issue34846] Runtime failure with Failed to import site module

Karthikeyan Singaravelan added the comment: Thanks for the report. Can you please add the full stack trace as text in the comment so that it's more accessible? Searching along similar lines there is an open issue about corrupted .pyc causing import related failure in issue28007 with a patch

[issue34846] Runtime failure with Failed to import site module

New submission from Satheesh Thomas : Run time failure to execute python scripts. It was running for long time without any issue . But sometimes get this error which stops the entire execution. Looks like some .pyc file got corrupted . -- components: Build files: Python error1.png mes