[issue10677] "make altinstall" includes ABI codes in versioned executable name

2010-12-11 Thread Barry A. Warsaw
Barry A. Warsaw added the comment: r87174 moves the creation of the hard link between python-3.2m and python-3.2 from the bininstall target to the altbininstall target. -- resolution: -> fixed status: open -> closed ___ Python tracker

[issue10677] "make altinstall" includes ABI codes in versioned executable name

2010-12-11 Thread Arfrever Frehtes Taifersar Arahesis
Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue10677] "make altinstall" includes ABI codes in versioned executable name

2010-12-11 Thread Éric Araujo
Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue10677] "make altinstall" includes ABI codes in versioned executable name

2010-12-11 Thread Georg Brandl
Georg Brandl added the comment: Nice, definitely a blocker. (BTW, if you configured without any specific --prefix, you shouldn't clobber anything installed by the distribution...) -- ___ Python tracker _

[issue10677] "make altinstall" includes ABI codes in versioned executable name

2010-12-11 Thread Nick Coghlan
Nick Coghlan added the comment: The other thing that makes this clearly an error is, of course, the fact that all the shebang lines expect the executable to be called "python3.2" -- ___ Python tracker ___

[issue10677] "make altinstall" includes ABI codes in versioned executable name

2010-12-11 Thread Nick Coghlan
Changes by Nick Coghlan : -- components: +Build stage: -> needs patch type: -> behavior ___ Python tracker ___ ___ Python-bugs-list

[issue10677] "make altinstall" includes ABI codes in versioned executable name

2010-12-11 Thread Nick Coghlan
New submission from Nick Coghlan : "make altinstall" is currently installing python3.2m rather than python3.2. Since PEP 3149 makes no mention of changing the executable name, this should be fixed to correctly install the executable as python3.2. I suspect this will also affect a "make install