Message127014
| Author |
michael.foord |
| Recipients |
benjamin.peterson, georg.brandl, loewis, michael.foord, naguilera, ned.deily, rhettinger, ronaldoussoren, vstinner |
| Date |
2011年01月25日.14:47:20 |
| SpamBayes Score |
0.0008738155 |
| Marked as misclassified |
No |
| Message-id |
<1295966840.97.0.670837489521.issue10973@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
The reason I think it is an issue is that a previous release of Python 2.7 could start IDLE (the initial window would appear), but a dialog would also appear saying that it could not connect to the subprocess and IDLE would exit. IDLE itself had been set to run as a 32bit process by default, but "various people" thought the issue was caused by the subprocess not being launched as 32bit. |
|