[Python-bugs-list] [ python-Bugs-775061 ] 2 problems with IDLE
SourceForge.net
noreply at sourceforge.net
Tue Sep 9 20:46:21 EDT 2003
Bugs item #775061, was opened at 2003-07-21 10:08
Message generated for change (Settings changed) made by kbk
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=775061&group_id=5470
Category: IDLE
Group: Python 2.3
>Status: Closed
>Resolution: Fixed
Priority: 3
Submitted By: Neal Norwitz (nnorwitz)
Assigned to: Kurt B. Kaiser (kbk)
Summary: 2 problems with IDLE
Initial Comment:
Lib/idlelib/idle.py should use #!/usr/bin/env python
not /usr/bin/python so the user can modify their path
to execute the correct version of python.
In Lib/idlelib/rpc.py around line 623, svr.register
(svr is an RPCServer instance) is called, but there is
no register method AFAICT.
----------------------------------------------------------------------
>Comment By: Kurt B. Kaiser (kbk)
Date: 2003-09-09 21:46
Message:
Logged In: YES
user_id=149084
idle.py 1.11
rpc.py 1.27
removed "idle" script
idle.py actually has the functionality to start IDLE
from any location even when python is not installed:
<path to python>/python <path to python>/Lib/idlelib/idle.py
----------------------------------------------------------------------
Comment By: Neal Norwitz (nnorwitz)
Date: 2003-09-05 21:10
Message:
Logged In: YES
user_id=33168
No objection from me.
----------------------------------------------------------------------
Comment By: Kurt B. Kaiser (kbk)
Date: 2003-09-05 21:04
Message:
Logged In: YES
user_id=149084
My idea on how to resolve this:
remove the "idle" script from idlelib and
remove the shebang from idlelib/idle.py so
it has to be called explicitly. Any objections?
----------------------------------------------------------------------
Comment By: Kurt B. Kaiser (kbk)
Date: 2003-09-05 18:13
Message:
Logged In: YES
user_id=149084
I use (from the idlelib dir):
../../python ./PyShell.py
to start an uninstalled IDLE for testing.
There is a more elaborate idle.py in IDLEfork which allows
starting an uninstalled IDLEfork from anywhere in the file
system. Maybe something like that would be useful to
someone? It's not useful to me, I either use the above,
or call my installed version (which is the latest official
release) from outside that directory. There is always an
installed IDLE now.
I recommend removing the idle script from
idlelib, since it is actually installed from Tools/scripts.
The files there uniformly start with #! /usr/bin/env python.
Exceptions: gprof2html.py, parseentities.py
Without objection, I'm going to remove idlelib/idle.
As far as the RPCServer issue goes, this is defunct test
code. I'll comment it out for now. A proper unit test of
the rpc.py module is needed.
----------------------------------------------------------------------
Comment By: Neal Norwitz (nnorwitz)
Date: 2003-07-21 21:19
Message:
Logged In: YES
user_id=33168
Hmmm, I do remember something about distutils rewriting the
line, but I'm not sure. My problem was that I was running
an uninstalled version in the CVS tree:
./Lib/idlelib/idle
Perhaps this isn't a bug. RPCServer still appears to be a
problem either way.
----------------------------------------------------------------------
Comment By: Martin v. Löwis (loewis)
Date: 2003-07-21 17:43
Message:
Logged In: YES
user_id=21627
I fail to see the first problem. Shouldn't distutils replace
the path in #! with sys.exec_prefix? /usr/bin/env should
*not* be used, as this might be a different python than the
one IDLE was installed for.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=775061&group_id=5470
More information about the Python-bugs-list
mailing list