From: Maxime Devos <maximedevos@telenet.be>
To: Filip Lajszczak <filip@lajszczak.dev>, 48289@debbugs.gnu.org
Subject: [bug#48289] [PATCH] gnu: Add python-pythonanywhere.
Date: Sat, 08 May 2021 23:16:23 +0200 [thread overview]
Message-ID: <864b6bb2288824630d6e28d01c22617443c1e5b8.camel@telenet.be> (raw)
In-Reply-To: <20210508132849.26030-1-filip@lajszczak.dev>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
Filip Lajszczak schreef op za 08-05-2021 om 15:28 [+0200]:
> * gnu/packages/python-xyz.scm (python-pythonanywhere): New variable.
> [...]
> + (arguments
> + `(#:phases (modify-phases %standard-phases
> + (add-before 'check 'change-home
> + (lambda _
> + (setenv "HOME" "/tmp") #t))
Phases do not need to return #t anymore; the warning you get if you
remove it is misleading. The warning will disappear once core-updates
is merged.
> + (replace 'check
> + (lambda _
> + (invoke "pytest" "-m" "not slowtest") #t)))))
To support "guix build --without-tests" and cross-compilation, make this
> + (replace 'check
> + (lambda* (#:key tests? #:allow-other-keys)
> + (when tests?
> + (invoke "pytest" "-m" "not slowtest"))))
The native-inputs and propagated-inputs seem about right to me,
but I haven't tested.
Greetings,
Maxime
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-05-08 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-08 13:28 [bug#48289] [PATCH] gnu: Add python-pythonanywhere Filip Lajszczak
2021-05-08 21:16 ` Maxime Devos [this message]
2021-05-09 13:06 ` Filip Lajszczak
2021-05-09 13:09 ` Filip Lajszczak
2021-12-17 23:08 ` Filip Lajszczak
2022-01-03 16:34 ` bug#48289: " Ludovic Courtès
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=864b6bb2288824630d6e28d01c22617443c1e5b8.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=48289@debbugs.gnu.org \
--cc=filip@lajszczak.dev \
/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).