➜

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 vstinner
Recipients vstinner
Date 2016-03-29.10:55:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1459248904.21.0.346977974246.issue26662@psf.upfronthosting.co.za>
In-reply-to
Content 
Oh ok, I understood the issue.
---                                                       
[haypo@freebsd ~/prog/python/default]$ rm Objects/typeslots.inc 
[haypo@freebsd ~/prog/python/default]$ make
python ./Objects/typeslots.py < ./Include/typeslots.h > Objects/typeslots.inc
/bin/sh: python: not found
*** Error code 127

Stop.
make: stopped in /home/haypo/prog/python/default
---

I have "python2" and "python3" but no "python" on FreeBSD CURRENT. The configure script is smart enough to select "python3" as the ASDL generator, but it uses $(PYTHON) ("python") to build Objects/typeslots.inc.

We should use a smarter code to select the external "python" program to build Objects/typeslots.inc.

Moreover, when "make Objects/typeslots.inc" fails, it creates an empty Objects/typeslots.inc file:
---
Objects/typeobject.o: Objects/typeslots.inc
Objects/typeslots.inc: $(srcdir)/Include/typeslots.h $(srcdir)/Objects/typeslots.py
        $(PYTHON) $(srcdir)/Objects/typeslots.py < $(srcdir)/Include/typeslots.h > Objects/typeslots.inc
---

The Objects/typeslots.inc should be written directly by Objects/typeslots.py.
History
Date User Action Args
2016-03-29 10:55:04vstinnersetrecipients: + vstinner
2016-03-29 10:55:04vstinnersetmessageid: <1459248904.21.0.346977974246.issue26662@psf.upfronthosting.co.za>
2016-03-29 10:55:04vstinnerlinkissue26662 messages
2016-03-29 10:55:03vstinnercreate