Changing to future division sitewide

[Michael Williams]

On Sun, 12 May 2002 17:16:14 +0100, Michael Williams wrote:
>>> 2) running a module they've saved (or indeed any module)
>> 
>> Would all such modules be saved from idlefork?  If so, see below.

For the record the fix for this is to ammend change the line that reads:

spawn.spawn( pyth_exe, load_py )

In idle/ExecBinding.py in the IDLEfork source to:

spawn.spawn( pyth_exe, "-Qnew", load_py )

>>> 3) Someone using the interactive interpreter in idlefork
>> 
>>> Presumably this is going to involve doing more than one thing if it
>>> ieven possible. We could always tell our students to put "from
>>> __future__ import division" at the start of every program
>> 
>> I would aim at creating an 'idlepy' command which would bring up python
>> in -Qnew mode (assuming idlefork code itself is 'Qnew clean') 

And Terry was right. Running IDLEfork by doing "python -Qnew <idle>" (<idle>
is just wherever your IDLEfork installation lives) fixes this.
-- 
Michael