From: "Michał Górny" <mgorny@gentoo.org>
To: Dirkjan Ochtman <djc@gentoo.org>
Cc: gentoo-python@lists.gentoo.org
Subject: Re: [gentoo-python] New eclass: obsoleting old python versions
Date: Wed, 13 Jun 2012 14:11:07 +0200 [thread overview]
Message-ID: <20120613141107.1d48ecc4@pomiocik.lan> (raw)
In-Reply-To: <CAKmKYaDcQ-NC3HRiJc3t=Yq6j43r3wCEOcDGYwDKnbFhYPY4VQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 703 bytes --]
On Wed, 13 Jun 2012 11:16:45 +0200
Dirkjan Ochtman <djc@gentoo.org> wrote:
> Additionally, the new eclass seems to think of pypy1_7, pypy1_8 as
> different. We should probably have something that says, "this ebuild
> supports python-2.7-equivalent pypy".
Are they equivalent API-wise? In other words, is it guaranteed that if
a particular Python extension (written in C) compiles with 1.8, it will
compile with 1.7 and vice-versa?
> Proposal:
>
> - Add python2_7_pypy atom for PYTHON_COMPAT, expands to a list of pypy
> versions which is fixed in the eclass.
Maybe we could just assume pypy1_7 means 1.7+ but older than next
pypy1_x defined.
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]
prev parent reply other threads:[~2012-06-13 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 9:16 [gentoo-python] New eclass: obsoleting old python versions Dirkjan Ochtman
2012-06-13 12:11 ` 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=20120613141107.1d48ecc4@pomiocik.lan \
--to=mgorny@gentoo.org \
--cc=djc@gentoo.org \
--cc=gentoo-python@lists.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