[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#36518: [core-updates] python-boot0 fails to build on armhf and aarch
From: |
Marius Bakke |
Subject: |
bug#36518: [core-updates] python-boot0 fails to build on armhf and aarch64 |
Date: |
Sun, 07 Jul 2019 16:42:35 +0200 |
User-agent: |
Notmuch/0.29.1 (https://notmuchmail.org) Emacs/26.2 (x86_64-pc-linux-gnu) |
Ricardo Wurmus <address@hidden> writes:
> Hi Marius,
>
>> But the interpreter fails with 'unbound variable: this' upon running
>> glibcs Python scripts.
>
> This means it fell through to the case where “python” is called with
> more than one argument:
>
> --8<---------------cut here---------------start------------->8---
> (define* (main #:optional (args (command-line)))
> (match args
> ((_ file)
> (let ((compiled (string-append file ".go")))
> (compile-file file
> #:from python
> #:output-file compiled)
> (load-compiled compiled)))
> ((_)
> (repl-default-option-set! 'prompt ">>> ")
> (set! (@@ (system repl common) repl-welcome)
> (const (display "\
> Python on Guile, version 0.1.0
> (Hit Ctrl-D to exit.)
> ")))
> (start-repl python)
> #t)
> (_ (format (current-error-port)
> "usage: ~a file.py~%" this))))
> --8<---------------cut here---------------end--------------->8---
>
> “this” was supposed to be the first match, i.e. the “python” executable
> itself. Anyway, the problem is that “python” doesn’t handle any flags
> at all. I’ll implement option “handling” soon (maybe we can ignore most
> options to “python”).
I pushed a workaround in 4f5fe46388eb70055b6935df053f74b7ccdaf55f, which
uses an older version of Python that can be built without threads.
signature.asc
Description: PGP signature