unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: 44656@debbugs.gnu.org
Subject: [bug#44656] [PATCH] Upgrade pypy3
Date: Fri, 06 Aug 2021 21:29:22 -0400	[thread overview]
Message-ID: <87h7g2jb4d.fsf@gmail.com> (raw)
In-Reply-To: <YQ1Kr3sqrhBdHcmP@noor.fritz.box> (Lars-Dominik Braun's message of "Fri, 6 Aug 2021 16:43:59 +0200")

Hi Lars-Dominik,

Lars-Dominik Braun <lars@6xq.net> writes:

> Hello Maxim,
>
> that’s answered quickly:
>
>> does it require its own .pyc files?
> Yes, .pyc files are implementation-dependent, as their name suggests
> (module.implementation-version.pyc).
>
>> Does it dismiss CPython's produced ones?
> It won’t look at them.
>
>> Can we not point it to consume our existing Python libraries (it's
>> different sys.path suggest differently), etc.)
> Technically plain Python modules should “just work”, but C extensions
> must be recompiled, so usually it’s safer to run setup.py using PyPy and
> install into a PyPy-specific site-modules.

Thanks for the insights.

I guess one way it could work was if we had some transformation option
to rebuild the Python collection against Pypy (do we have something to
do this already?).

Thanks,

Maxim




  reply	other threads:[~2021-08-07  1:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-15 12:39 [bug#44656] [PATCH] Upgrade pypy3 Lars-Dominik Braun
2020-11-15 19:33 ` Christopher Baines
2020-11-15 19:55   ` Lars-Dominik Braun
2020-11-16 17:26     ` Christopher Baines
2020-11-17  9:38       ` Lars-Dominik Braun
2021-08-03 21:39 ` Maxim Cournoyer
2021-08-05 16:54   ` bug#44656: " Maxim Cournoyer
2021-08-06  7:30   ` [bug#44656] " Lars-Dominik Braun
2021-08-06 14:22     ` Maxim Cournoyer
2021-08-06 14:43       ` Lars-Dominik Braun
2021-08-07  1:29         ` Maxim Cournoyer [this message]
2021-08-07  6:59           ` Lars-Dominik Braun
2021-08-20 10:39             ` zimoun
2021-08-20 14:25               ` Lars-Dominik Braun

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=87h7g2jb4d.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=44656@debbugs.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).