unofficial mirror of guix-devel@gnu.org 
 help / color / Atom feed
From: Lars-Dominik Braun <lars@6xq.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: "Jakub Kądziołka" <kuba@kadziolka.net>,
	"Guix Devel" <guix-devel@gnu.org>
Subject: Re: [Python] pypy3 integration
Date: Sat, 1 Aug 2020 10:23:36 +0200
Message-ID: <20200801082336.GA1347@noor.fritz.box> (raw)
In-Reply-To: <CAJ3okZ3bTnv1Aq=Cxkz6PtL4BQVaTSHx0Cbs+XN71z7ncB_Ziw@mail.gmail.com>

Hi,

> > Also, what about .pyc files?  Does pypy create 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.
both C extensions and .pyc files are guarded by encoding implementation
and Python version in the file name. If we look at python-numpy for
example, we can see files like decorators.cpython-38.pyc and
common.cpython-38-x86_64-linux-gnu.so. If I build numpy with pypy the
identifier (cpython-38) changes to pypy36 and pypy36-pp73 respectively.
Thus pypy won’t load CPython’s files.

> > 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".
I think that would be really helpful. What’s the status of this work? Is
there a PoC I can extend to cover CPython vs. PyPy?

Cheers,
Lars



  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
2020-08-01  8:23         ` Lars-Dominik Braun [this message]
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=20200801082336.GA1347@noor.fritz.box \
    --to=lars@6xq.net \
    --cc=guix-devel@gnu.org \
    --cc=kuba@kadziolka.net \
    --cc=zimon.toutoune@gmail.com \
    /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

unofficial mirror of guix-devel@gnu.org 

Archives are clonable:
	git clone --mirror https://yhetil.org/guix-devel/0 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/ https://yhetil.org/guix-devel \
		guix-devel@gnu.org
	public-inbox-index guix-devel

Example config snippet for mirrors

Newsgroups are available over NNTP:
	nntp://news.yhetil.org/yhetil.gnu.guix.devel
	nntp://news.gmane.io/gmane.comp.gnu.guix.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git