Message157119
| Author |
ncoghlan |
| Recipients |
ncoghlan, vstinner |
| Date |
2012年03月30日.01:34:45 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1333071286.18.0.639986116102.issue14439@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Never mind, I just looked at your patch and better understand what you're wanting to improve (i.e. diagnosing problems with bootstrapping runpy itself, not the errors that occur after runpy has already been found).
However, your proposed solution is questionable since it may produce spurious output when RunMainFromImporter() is executed.
Is it really so hard to do "python -c 'import runpy'" to further diagnose the problem that the bootstrapping reports? |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年03月30日 01:34:46 | ncoghlan | set | recipients:
+ ncoghlan, vstinner |
| 2012年03月30日 01:34:46 | ncoghlan | set | messageid: <1333071286.18.0.639986116102.issue14439@psf.upfronthosting.co.za> |
| 2012年03月30日 01:34:45 | ncoghlan | link | issue14439 messages |
| 2012年03月30日 01:34:45 | ncoghlan | create |
|