From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: buildroot@buildroot.org
Cc: Vincent Fazio <vfazio@xes-inc.com>
Subject: Re: [Buildroot] [PATCH] package/python3: ensure pyc embed rooted paths
Date: Thu, 25 Aug 2022 22:09:14 +0200 [thread overview]
Message-ID: <20220825200914.GB37358@scaer> (raw)
In-Reply-To: <20220825200510.125728-1-yann.morin.1998@free.fr>
On 2022-08-25 22:05 +0200, Yann E. MORIN spake thusly:
> To report usable tracebacks, pyc files embed the path of the original py
> files, so that users can more easily try and debug the reported issue.
>
> We genrate the pyc files by calling the python3-supplied compileall
> script, to scan the directry where python modules are installed. Since
> this is done on the build machine, we tell compileall.py to strip away
> the TARGET_DIR prefix, as that has no meaning at runtime.
>
> However, compileall.py forgets [0] to keep a leading / in the front of
This [0] note should have been:
[0] not sure whether this is a bug or a feature...
Regards,
Yann E. MORIN.
> the paths, thus generating non-rooted paths., e.g.:
> /path/buildroot.ouput/targt/usr/lib/python3.10/argparse.py
> gets embedded as:
> usr/lib/python3.10/argparse.py
>
> This is a bit confusing but, as far as we could see, should be mostly be
> used for display purposes in tracebacks, and does not seem to impact
> actual functkionality.
>
> We fix that by instructing compileall.py that the embeeded paths should
> be rooted to / which generates proper paths in tracebacks.
>
> And alternate solution would be to swith gears, and tell compileall.py
> exactly the resulting runtime "base" directory, wihch replaces the
> stripping and prefixing; i.e. it's either:
> -s $(TARGET_DIR) -p /
> or
> -d /usr/lib/python$(PYTHON3_MAJOR_VERSION)
>
> We choose to keep the first solution, because that is semantically what
> we really want to do: to strip the leading build-time path, rather than
> to force anything.
>
> Note: the python test-suite was executed with both solutions (in a
> pyc-only setup), and the results were exactly the same; so in practice,
> -d or -s+-p yield the same results.
>
> Many thanks go to Vincent for reporting the issue and suggesting the
> solutions.
>
> Reported-by: Vincent Fazio <vfazio@xes-inc.com>
> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
> ---
> package/python3/python3.mk | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/python3/python3.mk b/package/python3/python3.mk
> index 9af384712a..a9821d9a33 100644
> --- a/package/python3/python3.mk
> +++ b/package/python3/python3.mk
> @@ -255,6 +255,7 @@ define PYTHON3_CREATE_PYC_FILES
> $(if $(VERBOSE),,-q) \
> $(if $(BR2_PACKAGE_PYTHON3_PYC_ONLY),-b) \
> -s $(TARGET_DIR) \
> + -p / \
> $(TARGET_DIR)/usr/lib/python$(PYTHON3_VERSION_MAJOR)
> endef
>
> --
> 2.25.1
>
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-08-25 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 20:05 [Buildroot] [PATCH] package/python3: ensure pyc embed rooted paths Yann E. MORIN
2022-08-25 20:09 ` Yann E. MORIN [this message]
2022-08-29 19:16 ` Thomas Petazzoni via buildroot
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=20220825200914.GB37358@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=vfazio@xes-inc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.