This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

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.000873816
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.
History
Date User Action Args
2011-01-25 14:47:21michael.foordsetrecipients: + michael.foord, loewis, georg.brandl, rhettinger, ronaldoussoren, vstinner, benjamin.peterson, ned.deily, naguilera
2011-01-25 14:47:20michael.foordsetmessageid: <1295966840.97.0.670837489521.issue10973@psf.upfronthosting.co.za>
2011-01-25 14:47:20michael.foordlinkissue10973 messages
2011-01-25 14:47:20michael.foordcreate