public inbox for gentoo-python@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-python <gentoo-python@lists.gentoo.org>
Cc: python@gentoo.org
Subject: [gentoo-python] RFC: dropping slots on PyPy
Date: Mon, 13 Jan 2014 17:57:12 +0100	[thread overview]
Message-ID: <20140113175712.26eec1db@pomiot.lan> (raw)

[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]

Hello, all.

PyPy is currently slotted in a way similar to other versions of Python.
However, versioning of PyPy doesn't really fit the way CPython is
versioned and the almost-per-version slotting seems unnecessary.

My idea is to switch to a single slot of PyPy starting with the next
version to enter gx86. That is, we would no longer have:

  PYTHON_COMPAT=( pypy{1_8,1_9,2_0} ... )

but instead:

  PYTHON_COMPAT=( pypy pypy3 )

Similarly, we'd either have dev-python/pypy with slots 2 and 3, or even
separate dev-python/pypy3 with slot 0.

We would also add := subslot deps to enforce package rebuilds on pypy
upgrade.

The existing slots could be kept alive as long as pypy2.0 is supported.


Rationale:

Multiple slots of PyPy are using the standard library from the same
slot of CPython. Considering that slotting mostly helps prevent
breakages on upgrade, I don't think we actually need to make more
guarantees about PyPy than about CPython.

Therefore, new versions of PyPy often cause less trouble than new
versions of CPython. Testing all packages and updating PYTHON_COMPAT
on each new release of PyPy seems like a overkill to me.

Then, with pypy3 around, the version number appending ends up really
nasty. Having just 'pypy' and 'pypy3' will simply be cleaner :).


What do you think?

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 966 bytes --]

             reply	other threads:[~2014-01-13 16:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 16:57 Michał Górny [this message]
2014-01-13 17:58 ` [gentoo-python] RFC: dropping slots on PyPy 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

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=20140113175712.26eec1db@pomiot.lan \
    --to=mgorny@gentoo.org \
    --cc=gentoo-python@lists.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