A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2005-December/058625.html below:

[Python-Dev] should I really have to install Python before Icanbuild it ?

[Python-Dev] should I really have to install Python before Icanbuild it ? [Python-Dev] should I really have to install Python before Icanbuild it ?Fredrik Lundh fredrik at pythonware.com
Mon Dec 12 22:23:27 CET 2005
Brett Cannon wrote:

> > maybe the right thing here would be to change this to
> >
> >     #!./python
> >     """Generate C code from an ASDL description."""
> >
> > and only run the script if ./python has been built ?
>
> What if you build with a different suffix for the executable?  Or do
> different versions of make build different names (e.g., on my OS X
> machine the executable is python.exe in my checkout, not python)?

you're right.  I guess the right thing is to do this in the Makefile, and
use $(PYTHON) to find the appropriate interpreter.

changing the relevant rule to

$(AST_H) $(AST_C): $(AST_ASDL) $(ASDLGEN_FILES)
        -$(PYTHON) $(ASDLGEN) $(AST_ASDL)

might be sufficient.

> The idea seems fine to me, though, since the generated files are
> already checked out.

</F>



More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4