[Idle-dev] [ idlefork-Bugs-665814 ] path to python executable not parsed correctly

[SourceForge.net]

Bugs item #665814, was opened at 2003-01-10 10:50
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=109579&aid=665814&group_id=9579

Category: None
Group: None
>Status: Closed
>Resolution: Works For Me
Priority: 5
Submitted By: Gyro Funch (siva1311)
Assigned to: Nobody/Anonymous (nobody)
Summary: path to python executable not parsed correctly

Initial Comment:
When starting pyshell.py from the command line, I get
the following:

C:\Program: can't open file 'Files\Python22\python.exe'

It appears that there is a problem with spaces in the
path name leading to the Python executable.

Platform: Win2000
Python 2.2


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

>Comment By: Kurt B. Kaiser (kbk)
Date: 2003-01-10 11:41

Message:
Logged In: YES 
user_id=149084

Duplicate of 661191

The first thing I would check is whether the associations
between the .py and .pyw extensions and python/pythonw
are set correctly.

Using the command line on W2K is problematic, Redmond
is doing their best to eradicate it.
cd Program Files   works
dir Program Files does not

FWIW, on my W2K box I can call idlefork.pyw from
the Program Files\Python\Scripts directory and it
starts up OK.  (I renamed the file per the installation
notes)  

My Python is installed at
c:\Program Files\Python\  and I'm running 2.2.1

If you want to be able to call Python from anywhere
in the filesystem, you will have to add it to your PATH.

If you want to start IDLEfork I'd recommend not
calling PyShell.py.  Call idlefork.py instead.

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

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