From: "Jakub Kądziołka" <kuba@kadziolka.net>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: guix-devel@gnu.org
Subject: Re: [Python] pypy3 integration
Date: Mon, 20 Jul 2020 21:42:54 +0200 [thread overview]
Message-ID: <20200720194254.tiolat2ohihsbgu5@gravity> (raw)
In-Reply-To: <20200719082714.GB1359@noor.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
On Sun, Jul 19, 2020 at 10:27:14AM +0200, Lars-Dominik Braun wrote:
> Hi,
>
> I’ve been looking into integrating pypy3 (a JIT Python 3 implementation)
> tighter into guix. Right now we have a package, but it’s not that
> useful, because there are no pypy3-* libraries.
pypy3 works somewhat well for me already in this regard:
~$ genv --pure --ad-hoc pypy3 python-sympy python -- pypy3
Python 3.6.9 (?, Jan 01 1970, 00:00:00)
[PyPy 7.3.1 with GCC 7.5.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>> import sympy
>>>> sympy.isprime(694201337)
True
The `python' package needs to be included in the environment so that
PYTHONPATH gets set, but apart from that, the normal python-prefixed
packages seem to work with pypy. At least, for a sample size of 1 ;)
I suppose it could be worth it to precompile the packages for use in
pypy too, though. I'm not sure what's the best way of solving this. Just
creating separate pypy3-* packages has the big drawback that if you use
python-* instead, you silently get worse loading performance.
Thoughts?
Regards,
Jakub Kądziołka
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-07-20 19:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 8:27 [Python] pypy3 integration Lars-Dominik Braun
2020-07-20 11:17 ` zimoun
2020-07-20 19:16 ` Lars-Dominik Braun
2020-07-20 19:42 ` Jakub Kądziołka [this message]
2020-07-22 6:46 ` Lars-Dominik Braun
2020-07-22 10:39 ` zimoun
2020-07-27 10:48 ` Ludovic Courtès
2020-07-27 19:15 ` zimoun
2020-08-01 8:23 ` Lars-Dominik Braun
2020-07-22 10:34 ` zimoun
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=20200720194254.tiolat2ohihsbgu5@gravity \
--to=kuba@kadziolka.net \
--cc=guix-devel@gnu.org \
--cc=lars@6xq.net \
/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).