From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: SyntaxError with python3 update
Date: Sat, 26 Mar 2022 03:30:41 +0100 [thread overview]
Message-ID: <20220326023041.MRtDOYkOzWv8DeI3FCu4q728ygQkNO_Zof7XMGRUzRA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36347@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/36347#issuecomment-1079571203
Comment:
This is an expected side effect of the XBPS trigger that pre-compiles Python source and has been present for some time. The trigger uses the `compileall` module to recursively compile Python source in a module directory. The `blender_boolean.py` file responsible for the error is not valid Python source, but a template that is rendered by... something. (I'm not familiar with this package and don't know where it's used.)
Even if we made the trigger more sophisticated to avoid attempts to compile contents that obviously aren't Python source (the trigger used to try compiling a README for one package!), this particular case would be nearly impossible to detect and avoid because it has a `.py` extension and lives in a Python package hierarchy. The right fix here is for `trimesh` upstream to use a different location or extension for this file; it isn't valid Python until rendered and shouldn't masquerade as such.
next prev parent reply other threads:[~2022-03-26 2:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 21:12 [ISSUE] " dkwo
2022-03-26 2:30 ` ahesford [this message]
2022-03-26 2:30 ` [ISSUE] [CLOSED] " ahesford
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=20220326023041.MRtDOYkOzWv8DeI3FCu4q728ygQkNO_Zof7XMGRUzRA@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).