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.

classification
Title: 2 problems with IDLE
Type: Stage:
Components: IDLE Versions: Python 2.3
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: kbk Nosy List: kbk, loewis, nnorwitz
Priority: low Keywords:

Created on 2003-07-21 15:08 by nnorwitz, last changed 2022-04-10 16:10 by admin. This issue is now closed.

Messages (7)
msg17173 - (view) Author: Neal Norwitz (nnorwitz) * (Python committer) Date: 2003-07-21 15:08
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.
msg17174 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2003-07-21 22:43
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.
msg17175 - (view) Author: Neal Norwitz (nnorwitz) * (Python committer) Date: 2003-07-22 02:19
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.
msg17176 - (view) Author: Kurt B. Kaiser (kbk) * (Python committer) Date: 2003-09-05 23:13
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.
msg17177 - (view) Author: Kurt B. Kaiser (kbk) * (Python committer) Date: 2003-09-06 02:04
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?
msg17178 - (view) Author: Neal Norwitz (nnorwitz) * (Python committer) Date: 2003-09-06 02:10
Logged In: YES 
user_id=33168

No objection from me.
msg17179 - (view) Author: Kurt B. Kaiser (kbk) * (Python committer) Date: 2003-09-10 02:46
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
History
Date User Action Args
2022-04-10 16:10:05adminsetgithub: 38890
2003-07-21 15:08:46nnorwitzcreate