From: "Michał Górny" <mgorny@gentoo.org>
To: Marien Zwart <marienz@gentoo.org>
Cc: Dirkjan Ochtman <dirkjan@ochtman.nl>,
gentoo-python <gentoo-python@lists.gentoo.org>,
Gentoo Python Project <python@gentoo.org>
Subject: Re: [gentoo-python] Re: RFC: dropping slots on PyPy
Date: Tue, 14 Jan 2014 06:01:53 +0100 [thread overview]
Message-ID: <20140114060153.34209598@pomiot.lan> (raw)
In-Reply-To: <CAEWfL_RQQoP1XLQpL_AatUdn3PHe2txtEo9AzE6QrRrHvkrcxQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
Dnia 2014-01-14, o godz. 14:27:03
Marien Zwart <marienz@gentoo.org> napisał(a):
> On the other hand (at least in the short term) running an older PyPy
> isn't something I'd expect a lot of people to do: running the latest
> and greatest is usually beneficial, not just for features but also for
> better performance and fewer bugs. Chances are most users will either
> fix their code to work with latest PyPy, or run it under CPython for
> compatibility. That seems like an argument not to keep PyPy slotting
> if it's awkward to implement.
Oh, this reminds me of yet another argument. We're basically supporting
only one version of PyPy at a time. This makes the current workflow
like:
1. add new slot,
2. add PYTHON_COMPAT for new slot,
3. remove old slot.
So the two versions are really supported for a short time. I think we
may instead use the following work flow:
1. add new PyPy masked,
2. test packages,
3. unmask new PyPy :).
This would also mean that we'd be able to avoid removing old versions
of PyPy as fast as we do now.
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 966 bytes --]
prev parent reply other threads:[~2014-01-14 5:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 16:57 [gentoo-python] RFC: dropping slots on PyPy Michał Górny
2014-01-13 17:58 ` Mike Gilbert
[not found] ` <CAKmKYaCKMxk1Oa8ZeN3sfj3Y2vT5ZHevFT2hiRHWauWsCRctHA@mail.gmail.com>
2014-01-14 3:27 ` [gentoo-python] " Marien Zwart
2014-01-14 5:01 ` Michał Górny [this message]
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=20140114060153.34209598@pomiot.lan \
--to=mgorny@gentoo.org \
--cc=dirkjan@ochtman.nl \
--cc=gentoo-python@lists.gentoo.org \
--cc=marienz@gentoo.org \
--cc=python@gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox