From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Marcus Hoffmann <marcus.hoffmann@othermo.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Python pyc only and problem with scripts
Date: Mon, 8 Aug 2022 12:17:23 +0200 [thread overview]
Message-ID: <20220808121723.7d0d2bcb@windsurf> (raw)
In-Reply-To: <35ea7a5d-e0b4-d98e-ca1d-716de2d25698@othermo.de>
Hello Marcus,
On Mon, 8 Aug 2022 12:05:54 +0200
Marcus Hoffmann <marcus.hoffmann@othermo.de> wrote:
> I've noticed a similar problem for pip's PEP517 backend as well, which
> normally calls some internal helper script via python subprocess (and
> uses the .py name for that). This is fixable by using the .pyc suffix
> instead in that case though.
Do you have some details on this?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-08-08 10:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 7:40 [Buildroot] Python pyc only and problem with scripts Federico Pellegrin
2022-08-08 10:05 ` Marcus Hoffmann
2022-08-08 10:17 ` Thomas Petazzoni via buildroot [this message]
2022-08-08 10:30 ` Marcus Hoffmann
2022-08-08 10:47 ` Thomas Petazzoni via buildroot
2022-08-08 17:55 ` Marcus Hoffmann
2022-08-26 9:09 ` Marcus Hoffmann
2022-08-08 10:20 ` Thomas Petazzoni via buildroot
2022-08-08 13:19 ` Federico Pellegrin
2022-08-08 20:48 ` Arnout Vandecappelle
2022-08-09 4:49 ` Federico Pellegrin
2022-08-09 12:54 ` [Buildroot] [External] - " Vincent Fazio
2022-08-09 16:35 ` Yann E. MORIN
2022-08-26 16:31 ` [Buildroot] " James Hilliard
2022-08-26 16:22 ` James Hilliard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220808121723.7d0d2bcb@windsurf \
--to=buildroot@buildroot.org \
--cc=marcus.hoffmann@othermo.de \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox