[issue6047] "install" target in python 3.x makefile should be "fullinstall"

Benjamin Peterson added the comment: Removed fullinstall in r72857. -- resolution: -> accepted status: open -> closed ___ Python tracker ___

[issue6047] "install" target in python 3.x makefile should be "fullinstall"

Georg Brandl added the comment: fullinstall should be removed -- I have the same recollection as Ronald, so if someone really wants python == python3, he can create the link himself. -- nosy: +georg.brandl ___ Python tracker

[issue6047] "install" target in python 3.x makefile should be "fullinstall"

Ronald Oussoren added the comment: 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

[issue6047] "install" target in python 3.x makefile should be "fullinstall"

Benjamin Peterson added the comment: I don't understand. fullinstall still overwrites python to link to python3. -- ___ Python tracker ___ ___

[issue6047] "install" target in python 3.x makefile should be "fullinstall"

New submission from Ronald Oussoren : 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 ful