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 naguilera
Recipients benjamin.peterson, georg.brandl, loewis, michael.foord, naguilera, ned.deily, rhettinger, ronaldoussoren, vstinner
Date 2011-01-23.11:35:54
SpamBayes Score 6.55662e-10
Marked as misclassified No
Message-id <DF0623EE-9C28-44A7-A6F0-1B224BAED2ED@santafe-conicet.gov.ar>
In-reply-to <1295768014.87.0.414889181595.issue10973@psf.upfronthosting.co.za>
Content
On 23 Jan 2011, at 04:33, Georg Brandl wrote:

> Georg Brandl <georg@python.org> added the comment:
> 
>> I disagree. There aren't really "64-bit users" on OSX, thanks to fat
>> binaries. So if starting IDLE would start a 32-bit interpreter, users
>> likely won't even notice. If they do notice, they can still run in
>> 64-bit mode from the command line.

> Okay, fair enough.  If it's easy to always let IDLE run in 32-bit mode, I'm fine with that.  What about other programs using tkinter?

In a previous message (http://bugs.python.org/issue10973#msg126868) I mentioned that I get warning messages with the 32-bit version of 3.1.3 in OSX 10.6. Would a 32-bit version for 3.2 correct these?
History
Date User Action Args
2011-01-23 11:35:56naguilerasetrecipients: + naguilera, loewis, georg.brandl, rhettinger, ronaldoussoren, vstinner, benjamin.peterson, ned.deily, michael.foord
2011-01-23 11:35:54naguileralinkissue10973 messages
2011-01-23 11:35:54naguileracreate