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.

Author ncoghlan
Recipients Kerrick.Staley, benjamin.peterson, eric.araujo, jbicha, loewis, meador.inge, ncoghlan, ned.deily, petri.lehtinen
Date 2012-02-16.12:17:37
SpamBayes Score 4.5587563e-05
Marked as misclassified No
Message-id <1329394657.81.0.000271783666104.issue12627@psf.upfronthosting.co.za>
In-reply-to
Content
Actually, the Python 3 Makefile.pre.in is currently broken if $(EXE) is ever non-empty - in a few places it uses "$(PYTHON)$(VERSION)$(EXE)" and "$(PYTHON)3$(EXE)".

Those are wrong, because the definition of $(PYTHON) at the top of the file is "python$(EXE)"

Instead, they need to be written as "python$(VERSION)$(EXE)" and "python3$(EXE)"
History
Date User Action Args
2012-02-16 12:17:37ncoghlansetrecipients: + ncoghlan, loewis, benjamin.peterson, ned.deily, eric.araujo, meador.inge, petri.lehtinen, Kerrick.Staley, jbicha
2012-02-16 12:17:37ncoghlansetmessageid: <1329394657.81.0.000271783666104.issue12627@psf.upfronthosting.co.za>
2012-02-16 12:17:37ncoghlanlinkissue12627 messages
2012-02-16 12:17:37ncoghlancreate