[Python-bugs-list] [ python-Bugs-537328 ] Problematic .py extension mapping on XP
noreply@sourceforge.net
noreply@sourceforge.net
Sun, 31 Mar 2002 02:40:42 -0800
Bugs item #537328, was opened at 2002-03-31 18:28
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=537328&group_id=5470
Category: Installation
Group: Platform-specific
Status: Closed
Resolution: Wont Fix
Priority: 5
Submitted By: steve matheson (stevematheson)
Assigned to: Tim Peters (tim_one)
Summary: Problematic .py extension mapping on XP
Initial Comment:
When the windows pre built version installs on
windows xp it sets up a file association that
maps ".py" to the c:\python22\python.exe executable
as it should.
If python is installed in "c:\program files\python22"
the map ".py" points to "c:\progra~1\python22". This
is fine and from the command line <script>.py runs as
expected.
However, if one then trys to set up a script map in
IIS on XP (so that "http:\host\test\script.py"
works) it proves impossible. The IIS admin snap in
returns "wrong executeable" even though the correct
executeable "c:\program files\python22\python.exe %s %
s" is selected. This is because the two mappings must
match exactly.
The manual work around is to enter the 8.3 file name
form of the "program to execute" against ".py" in the
IIS admin snap-in rather than use the browse button
(which returns the normal NT/XP long form of the
name).
The better solution which would remove all confusion
is to ensure the install script enters the full form
of the file name in file association mapping.
i.e. associate
.py with c:\program files\python22\python.exe
rather than
.py with c:\progra~1\python22\python.exe
which it does currently.
Then the IIS admin snapin would work as expected.
----------------------------------------------------------------------
>Comment By: steve matheson (stevematheson)
Date: 2002-03-31 22:40
Message:
Logged In: YES
user_id=307994
Fair enough ... but it has just taken me about 6 hours to
work out what was going on and I guess others will be
eqaully frustrated so in the interests of building py a
positive following perhaps you could change the installer
to prevent the location being changed, or at least
restrict the options, or as a last resort warn of the
implications. Keep up the good work. Rgds Steve
----------------------------------------------------------------------
Comment By: Tim Peters (tim_one)
Date: 2002-03-31 19:05
Message:
Logged In: YES
user_id=31435
Sorry, I'm closing this as WontFix. If you choose to
install into a non-default location, you're responsible for
dealing with the consequences. Some years ago the
PythonLabs installer did install under "Program Files" by
deafault, and associated to the full path, and the problems
*that* created for people were endless (especially embedded
spaces). Now we deliberately install into a non-
problematic ("short name" same as "long name", no embedded
spaces) path by default. Note that can you easily change
the .py association yourself (Windows supplies several
simple ways to do that).
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=537328&group_id=5470