unofficial mirror of 
 help / color / Atom feed
From: zimoun <>
To: "Ludovic Courtès" <>
Cc: "Jakub Kądziołka" <>,
	"Guix Devel" <>,
	"Lars-Dominik Braun" <>
Subject: Re: [Python] pypy3 integration
Date: Mon, 27 Jul 2020 21:15:40 +0200
Message-ID: <> (raw)
In-Reply-To: <>


On Mon, 27 Jul 2020 at 12:48, Ludovic Courtès <> wrote:
> Lars-Dominik Braun <> skribis:
> >> pypy3 works somewhat well for me already in this regard:
> > indeed, you’re right.
> >
> > 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.
> Also, what about .pyc files?  Does pypy create compatible .pyc files?

What do you mean by "compatible .pyc files"?

Well, the .pyc generated by CPython should be compatible with the ones
generated by Pypy, both VM targeting say Python 3.6.
But there is no necessary compatibility between .pyc of Python 3.6 and
Python 3.8, at least for CPython as Lars wrote.

CPython being the reference implementation, Pypy is always late.

> > So, does this justify creating pypy3-* packages?
> It probably does.  But do we want to mirror all the ‘python-’ packages,
> or just some of them?  It seems overkill to mirror all of them.

With the current situation, somehow you have to.  But...

> Perhaps we could have a package transformation option to turn a
> ‘python-build-system’ package into a pypy package?

...Yes it could be nice to be able to change the "package builder" of
the build-system.  (Obviously, without any guarantee that the build
would be correct for all combinatorial :-))
The issue is the same for emacs vs emacs-next, GCC versions (without
saying gcc vs clang ;-)), OCaml 4.07 vs OCaml 4.09 etc..
We already discussed this kind of issue when discussing "package parameters".

All the best,

  reply index

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-19  8:27 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
2020-07-27 10:48     ` Ludovic Courtès
2020-07-27 19:15       ` zimoun [this message]
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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

unofficial mirror of 

Archives are clonable:
	git clone --mirror guix-devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 guix-devel guix-devel/ \
	public-inbox-index guix-devel

Example config snippet for mirrors

Newsgroups are available over NNTP:

AGPL code for this site: git clone