Re: [Buildroot] Python pyc only and problem with scripts

[Thomas Petazzoni via buildroot <buildroot@buildroot.org>]

Hello Marcus,

On Mon, 8 Aug 2022 12:30:10 +0200
Marcus Hoffmann <marcus.hoffmann@othermo.de> wrote:

> Sorry, I hadn't really gotten around to properly reporting but here's 
> some details:
> 
> https://github.com/pypa/pip/blob/main/src/pip/_vendor/pep517/in_process/__init__.py#L13 
> returns the path to the .py file in question and is called by
> 
> https://github.com/pypa/pip/blob/1880f4a58b4e4ed577a6337d666767784f6831d5/src/pip/_vendor/pep517/wrappers.py#L320-L326 
> via the subprocess call.
> 
> Why they are doing that, I couldn't figure out in the time I spent 
> looking at this.
> 
> This is happening for us when we `pip install` an internal package that 
> uses flit[1] as it's pep517 build backend.
> 
> [1]: https://github.com/pypa/flit

Ah, but you're doing "pip install" on the target?

Without saying it's not supported in Buildroot, it's not really the
recommended way of doing things: we encourage to create proper
Buildroot packages for Python modules.

Of course, since we support installing pip on the target, ideally this
should also work, but I'm not too surprised it can be broken for some
packages as I'm not sure many people use "pip install" on the target in
a Buildroot context.

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