From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Antwane Mason <ad.mason1413@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Python Site Package Syntax Runtime Error
Date: Mon, 20 Sep 2021 14:32:14 +0200 [thread overview]
Message-ID: <1621bc1d-a291-e2dd-c598-0367d7c47edd@crazy-compilers.com> (raw)
In-Reply-To: <CAAztfgJraRCKUr74m9dpWWTdLrnkVx=cSbhUDvfrjTkMMG=orQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]
Am 18.09.21 um 21:44 schrieb Antwane Mason:
> From what I can tell, one of the build phases responsible for wrapping
> executables into shell scripts is wrongly wrapping one of the python
> files. This causes the shell script which is named as the original
> python file to be loaded as a python module causing a syntax error
> because the export line is a shell directive and not valid python
> syntax. Below is the stack trace again for reference. The last file
> referenced in the stack trace is a shell script wrapper for the
> original onlykey_agent.py file which was renamed
> .onlykey_agent.py-real. Below is the full file for this shell script.
> Can anyone provide guidance as to which build phase needs to change
> and how to change it to prevent onlykey_agent.py from being wrapped?
Looking at the code of the package - which actually is quite simple - I
discover
scripts=['onlykey_agent.py'],
This might indeed trigger some issue in phase wrap. Please open a
bug-report for this, explicitly pointing to release v1.1.11 of that package.
As a solution for you I propose replacing the aforementioned line in
setup.py by this line:
py_modules=['onlykey_agent'],
I also suggest reporting this upstream, since I assume having
onlykey_agent.py in bin is not desired. (Actually this is not a working
script at all.)
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
[-- Attachment #2: Type: text/html, Size: 2558 bytes --]
next prev parent reply other threads:[~2021-09-20 12:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 17:39 Python Site Package Syntax Runtime Error Antwane Mason
2021-09-16 12:06 ` Hartmut Goebel
2021-09-18 19:44 ` Antwane Mason
2021-09-19 16:31 ` Antwane Mason
2021-09-20 12:32 ` Hartmut Goebel [this message]
2021-09-20 20:28 ` Antwane Mason
2021-09-20 20:45 ` Hartmut Goebel
2021-09-19 17:59 ` Maxime Devos
[not found] ` <CAAztfgL+ZmbupibJtAeEQLdLoPwR=BNmnU80YU10Ea35P3jdeA@mail.gmail.com>
2021-09-20 20:10 ` Antwane Mason
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1621bc1d-a291-e2dd-c598-0367d7c47edd@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=ad.mason1413@gmail.com \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).