Issue 6047: "install" target in python 3.x makefile should be "fullinstall" (original) (raw)

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/50297

classification

process

Created on 2009-05-17 10:22 by ronaldoussoren, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (5)
msg87980 - (view)	Author: Ronald Oussoren (ronaldoussoren) *	Date: 2009-05-17 10:22
The default "install" target in the toplevel makefile for python 3.x behaves like the "altinstall" target in python 2.x. This behaviour was choosen to avoid conflicts between python 3.x and python 2.x installations. IMO this is no longer needed, "make fullinstall" can coexist nicely with Python 2.x because the binaries that get installed for Python 3.x are named differently than those in Python 2.x. Furthermore the "fullinstall" target is what most users will actually want to use: that install the 'unversioned' filenames. I therefore propose to renamed the "install" target in Python 3.x to "altinstall" and to rename the "fullinstall" target to "install".
msg87995 - (view)	Author: Benjamin Peterson (benjamin.peterson) *	Date: 2009-05-17 14:02
I don't understand. fullinstall still overwrites python to link to python3.
msg87997 - (view)	Author: Ronald Oussoren (ronaldoussoren) *	Date: 2009-05-17 16:20
Sorry about the noise, I mustn't have been awake this morning :-( The fact that fullinstall still creates a "python" executable confuses me a little though, I thought the consesus at the language summit at Pycon was that we shouldn't do that but only have a "python3" executable.
msg87998 - (view)	Author: Georg Brandl (georg.brandl) *	Date: 2009-05-17 17:00
fullinstall should be removed -- I have the same recollection as Ronald, so if someone really wants python == python3, he can create the link himself.
msg88240 - (view)	Author: Benjamin Peterson (benjamin.peterson) *	Date: 2009-05-23 16:15
Removed fullinstall in r72857.