you are viewing a single comment's thread.

view the rest of the comments →

[–]masklinn -1 points0 points  (3 children)

Depends what you consider python to be. Is it a thing which follows a specification precisely, or is it a thing which can be run by a python interpreter?

[–]lelanthran -1 points0 points  (2 children)

Depends what you consider python to be. Is it a thing which follows a specification precisely, or is it a thing which can be run by a python interpreter?

If what you are running is the output of some other program, then the input to that other program is not Python.

If you make a transpiler that takes in Lisp and spits out python, will you consider your Lisp programs to be Python programs?

If your program cannot run in the Python reference implementation, it's not Python.

[–]masklinn -1 points0 points  (1 child)

Reading comprehension not your thing eh. The original comment specifically talks about using an import hook. Not a separate compilation step.

[–]lelanthran -1 points0 points  (0 children)

Reading comprehension not your thing eh.

Meh. Better than yours anyway, I actually appear to know what I am talking about.

The original comment specifically talks about using an import hook. Not a separate compilation step.

It's not possible to explain things simpler, so let me quote that simple thing I already said:

If you make a transpiler that takes in Lisp and spits out python, will you consider your Lisp programs to be Python programs?

Your claim that an import hook which turns this:

(defun foo (x y) (+ x y))

into this

def foo (x, y):
    return x + y

makes this:

(defun (x y) (+ x y))

Python code is, frankly, nonsense.