[Idle-dev] [ idlefork-Patches-686254 ] Run IDLEfork from any directory without set-up

[SourceForge.net]

Patches item #686254, was opened at 2003-02-13 17:15
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=309579&aid=686254&group_id=9579

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Noam Raphael (noamr)
Assigned to: Nobody/Anonymous (nobody)
Summary: Run IDLEfork from any directory without set-up

Initial Comment:
This patch adds the directory of the PyShell module to
the PYTHONPATH environment variable of the spawned
subprocess, so that it will find the IDLEfork modules
no matter from which directory it was run, no matter
where they are, and with no need for changing system
configuration.

----------------------------------------------------------------------

>Comment By: Kurt B. Kaiser (kbk)
Date: 2003-02-22 20:53

Message:
Logged In: YES 
user_id=149084

You could install python2.2-dev, which contains the necessary
distutils code.  Alternatively, you could add the IDLE directory
to your sys.path via a Python startup file referenced by your
PYTHONSTARTUP env variable.  That would do the same 
thing as the patch, but specifically for your situation.

----------------------------------------------------------------------

Comment By: Noam Raphael (noamr)
Date: 2003-02-22 16:32

Message:
Logged In: YES 
user_id=679426

I'm trying to solve the problem of using idlefork if it was
not installed using distutils. On my machine it seems that I
don't have distutils - the command "from distutils.core
import setup" raises "ImportError: No module named
distutils.core", both as root and as a normal user, both on
python 2.1.3 (the default) and on python 2.2.1. I'm using
debian woody.
I think it may help a large group of users - those without
root privileges. It will also help users who just want to
experiment - to them, extracting the files to a directory
and running, without installing, is the easiest way.
In such cases, when idlefork's files just sit in their
directory, and you want a Python shell in your current
directory (this happens to me a lot of times), you must
change to idlefork's directory, run ./idle, and then change
back to your original directory both in your system shell
and in your Python shell, and still, when you open a file
from an idlefork's window, you must manually go to your
working directory. I think running, say, ~/idlefork/idle, is
much simpler than the process I described above.

----------------------------------------------------------------------

Comment By: Kurt B. Kaiser (kbk)
Date: 2003-02-17 16:30

Message:
Logged In: YES 
user_id=149084

It's not clear to me what problem you are trying to
solve with this patch.  It's not intended that the
user's search path include IDLEfork.  If you want that,
try e.g. import idleforklib.PyShell.  If you are in the 
IDLEfork directory, just import PyShell will work.  Are
you having some problem starting IDLEfork?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=309579&aid=686254&group_id=9579