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: installer ignores changed installation directory
Type: behavior Stage: needs patch
Components: Installation Versions: Python 3.2, Python 2.7
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: loewis Nosy List: ajaksu2, blubbfallo, iritkatriel, loewis
Priority: high Keywords:

Created on 2005-05-24 02:21 by blubbfallo, last changed 2022-04-11 14:56 by admin.

Messages (6)
msg25406 - (view) Author: Blubb Fallo (blubbfallo) Date: 2005-05-24 02:21
concerning python-2.4.1.msi at win2000 sp4

After having spent quite some time at python.org to find 
out if I had to remove 2.4 before installing 2.4.1 (without 
any success, btw) I dared to start overinstalling. 

1. Unfortunately, I didn't recognize that the suggested 
directory was different from where I wanted Python to 
stay in. Now, there seems to be no way back except 
completele un- and reinstalling:

2. I run the installer again and selected "change Python 
2.4.1", then clicked "back", choosing the right directory, 
then went on  to "next" and on, but my directory choice 
was ignored.

3. Finally, I run the installer at commandline, specifying 
TARGETDIR, chose the "change Python 2.4.1" 
radiobutton ... and again, Python was reinstalled as if 
TARGETDIR wasn't given.

Paths containing spaces are not involved.
msg25407 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2005-05-30 08:32
Logged In: YES 
user_id=21627

1. Correct, this is indeed the case. However, this sounds
like an operator error, not a bug in Python.

2. Correct. It never occurred to me that somebody would try
to move the installation in a "modify" installation. I will
fix this by disabling the "back" button.

3. Likewise, however, this is an operator error. You
shouldn't be specifying TARGETDIR in the "modify" mode.
msg62788 - (view) Author: Daniel Diniz (ajaksu2) * (Python triager) Date: 2008-02-23 17:57
If the fix was applied, this should be closed. If not, seems pretty easy
to do (worst case: add as Known Issue, Won't Fix).
msg62791 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2008-02-23 18:22
It was not fixed yet, but I will fix it eventually (this year, or later).
msg396168 - (view) Author: Irit Katriel (iritkatriel) * (Python committer) Date: 2021-06-20 11:55
Did Terry remove 3.1 because this is only relevant to python 2?  Is this resolved/obsolete by now?
msg396169 - (view) Author: Irit Katriel (iritkatriel) * (Python committer) Date: 2021-06-20 11:56
Ah I see 3.2 is still there, so it's wasn't just a python 2 issue.
History
Date User Action Args
2022-04-11 14:56:11adminsetgithub: 42005
2021-06-20 11:56:48iritkatrielsetmessages: + msg396169
2021-06-20 11:55:54iritkatrielsetnosy: + iritkatriel
messages: + msg396168
2011-06-12 18:46:28terry.reedysetversions: - Python 3.1
2010-08-21 14:40:27BreamoreBoysetstage: needs patch
type: behavior
versions: + Python 3.1, Python 2.7, Python 3.2
2008-02-23 18:23:00loewissetmessages: + msg62791
2008-02-23 17:57:34ajaksu2setnosy: + ajaksu2
messages: + msg62788
2005-05-24 02:21:55blubbfallocreate