From: zimoun <zimon.toutoune@gmail.com>
To: "Lars-Dominik Braun" <lars@6xq.net>,
"Jakub Kądziołka" <kuba@kadziolka.net>
Cc: guix-devel@gnu.org
Subject: Re: [Python] pypy3 integration
Date: Wed, 22 Jul 2020 12:39:39 +0200 [thread overview]
Message-ID: <86imef25qs.fsf@gmail.com> (raw)
In-Reply-To: <20200722064657.GA1350@noor.fritz.box>
Dear Lars,
On Wed, 22 Jul 2020 at 08:46, Lars-Dominik Braun <lars@6xq.net> wrote:
>> pypy3 works somewhat well for me already in this regard:
> indeed, you’re right.
Well, python-package and pypy-package would not be compiled with the
same VM. So the performances (optimizations) are not necessary the
sames.
For example, it is the same situation with emacs-package “compiled” with
emacs and run with emacs-next. Even if the bytecode is stable, there is
no guarantee.
> This will probably break for some packages, because python provides
> Python 3.8 whereas pypy3 provides Python 3.6. (They’ve always lagged
> behind and given that we’re going towards 3.10, well…) One example are
> packages depending on importlib.resources, which only became available
> with Python 3.7. Unfortunately this includes the widely-used pytest (or
> rather: its dependency python-pluggy).
>
> Also Python’s C ABI is not stable[1] and thus extensions compiled for 3.8
> can fail in unpredictable ways with 3.6. And looking at python-numpy,
> it seems they won’t even load.
>
> So, does this justify creating pypy3-* packages?
From my point of view, yes.
All the best,
simon
next prev parent reply other threads:[~2020-07-22 10:39 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
2020-07-22 6:46 ` Lars-Dominik Braun
2020-07-22 10:39 ` zimoun [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86imef25qs.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=kuba@kadziolka.net \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.